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