From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Kanchan Joshi <joshi.k@samsung.com>, "axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"selvakuma.s1@samsung.com" <selvakuma.s1@samsung.com>,
"nj.shetty@samsung.com" <nj.shetty@samsung.com>,
"javier.gonz@samsung.com" <javier.gonz@samsung.com>
Subject: Re: [PATCH v2 0/1] concurrency handling for zoned null-blk
Date: Mon, 28 Sep 2020 10:08:12 +0000 [thread overview]
Message-ID: <CY4PR04MB37518CD9911CD9EC1643EFBFE7350@CY4PR04MB3751.namprd04.prod.outlook.com> (raw)
In-Reply-To: <20200928095549.184510-1-joshi.k@samsung.com>
On 2020/09/28 18:59, Kanchan Joshi wrote:
> Changes since v1:
> - applied the refactoring suggested by Damien
>
> Kanchan Joshi (1):
> null_blk: synchronization fix for zoned device
>
> drivers/block/null_blk.h | 1 +
> drivers/block/null_blk_zoned.c | 22 ++++++++++++++++++----
> 2 files changed, 19 insertions(+), 4 deletions(-)
>
For single patches, you should add this after the "---" in the patch file, above
the patch stats. This is ignores by git when the patch is applied (the patch
starts at the first "diff" entry).
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2020-09-28 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200928095910epcas5p2226ab95a8e4fbd3cfe3f48afb1a58c40@epcas5p2.samsung.com>
2020-09-28 9:55 ` Kanchan Joshi
[not found] ` <CGME20200928095914epcas5p1beae8d5a201c35b598fde8288532d58d@epcas5p1.samsung.com>
2020-09-28 9:55 ` [PATCH v2 1/1] null_blk: synchronization fix for zoned device Kanchan Joshi
2020-09-28 10:11 ` Damien Le Moal
2020-10-28 2:40 ` Jens Axboe
2020-09-28 10:08 ` Damien Le Moal [this message]
2020-09-28 12:11 ` [PATCH v2 0/1] concurrency handling for zoned null-blk Greg KH
2020-09-28 17:46 ` Kanchan Joshi
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=CY4PR04MB37518CD9911CD9EC1643EFBFE7350@CY4PR04MB3751.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=javier.gonz@samsung.com \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nj.shetty@samsung.com \
--cc=selvakuma.s1@samsung.com \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®