From: Shuah Khan <skhan@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>, gregkh@linuxfoundation.org
Cc: stable@vger.kernel.org, Tom Seewald <tseewald@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: FAILED: patch "[PATCH] usbip: vudc synchronize sysfs code paths" failed to apply to 4.14-stable tree
Date: Fri, 23 Apr 2021 13:59:18 -0600 [thread overview]
Message-ID: <5a668128-93ff-8e77-f595-dea0c8233d58@linuxfoundation.org> (raw)
In-Reply-To: <YIMjud72SYv5t5tt@debian>
On 4/23/21 1:44 PM, Sudip Mukherjee wrote:
> Hi Greg,
>
> On Sun, Apr 11, 2021 at 09:20:12AM +0200, 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>.
>>
>> thanks,
>>
>> greg k-h
>>
>> ------------------ original commit in Linus's tree ------------------
>>
>> From bd8b82042269a95db48074b8bb400678dbac1815 Mon Sep 17 00:00:00 2001
>
> Just wondering if you have missed this one as I am not seeing it in your
> queue for 4.14-stable but can see in 4.9-stable queue. And this will apply
> directly on top of your 4.14-stable queue.
>
>
This patch needed some work. Tom sent in the patch.
https://lore.kernel.org/stable/d2cc4517-4790-b3a7-eec0-16fe06ea22eb@linuxfoundation.org/
thanks,
-- Shuah
next prev parent reply other threads:[~2021-04-23 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 7:20 FAILED: patch "[PATCH] usbip: vudc synchronize sysfs code paths" failed to apply to 4.14-stable tree gregkh
2021-04-23 19:44 ` Sudip Mukherjee
2021-04-23 19:59 ` Shuah Khan [this message]
2021-04-24 14:45 ` Greg KH
2021-04-26 15:39 ` Shuah Khan
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=5a668128-93ff-8e77-f595-dea0c8233d58@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=tseewald@gmail.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 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).