> On Mon, 1 Dec 2025 20:38:16 -0500 > Steven Rostedt <[email protected]> wrote: > > It's best to always use your latest branch that you did your last pull on > during a release cycle. > > I see you based these changes on v6.18-rc7, but your previous pull was > based on v6.18-rc5. If I were to pull this in, it gets a bit spaghetti like > in the merges. > > v6.18-rc5 -> pull1 > merge <- v6.18-rc7 <- pull2 > > Where now we have changes between rc5 and rc7. Was there a reason you > based on top of rc7 and not use your last pull? > > It's fine sending urgent patches this way, as these tags are in Linus's > tree and it's just new changes being added. But for a subsytem tree, it's > best not to pull in Linus's tree unless there's a good reason to do that.
Yeah got it, there was no valid reason for that rebase, I'm going to keep it stable next time or write it explicitly otherwise. > What I can do is simply pull the patches on top of your last patch > directly, and keep the history clean for my pull request to Linus. I'm pushed the tag rebased on -rc5 (actually on the last PR) just in case it makes your life easier: The following changes since commit 69d8895cb9a9f6450374577af8584c2e21cb5a9f: rv: Add explicit lockdep context for reactors (2025-11-11 13:18:56 +0100) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gmonaco/linux.git rv-6.19-next-2-rc5 for you to fetch changes up to b30f635bb6492f02f2f704b46d898679371015cb: rv: Convert to use __free (2025-12-02 07:28:32 +0100) Thanks, Gabriele
