public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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 4.4.y 2/2] dm table: fix no_sg_merge iterate_devices based device capability checks
Date: Fri, 5 Mar 2021 07:46:24 +0100	[thread overview]
Message-ID: <YEHTwKad3rP+fMIe@kroah.com> (raw)
In-Reply-To: <20210305063051.51030-3-jefflexu@linux.alibaba.com>

On Fri, Mar 05, 2021 at 02:30:51PM +0800, Jeffle Xu wrote:
> Similar to commit a4c8dd9c2d09 ("dm table: fix iterate_devices based
> device capability checks"), fix NO_SG_MERGE capability check and invert
> logic of the corresponding iterate_devices_callout_fn so that all
> devices' NO_SG_MERGE capabilities are properly checked.
> 
> Signed-off-by: Jeffle Xu <jefflexu@linux.alibaba.com>
> Fixes: 200612ec33e5 ("dm table: propagate QUEUE_FLAG_NO_SG_MERGE")
> ---
>  drivers/md/dm-table.c | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)

What is the git commit id of this patch in Linus's tree?

thanks,

greg k-h

  reply	other threads:[~2021-03-05  6:46 UTC|newest]

Thread overview: 9+ 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 4.4-stable tree gregkh
2021-03-05  6:30 ` [PATCH 4.4.y 0/2] dm: device capability check fixes Jeffle Xu
2021-03-05  6:30   ` [PATCH 4.4.y 1/2] dm table: fix iterate_devices based device capability checks Jeffle Xu
2021-03-05  6:30   ` [PATCH 4.4.y 2/2] dm table: fix no_sg_merge " Jeffle Xu
2021-03-05  6:46     ` Greg KH [this message]
2021-03-05  7:00       ` JeffleXu
2021-03-08  3:21     ` JeffleXu
2021-03-08 13:45       ` JeffleXu
2021-03-05  6:47   ` [PATCH 4.4.y 0/2] 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=YEHTwKad3rP+fMIe@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