From: Jonathan Corbet <corbet@lwn.net>
To: NIKIL PAUL <snikilpaul@gmail.com>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH 2/2 v3] docs: rcu: Replace multiple dead OLS links in RTFP.txt
Date: Mon, 18 Aug 2025 10:52:38 -0600 [thread overview]
Message-ID: <877bz08td5.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CAHHgkHp-oMuCfRGqL6FGrDNSi3a3HzU7uW27vUfNW7evk1m4+Q@mail.gmail.com>
[CCs restored]
NIKIL PAUL <snikilpaul@gmail.com> writes:
> A smal follow-up, Do i need to do any more changes on this before getting accepted?
> It has two more changes which weren't in the previous version.
So I only received 2/2, so I lack some context here. It seems you only
reposted this one patch out of the series? When you make changes, you
need to post the whole series so that maintainers know what is going on.
Thanks,
jon
prev parent reply other threads:[~2025-08-18 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 16:32 [PATCH 2/2 v3] docs: rcu: Replace multiple dead OLS links in RTFP.txt Nikil Paul S
[not found] ` <CAHHgkHp-oMuCfRGqL6FGrDNSi3a3HzU7uW27vUfNW7evk1m4+Q@mail.gmail.com>
2025-08-18 16:52 ` 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=877bz08td5.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=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