On Sun, Apr 19, 2026 at 02:52:06PM -0700, Linus Torvalds wrote: > On Sun, 19 Apr 2026 at 14:38, Jarkko Sakkinen <[email protected]> wrote: > > > > I tested both PRs for the same baseline with two separate buildroot builds > > of > > You threw away any and all testing that had been done by anybody else > in linux-next. > > And you rebased things on top of a random commit-of-the-day during the > merge window, when things are possibly unstable due to all the *other* > churn going on. > > In other words, you did *EVERYTHING* that you shouldn't be doing, and > that the documentation tells you not to do. > > The WHOLE POINT of being in linux-next and being ready when the merge > window opens is gone. All for apparently nothing. > > Those stable cc tags do not add *any* value, since you could just have > cc'd stable later instead. > > I'm not pulling this. You need to stop doing this pointless churn, and > read the docs on rebasing. See > > Documentation/maintainer/rebasing-and-merging.rst > > about how you are *not* supposed to randomly just rebase, and > _particularly_ not rebase on top of some random state during the merge > window.
"A frequent cause of merge-window trouble is when Linus is presented with a patch series that has clearly been reparented, often to a random commit, shortly before the pull request was sent. The chances of such a series having been adequately tested are relatively low - as are the chances of the pull request being acted upon." OK, point digested. I can update 'next' to contain only fixes from these PRs, and hold on up til doing PR for -rc2 (as corrective step). > > Linus BR, Jarkko
