Hi Paul,
On Tue, 28 May 2024 11:54:44 -0700 "Paul E. McKenney" <paulmck@xxxxxxxxxx> wrote:
>
> From here on, could you please pull from branch "next" in our shiny new
> shared RCU tree?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rcu/linux
Do you want this to replace your current tree, or in addition?
> Please let me know of any questions or concerns. Or, for that matter, if
> there is some automated way to do this that I have long since forgotten.
>
> I will still have non-RCU commits from my own tree for -next, and I must
> confess that the name "rcu/next" seems entirely inappropriate (to say
> nothing of confusing) for that purpose. Would you be OK changing to a
> branch named "non-rcu/next" or something similar?
I don't care what the branch is called as long as it is a stable name.
I have done the following for now: added the new rcu tree as above and
renamed the old rcu tree to be the paulmck tree (still fetching the
rcu/next branch). Let me know what you want the final set up to look
like. Also, do you have more contacts (preferable full email
addresses) for the new rcu tree (currently I just have you)?
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgement of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
sfr@xxxxxxxxxxxxxxxx
--
Cheers,
Stephen Rothwell
Attachment:
pgpy2mk0HM7DH.pgp
Description: OpenPGP digital signature
