From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Milan Lakhani <milan.lakhani@codethink.co.uk>
Cc: corbet@lwn.net, lukas.bulwahn@gmail.com,
linux-kernel@vger.kernel.org, linux-safety@lists.elisa.tech,
devel@driverdev.osuosl.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH] Documentation: process: Correct numbering
Date: Tue, 15 Dec 2020 20:16:39 +0000 [thread overview]
Message-ID: <20201215201639.cuq7xtyanbk6bxan@debian> (raw)
In-Reply-To: <1608061835-5118-1-git-send-email-milan.lakhani@codethink.co.uk>
Hi Milan,
On Tue, Dec 15, 2020 at 07:50:35PM +0000, Milan Lakhani wrote:
> Renumber the steps in submit-checklist.rst as some numbers were skipped.
>
> Signed-off-by: Milan Lakhani <milan.lakhani@codethink.co.uk>
Maybe you can also add:
Fixes: 72deb455b5ec ("block: remove CONFIG_LBDAF")
But I am confused about why you have added Greg and staging list instead
of 'linux-doc@vger.kernel.org'.
--
Regards
Sudip
parent reply other threads:[~2020-12-15 20:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1608061835-5118-1-git-send-email-milan.lakhani@codethink.co.uk>]
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=20201215201639.cuq7xtyanbk6bxan@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=corbet@lwn.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-safety@lists.elisa.tech \
--cc=lukas.bulwahn@gmail.com \
--cc=milan.lakhani@codethink.co.uk \
/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