From: Joe Lawrence <joe.lawrence@redhat.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Livepatching <live-patching@vger.kernel.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>, Jonathan Corbet <corbet@lwn.net>,
Attreyee Mukherjee <tintinm2017@gmail.com>
Subject: Re: [PATCH 0/2] Minor grammatical fixup for livepatch docs
Date: Wed, 29 Nov 2023 08:53:22 -0500 [thread overview]
Message-ID: <ac7a90a7-4d29-059b-fbff-6b67e6f5c2d3@redhat.com> (raw)
In-Reply-To: <20231129132527.8078-1-bagasdotme@gmail.com>
On 11/29/23 08:25, Bagas Sanjaya wrote:
> I was prompted to write this little grammar fix series when reading
> the fix from Attreyee [1], with review comments requesting changes
> to that fix. So here's my version of the fix, with reviews from [1]
> addressed (and distinct grammar fixes splitted).
>
Typical kernel workflow would be for Attreyee to incorporate feedback
and post their v2 after a day or two. From the format they posted, it
appears to be a first(ish) kernel contribution post. Let's be kind and
patient so they we all may benefit from the practice of iterating on
their patch.
--
Joe
next prev parent reply other threads:[~2023-11-29 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 13:25 [PATCH 0/2] Minor grammatical fixup for livepatch docs Bagas Sanjaya
2023-11-29 13:25 ` [PATCH 1/2] Documentation: livepatch: Correct "step on each other's toes" idiom Bagas Sanjaya
2023-11-29 13:25 ` [PATCH 2/2] Documentation: livepatch: Correct opposite of releasing locks Bagas Sanjaya
2023-11-29 13:53 ` Joe Lawrence [this message]
2023-11-29 23:58 ` [PATCH 0/2] Minor grammatical fixup for livepatch docs Bagas Sanjaya
2023-11-30 0:08 ` Matthew Wilcox
2023-11-30 3:25 ` Bagas Sanjaya
2023-11-30 0:10 ` Jonathan Corbet
2023-11-30 8:04 ` Bagas Sanjaya
2023-11-29 14:29 ` Jonathan Corbet
2023-11-29 15:26 ` Matthew Wilcox
2023-11-30 0:13 ` Bagas Sanjaya
[not found] ` <CAJjsb4r5S80ZqdX3EnucSfeiyeFEgUOW+5++=XG4rT85Os4PNQ@mail.gmail.com>
2023-11-30 0:14 ` Bagas Sanjaya
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=ac7a90a7-4d29-059b-fbff-6b67e6f5c2d3@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=jikos@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=tintinm2017@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 NNTP newsgroup(s).