[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CY4PR04MB37518CD9911CD9EC1643EFBFE7350@CY4PR04MB3751.namprd04.prod.outlook.com>
Date: Mon, 28 Sep 2020 10:08:12 +0000
From: Damien Le Moal <Damien.LeMoal@....com>
To: Kanchan Joshi <joshi.k@...sung.com>,
"axboe@...nel.dk" <axboe@...nel.dk>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"selvakuma.s1@...sung.com" <selvakuma.s1@...sung.com>,
"nj.shetty@...sung.com" <nj.shetty@...sung.com>,
"javier.gonz@...sung.com" <javier.gonz@...sung.com>
Subject: Re: [PATCH v2 0/1] concurrency handling for zoned null-blk
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
Powered by blists - more mailing lists