From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: alexander.levin@verizon.com
Cc: Mark Brown <broonie@kernel.org>,
"codekipper@gmail.com" <codekipper@gmail.com>,
"maxime.ripard@free-electrons.com"
<maxime.ripard@free-electrons.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"stable-commits@vger.kernel.org" <stable-commits@vger.kernel.org>
Subject: Re: Patch "ASoC: sunxi: Add bindings for sun8i to SPDIF" has been added to the 4.9-stable tree
Date: Mon, 13 Nov 2017 13:53:00 +0100 [thread overview]
Message-ID: <20171113125300.GB29947@kroah.com> (raw)
In-Reply-To: <20171111202416.au2epogqwadr2qvt@sasha-lappy>
On Sat, Nov 11, 2017 at 08:24:18PM +0000, alexander.levin@verizon.com wrote:
> On Fri, Nov 10, 2017 at 04:44:00PM +0000, Mark Brown wrote:
> >On Fri, Nov 10, 2017 at 05:36:32PM +0100, gregkh@linuxfoundation.org wrote:
> >> On Fri, Nov 10, 2017 at 04:04:22PM +0000, alexander.levin@verizon.com wrote:
> >
> >> > - 96e53c41e1f81c9e9d1ce38d3f28b95668b71dcf - just dead code removal,
> >> > avoids conflicts later.
> >
> >> This commit claims the hardware is now supported by a different driver.
> >> Is that support in 4.9? I couldn't figure it out :(
>
> >From what I can tell its that way since 3.11.
>
> >I suspect this isn't worth the effort - it's defintely more than a
> >simple quirk anyway.
>
> But as Mark points out, this is getting a bit too complicated and
> risky.
Ok, now dropped, thanks.
greg k-h
prev parent reply other threads:[~2017-11-13 12:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 9:09 Patch "ASoC: sunxi: Add bindings for sun8i to SPDIF" has been added to the 4.9-stable tree gregkh
2017-11-09 11:07 ` Mark Brown
2017-11-09 16:09 ` Levin, Alexander (Sasha Levin)
2017-11-09 16:17 ` Mark Brown
2017-11-09 16:28 ` Levin, Alexander (Sasha Levin)
2017-11-10 13:34 ` gregkh
2017-11-10 16:04 ` alexander.levin
2017-11-10 16:36 ` gregkh
2017-11-10 16:44 ` Mark Brown
2017-11-11 20:24 ` alexander.levin
2017-11-13 12:53 ` gregkh [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=20171113125300.GB29947@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@verizon.com \
--cc=broonie@kernel.org \
--cc=codekipper@gmail.com \
--cc=maxime.ripard@free-electrons.com \
--cc=stable-commits@vger.kernel.org \
--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 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.