From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: [PATCH] dm zoned: assign max_io_len correctly
Date: Tue, 30 Jun 2020 10:20:19 +0200 [thread overview]
Message-ID: <20200630082019.GA636803@kroah.com> (raw)
In-Reply-To: <CY4PR04MB37511B459111266535ACEF62E76F0@CY4PR04MB3751.namprd04.prod.outlook.com>
On Tue, Jun 30, 2020 at 06:20:58AM +0000, Damien Le Moal wrote:
> On 2020/06/30 15:18, Greg Kroah-Hartman wrote:
> > On Tue, Jun 30, 2020 at 01:00:47PM +0900, Damien Le Moal wrote:
> >> From: Hou Tao <houtao1@huawei.com>
> >>
> >> commit 7b2377486767503d47265e4d487a63c651f6b55d upstream.
> >>
> >> The unit of max_io_len is sector instead of byte (spotted through
> >> code review), so fix it.
> >>
> >> Fixes: 3b1a94c88b79 ("dm zoned: drive-managed zoned block device target")
> >> Cc: stable@vger.kernel.org
> >> Signed-off-by: Hou Tao <houtao1@huawei.com>
> >> Reviewed-by: Damien Le Moal <damien.lemoal@wdc.com>
> >> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
> >> ---
> >> drivers/md/dm-zoned-target.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > What stable tree(s) is this for?
> >
>
> 5.7, 5.4, 4.19 and 4.14.
>
> Got the automated email that the patch was not applying so I sent this corrected
> version. I sent you a separate note about this.
Yes, but given the huge email flow, you need to be specific as your
response there was seen about an hour after this email due to them not
being threaded/attached/whatever :)
thanks,
gre gk-h
next prev parent reply other threads:[~2020-06-30 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 4:00 [PATCH] dm zoned: assign max_io_len correctly Damien Le Moal
2020-06-30 6:18 ` Greg Kroah-Hartman
2020-06-30 6:20 ` Damien Le Moal
2020-06-30 8:20 ` Greg Kroah-Hartman [this message]
2020-07-01 0:36 ` Damien Le Moal
2020-07-07 14:05 ` Greg Kroah-Hartman
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=20200630082019.GA636803@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Damien.LeMoal@wdc.com \
--cc=snitzer@redhat.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;
as well as URLs for NNTP newsgroup(s).