From: Greg KH <gregkh@linuxfoundation.org>
To: Jeffle Xu <jefflexu@linux.alibaba.com>
Cc: sashal@kernel.org, stable@vger.kernel.org, snitzer@redhat.com
Subject: Re: [PATCH 5.4.y 2/4] dm table: fix partial completion iterate_devices based device capability checks
Date: Fri, 5 Mar 2021 09:44:43 +0100 [thread overview]
Message-ID: <YEHve5QkPuimNnnY@kroah.com> (raw)
In-Reply-To: <20210305065722.73504-3-jefflexu@linux.alibaba.com>
On Fri, Mar 05, 2021 at 02:57:20PM +0800, Jeffle Xu wrote:
> Similar to commit a4c8dd9c2d09 ("dm table: fix iterate_devices based
> device capability checks"), fix partial completion capability check and
> invert logic of the corresponding iterate_devices_callout_fn so that all
> devices' partial completion capabilities are properly checked.
>
> Signed-off-by: Jeffle Xu <jefflexu@linux.alibaba.com>
> Fixes: 22c11858e800 ("dm: introduce DM_TYPE_NVME_BIO_BASED")
> ---
> drivers/md/dm-table.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Why isn't this a commit in Linus's tree? That needs to be really really
explicitly documented here.
thanks,
greg k-h
next prev parent reply other threads:[~2021-03-05 8:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 13:44 FAILED: patch "[PATCH] dm table: fix iterate_devices based device capability checks" failed to apply to 5.4-stable tree gregkh
2021-03-05 6:57 ` [PATCH 5.4.y 0/4] dm: device capability check fixes Jeffle Xu
2021-03-05 6:57 ` [PATCH 5.4.y 1/4] dm table: fix iterate_devices based device capability checks Jeffle Xu
2021-03-07 15:11 ` Greg KH
2021-03-05 6:57 ` [PATCH 5.4.y 2/4] dm table: fix partial completion " Jeffle Xu
2021-03-05 8:44 ` Greg KH [this message]
2021-03-05 8:57 ` JeffleXu
2021-03-05 6:57 ` [PATCH 5.4.y 3/4] dm table: fix DAX " Jeffle Xu
2021-03-07 15:06 ` Greg KH
2021-03-08 2:05 ` JeffleXu
2021-03-05 6:57 ` [PATCH 5.4.y 4/4] dm table: fix zoned " Jeffle Xu
2021-03-05 8:49 ` [PATCH 5.4.y 0/4] dm: device capability check fixes Greg KH
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=YEHve5QkPuimNnnY@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jefflexu@linux.alibaba.com \
--cc=sashal@kernel.org \
--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