From: Neeraj upadhyay <neeraj.iitr10@gmail.com>
To: Joel Fernandes <joelagnelf@nvidia.com>
Cc: linux-kernel@vger.kernel.org, rcu@vger.kernel.org, paulmck@kernel.org
Subject: Re: [PATCH -next 0/6] Patches for v6.17
Date: Wed, 16 Jul 2025 11:02:06 +0530 [thread overview]
Message-ID: <CAFwiDX9oGOdvFjdRrrfqrnHeFmfz3GHmA1AgHMZAHGdyn6qPPA@mail.gmail.com> (raw)
In-Reply-To: <20250715200156.2852484-1-joelagnelf@nvidia.com>
Hi Joel,
On Wed, Jul 16, 2025 at 1:32 AM Joel Fernandes <joelagnelf@nvidia.com> wrote:
>
> Just a repost of patches with tags, for our consideration into v6.17.
>
> All have tags, and the last commit is a fixup for the deadloop patch which can
> be squashed into the original patch.
>
> Joel Fernandes (6):
> smp: Document preemption and stop_machine() mutual exclusion
> rcu: Refactor expedited handling check in rcu_read_unlock_special()
> rcu: Document GP init vs hotplug-scan ordering requirements
> rcu: Document separation of rcu_state and rnp's gp_seq
> rcu: Document concurrent quiescent state reporting for offline CPUs
> [please squash] fixup! rcu: Fix rcu_read_unlock() deadloop due to IRQ
> work
>
I have included patches 2-6 here:
https://git.kernel.org/pub/scm/linux/kernel/git/neeraj.upadhyay/linux-rcu.git/log/?h=rcu.merge.16.07.2025c
for testing
Fixed few whitespaces errors in the documentation.
I see below warnings while doing `make htmldocs`. Can you suggest a
fix for these?
Documentation/RCU/Design/Data-Structures/Data-Structures.rst:305:
ERROR: Unexpected indentation.
Documentation/RCU/Design/Data-Structures/Data-Structures.rst:307:
WARNING: Block quote ends without a blank line; unexpected unindent.
- Neeraj
next prev parent reply other threads:[~2025-07-16 5:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 20:01 [PATCH -next 0/6] Patches for v6.17 Joel Fernandes
2025-07-15 20:01 ` [PATCH -next 1/6] smp: Document preemption and stop_machine() mutual exclusion Joel Fernandes
2025-07-15 20:01 ` [PATCH -next 2/6] rcu: Refactor expedited handling check in rcu_read_unlock_special() Joel Fernandes
2025-07-15 20:01 ` [PATCH -next 3/6] rcu: Document GP init vs hotplug-scan ordering requirements Joel Fernandes
2025-07-15 20:01 ` [PATCH -next 4/6] rcu: Document separation of rcu_state and rnp's gp_seq Joel Fernandes
2025-07-15 20:01 ` [PATCH -next 5/6] rcu: Document concurrent quiescent state reporting for offline CPUs Joel Fernandes
2025-07-15 20:01 ` [PATCH -next 6/6] [please squash] fixup! rcu: Fix rcu_read_unlock() deadloop due to IRQ work Joel Fernandes
2025-07-16 5:32 ` Neeraj upadhyay [this message]
2025-07-20 4:30 ` [PATCH -next 0/6] Patches for v6.17 Akira Yokosawa
2025-07-21 4:29 ` Neeraj upadhyay
2025-07-21 8:27 ` Joel Fernandes
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=CAFwiDX9oGOdvFjdRrrfqrnHeFmfz3GHmA1AgHMZAHGdyn6qPPA@mail.gmail.com \
--to=neeraj.iitr10@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
/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 NNTP newsgroup(s).