From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH v2] nvmet: fix nvmet_execute_write_zeroes function
Date: Wed, 4 Apr 2018 19:48:18 -0600 [thread overview]
Message-ID: <20180405014818.GC10098@localhost.localdomain> (raw)
In-Reply-To: <DM5PR2101MB1032170718BCAF7FB1BD0B98FBBB0@DM5PR2101MB1032.namprd21.prod.outlook.com>
On Thu, Apr 05, 2018@01:34:28AM +0000, Sasha Levin wrote:
> [This is an automated email]
>
> This commit has been processed by the -stable helper bot and determined
> to be a high probability candidate for -stable trees. (score: 6.9916)
>
> The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126,
Nice! Good bot. :)
> v4.15.15: Build OK!
> v4.14.32: Build OK!
> v4.9.92: Failed to apply! Possible dependencies:
> d262920998c8: ("nvmet: add support for the Write Zeroes command")
> 78ce3daa7d70: ("nvmet: fix byte swap in nvmet_execute_write_zeroes")
> d262920998c8: ("nvmet: add support for the Write Zeroes command")
>
> v4.4.126: Failed to apply! Possible dependencies:
> d262920998c8: ("nvmet: add support for the Write Zeroes command")
> a07b4970f464: ("nvmet: add a generic NVMe target")
> 78ce3daa7d70: ("nvmet: fix byte swap in nvmet_execute_write_zeroes")
> d262920998c8: ("nvmet: add support for the Write Zeroes command")
> a07b4970f464: ("nvmet: add a generic NVMe target")
>
>
> Please let us know if you'd like to have this patch included in a stable tree.
Yes, please! 4.14+
WARNING: multiple messages have this Message-ID (diff)
From: Keith Busch <keith.busch@intel.com>
To: Sasha Levin <Alexander.Levin@microsoft.com>
Cc: "Rodrigo R. Galvao" <rosattig@linux.vnet.ibm.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"hch@lst.de" <hch@lst.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"sagi@grimberg.me" <sagi@grimberg.me>
Subject: Re: [PATCH v2] nvmet: fix nvmet_execute_write_zeroes function
Date: Wed, 4 Apr 2018 19:48:18 -0600 [thread overview]
Message-ID: <20180405014818.GC10098@localhost.localdomain> (raw)
In-Reply-To: <DM5PR2101MB1032170718BCAF7FB1BD0B98FBBB0@DM5PR2101MB1032.namprd21.prod.outlook.com>
On Thu, Apr 05, 2018 at 01:34:28AM +0000, Sasha Levin wrote:
> [This is an automated email]
>
> This commit has been processed by the -stable helper bot and determined
> to be a high probability candidate for -stable trees. (score: 6.9916)
>
> The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126,
Nice! Good bot. :)
> v4.15.15: Build OK!
> v4.14.32: Build OK!
> v4.9.92: Failed to apply! Possible dependencies:
> d262920998c8: ("nvmet: add support for the Write Zeroes command")
> 78ce3daa7d70: ("nvmet: fix byte swap in nvmet_execute_write_zeroes")
> d262920998c8: ("nvmet: add support for the Write Zeroes command")
>
> v4.4.126: Failed to apply! Possible dependencies:
> d262920998c8: ("nvmet: add support for the Write Zeroes command")
> a07b4970f464: ("nvmet: add a generic NVMe target")
> 78ce3daa7d70: ("nvmet: fix byte swap in nvmet_execute_write_zeroes")
> d262920998c8: ("nvmet: add support for the Write Zeroes command")
> a07b4970f464: ("nvmet: add a generic NVMe target")
>
>
> Please let us know if you'd like to have this patch included in a stable tree.
Yes, please! 4.14+
next prev parent reply other threads:[~2018-04-05 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 14:49 [PATCH v2] nvmet: fix nvmet_execute_write_zeroes function Rodrigo R. Galvao
2018-04-02 14:49 ` Rodrigo R. Galvao
2018-04-02 14:58 ` Keith Busch
2018-04-02 14:58 ` Keith Busch
2018-04-02 16:31 ` Rodrigo Rosatti Galvao
2018-04-02 16:31 ` Rodrigo Rosatti Galvao
2018-04-05 1:34 ` Sasha Levin
2018-04-05 1:34 ` Sasha Levin
2018-04-05 1:48 ` Keith Busch [this message]
2018-04-05 1:48 ` Keith Busch
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=20180405014818.GC10098@localhost.localdomain \
--to=keith.busch@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.