From: Sasha Levin <sashal@kernel.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: gregkh@linuxfoundation.org, ming.lei@redhat.com, axboe@kernel.dk,
hch@lst.de, mariusz.dabrowski@intel.com, ming.l@ssi.samsung.com,
snitzer@redhat.com, xni@redhat.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] block: don't deal with discard limit in" failed to apply to 4.14-stable tree
Date: Fri, 21 Dec 2018 18:20:26 -0500 [thread overview]
Message-ID: <20181221232026.GF86645@sasha-vm> (raw)
In-Reply-To: <20181220205347.33fjvgobwybpmh2t@debian>
On Thu, Dec 20, 2018 at 08:53:47PM +0000, Sudip Mukherjee wrote:
>Hi Greg,
>
>On Thu, Nov 08, 2018 at 09:23:10AM -0800, gregkh@linuxfoundation.org wrote:
>>
>> The patch below does not apply to the 4.14-stable tree.
>> If someone wants it applied there, or to any other stable or longterm
>> tree, then please email the backport, including the original git commit
>> id to <stable@vger.kernel.org>.
>
>Instead of backporting it was easier to add the commits it depends on.
>1) af097f5d199e ("block: break discard submissions into the user defined size")
>It is not marked for stable but seems it can be in stable.
>
>2) b88aef36b87c ("block: fix infinite loop if the device loses discard capability")
>It is marked for stable but is not there in 4.14-stable.
>
>All are attached to this mail for you to apply.
I've queued both for 4.14 and 4.9. It seems that 4.4 needs something
more complex than that.
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-12-21 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 17:23 FAILED: patch "[PATCH] block: don't deal with discard limit in" failed to apply to 4.14-stable tree gregkh
2018-12-20 20:53 ` Sudip Mukherjee
2018-12-21 23:20 ` Sasha Levin [this message]
2018-12-22 22:40 ` Sudip Mukherjee
2019-01-10 19:21 ` 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=20181221232026.GF86645@sasha-vm \
--to=sashal@kernel.org \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=mariusz.dabrowski@intel.com \
--cc=ming.l@ssi.samsung.com \
--cc=ming.lei@redhat.com \
--cc=snitzer@redhat.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=xni@redhat.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.