From: Jonathan Corbet <corbet@lwn.net>
To: paulmck@kernel.org
Cc: Nikil Paul S <snikilpaul@gmail.com>,
linux-doc@vger.kernel.org, skhan@linuxfoundation.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH v4] docs: rcu: Replace multiple dead OLS links in RTFP.txt
Date: Thu, 21 Aug 2025 16:14:13 -0600 [thread overview]
Message-ID: <877bywqq4q.fsf@trenco.lwn.net> (raw)
In-Reply-To: <972cf9c8-f8a6-4a5a-90a4-696f9a4e0f6d@paulmck-laptop>
"Paul E. McKenney" <paulmck@kernel.org> writes:
> On Thu, Aug 21, 2025 at 11:54:45AM -0600, Jonathan Corbet wrote:
>> Nikil Paul S <snikilpaul@gmail.com> writes:
>>
>> > This patch updates several dead OLS links in RTFP.txt, replacing them
>> > with working copies hosted on kernel.org.
>> >
>> > Originally posted as part of a 2-patch series, this is now being sent
>> > as a standalone v4 patch to avoid confusion.
>> >
>> > Changes since v3:
>> > - No change in content, only resubmitted as a single patch instead of
>> > "2/2" from the earlier series.
>> >
>> > Signed-off-by: Nikil Paul S <snikilpaul@gmail.com>
>> > ---
>> > Documentation/RCU/RTFP.txt | 6 +++---
>> > 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> So this looks good to me, but it should really be run past the RCU folks
>> (and Paul in particular) as well; adding him to the CC.
>
> I queued this and checked it and it looks good. By default, I would
> send this during the upcoming merge window. But if you would rather
> take it:
>
> Reviewed-by: Paul E. McKenney <paulmck@kernel.org>
>
> Either way, let me know!
It's all yours.
Thanks,
jon
prev parent reply other threads:[~2025-08-21 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 18:05 [PATCH v4] docs: rcu: Replace multiple dead OLS links in RTFP.txt Nikil Paul S
2025-08-21 17:54 ` Jonathan Corbet
2025-08-21 21:31 ` Paul E. McKenney
2025-08-21 22:14 ` Jonathan Corbet [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=877bywqq4q.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=snikilpaul@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