ba93f2d ("8250: Make SERIAL_8250_RUNTIME_UARTS work correctly")
0d1ed2d ("Revert "serial: 8250: Do nothing if nr_uarts=0"")
... and then turn around and add them back in with a commit message that more accurately explains the problem we have, how we tried to solve it, why upstream won't take it, but why we still need it (or something with the same functionality).
This is also a bit of an experiment to see how well this sort of workflow for no-actual-changes-but-new-commit-messages works with PR tooling. (Unfortunately because of the nature of this I don't think you'll be able to mark comments on parts of the commit messages themselves?)
I am also attempting to use Upstream-Status in a way similar to OpenEmbedded's patch guidelines for commits that we know can't or won't be able to go upstream.
Revert two commits:
... and then turn around and add them back in with a commit message that more accurately explains the problem we have, how we tried to solve it, why upstream won't take it, but why we still need it (or something with the same functionality).
This is also a bit of an experiment to see how well this sort of workflow for no-actual-changes-but-new-commit-messages works with PR tooling. (Unfortunately because of the nature of this I don't think you'll be able to mark comments on parts of the commit messages themselves?)
I am also attempting to use
Upstream-Statusin a way similar to OpenEmbedded's patch guidelines for commits that we know can't or won't be able to go upstream.