From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Daniel Mack <daniel@zonque.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Mark Brown <broonie@kernel.org>,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ASoC: sta32x: set ->component pointer in private struct" failed to apply to 4.14-stable tree
Date: Sun, 23 Dec 2018 13:02:17 +0100 [thread overview]
Message-ID: <20181223120216.GA32473@kroah.com> (raw)
In-Reply-To: <20181221232458.GG86645@sasha-vm>
On Fri, Dec 21, 2018 at 06:24:58PM -0500, Sasha Levin wrote:
> On Fri, Dec 21, 2018 at 02:10:39PM +0100, Daniel Mack wrote:
> > On 20/12/2018 10:48 PM, Sudip Mukherjee wrote:
> > > On Sun, Nov 11, 2018 at 06:29:26AM -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>.
> > >
> > > The attached backported patch will apply to 4.14-stable tree.
> > > But I will prefer to wait for Mark or Daniel to confirm that I have
> > > not done something foolish.
> >
> > Yes, LGTM.
>
> Queued for all but 3.18, thanks all.
It breaks the build on 4.4 and 4.9, so I've dropped it from there :(
thanks,
greg k-h
prev parent reply other threads:[~2018-12-23 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 14:29 FAILED: patch "[PATCH] ASoC: sta32x: set ->component pointer in private struct" failed to apply to 4.14-stable tree gregkh
2018-12-20 21:48 ` Sudip Mukherjee
2018-12-21 10:58 ` Mark Brown
2018-12-21 13:10 ` Daniel Mack
2018-12-21 23:24 ` Sasha Levin
2018-12-23 12:02 ` Greg KH [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=20181223120216.GA32473@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@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).