From: Jonathan Corbet <corbet@lwn.net>
To: Andrew Klychkov <andrew.a.klychkov@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: fix typos found in admin-guide subdirectory
Date: Thu, 3 Dec 2020 08:05:52 -0700 [thread overview]
Message-ID: <20201203080552.5411702f@lwn.net> (raw)
In-Reply-To: <CA+mfrmy-cWfT+GJK1WiqVm8_CrUmCFP_0xDkoCGhyc0qi=i+Jw@mail.gmail.com>
On Thu, 3 Dec 2020 06:52:30 +0300
Andrew Klychkov <andrew.a.klychkov@gmail.com> wrote:
> Should i fix the patch or you’ll just exclude this part yourself?
Please send a fixed version with Randy's Reviewed-by tag added as well.
The right way to fix that might be "ANDed" to make it what is being said
clear.
Thanks,
jon
prev parent reply other threads:[~2020-12-03 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 8:44 [PATCH] Documentation: fix typos found in admin-guide subdirectory Andrew Klychkov
2020-12-03 0:30 ` Randy Dunlap
[not found] ` <CA+mfrmy-cWfT+GJK1WiqVm8_CrUmCFP_0xDkoCGhyc0qi=i+Jw@mail.gmail.com>
2020-12-03 15:05 ` 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=20201203080552.5411702f@lwn.net \
--to=corbet@lwn.net \
--cc=andrew.a.klychkov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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).