RCU Archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: rcu@vger.kernel.org, frederic@kernel.org,
	quic_neeraju@quicinc.com, urezki@gmail.com,
	joel@joelfernandes.org, boqun.feng@gmail.com
Subject: Boqun will be doing RCU PR for v6.9 merge window
Date: Wed, 6 Mar 2024 09:03:48 -0800	[thread overview]
Message-ID: <e85e7908-3d25-40ba-9931-917649d9a343@paulmck-laptop> (raw)
In-Reply-To: <d9bab0d0-02a4-4220-88b0-3f9a86512bf8@paulmck-laptop>

Hello, Linus,

This time, Boqun Feng will be handling the RCU commits for the upcoming
v6.9 merge window.  This is once again a practice exercise.  And again,
I suggested that I would be doing v6.9, but Boqun was willing to give
it a go, so why not?

Once all five have done one solo pull request, I expect that we will
move to a shared RCU tree on kernel.org, and I have already alerted
Konstantin to this.

This yet again covers only RCU, so I will be sending pull requests as
needed for the other topics.  Of which there just might not be any.

And yet again, please let me know of any concerns or issues with this.

							Thanx, Paul

      parent reply	other threads:[~2024-03-06 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 15:44 Frederic will be doing RCU PR for v6.7 merge window Paul E. McKenney
2023-11-28  5:03 ` Neeraj will be doing RCU PR for v6.8 " Paul E. McKenney
2023-11-28  5:05   ` Paul E. McKenney
2024-01-11 10:52     ` Paul E. McKenney
2024-01-11 18:18       ` Linus Torvalds
2024-01-11 18:35         ` Neeraj upadhyay
2024-03-06 17:03   ` Paul E. McKenney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e85e7908-3d25-40ba-9931-917649d9a343@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=frederic@kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=quic_neeraju@quicinc.com \
    --cc=rcu@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=urezki@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).