stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Levin, Alexander (Sasha Levin)" <alexander.levin@one.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: Fri, 10 Nov 2017 14:34:31 +0100	[thread overview]
Message-ID: <20171110133431.GC30012@kroah.com> (raw)
In-Reply-To: <20171109162803.ofzpnajnhqnsejhr@sasha-lappy>

On Thu, Nov 09, 2017 at 04:28:05PM +0000, Levin, Alexander (Sasha Levin) wrote:
> On Thu, Nov 09, 2017 at 04:17:33PM +0000, Mark Brown wrote:
> >On Thu, Nov 09, 2017 at 04:09:12PM +0000, Levin, Alexander (Sasha Levin) wrote:
> >> On Thu, Nov 09, 2017 at 11:07:44AM +0000, Mark Brown wrote:
> >
> >> >This doesn't seem like a good idea - note how the changelog says that
> >> >the transmit FIFO is at a different address, I'd expect this means that
> >> >people won't be able to use the new compatible without a corresponding
> >> >code change.
> >
> >> Interesting. I keep trying to automate DT patch selection to deal with
> >> issues as this, but it seems like there is always something...
> >
> >> I agree with Mark. I think it would make sense to pick 1bd92af877 as
> >> well to deal with this issue.
> >
> >Yeah, if they both go in together it's fine by me (though it's a little
> >more than just a device ID).
> 
> It's a quirk too :)

Ok, but 1bd92af877 does not apply cleanly (or even not cleanly) to 4.9,
can someone provide me a backport?

thanks,

greg k-h

  reply	other threads:[~2017-11-10 13:34 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 [this message]
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

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=20171110133431.GC30012@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.levin@one.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 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).