public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: axboe@kernel.dk, Damien.LeMoal@wdc.com,
	linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	stable@vger.kernel.org, selvakuma.s1@samsung.com,
	nj.shetty@samsung.com, javier.gonz@samsung.com
Subject: Re: [PATCH v2 0/1] concurrency handling for zoned null-blk
Date: Mon, 28 Sep 2020 14:11:36 +0200	[thread overview]
Message-ID: <20200928121136.GA661041@kroah.com> (raw)
In-Reply-To: <20200928095549.184510-1-joshi.k@samsung.com>

On Mon, Sep 28, 2020 at 03:25:48PM +0530, 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(-)
> 
> -- 
> 2.25.1
> 


<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

  parent reply	other threads:[~2020-09-28 12:11 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 ` [PATCH v2 0/1] concurrency handling for zoned null-blk Kanchan Joshi
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   ` [PATCH v2 0/1] concurrency handling for zoned null-blk Damien Le Moal
2020-09-28 12:11   ` Greg KH [this message]
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=20200928121136.GA661041@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=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