From: Shuah Khan <skhan@linuxfoundation.org>
To: gregkh@linuxfoundation.org, suwan.kim027@gmail.com,
dan.carpenter@oracle.com, lkp@intel.com, stable@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: FAILED: patch "[PATCH] usbip: Fix uninitialized symbol 'nents' in" failed to apply to 4.9-stable tree
Date: Wed, 27 Nov 2019 16:32:38 -0700 [thread overview]
Message-ID: <b3cb8295-cbb3-013c-dc75-1e56ddd0a8de@linuxfoundation.org> (raw)
In-Reply-To: <1574884381220214@kroah.com>
On 11/27/19 12:53 PM, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 4.9-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>.
>
This patch isn't applicable to 4.4. We can ignore the failure.
thanks,
-- Shuah
prev parent reply other threads:[~2019-11-27 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 19:53 FAILED: patch "[PATCH] usbip: Fix uninitialized symbol 'nents' in" failed to apply to 4.9-stable tree gregkh
2019-11-27 23:32 ` Shuah Khan [this message]
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=b3cb8295-cbb3-013c-dc75-1e56ddd0a8de@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=lkp@intel.com \
--cc=stable@vger.kernel.org \
--cc=suwan.kim027@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).