Message ID | CAPM=9ty6MLNc4qYKOAO3-eFDpQtm9hGPg9hPQOm4iRg_8MkmNw@mail.gmail.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [git,pull] drm for 5.5-rc1 | expand |
Hi Dave, On Thu, 28 Nov 2019 12:37:06 +1000 Dave Airlie <airlied@gmail.com> wrote: > > > And apparently nobody bothered to tell me about the semantic conflict > > with the media tree due to the changed calling convention of > > cec_notifier_cec_adap_unregister(). Didn't that show up in linux-next? > > I can see no mention of it, I've got > > Hans saying > > "This will only be a problem if a new CEC adapter driver is added to the media > subsystem for v5.5, but I am not aware of any plans for that." when I > landed that > in my tree, but I assume the ao-cec change in the media tree collided with it. > > But I hadn't seen any mention of it from -next before you mentioned it now. See https://lore.kernel.org/lkml/20191014111225.66b36035@canb.auug.org.au/
On Fri, 29 Nov 2019 at 07:55, Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > Hi Dave, > > On Thu, 28 Nov 2019 12:37:06 +1000 Dave Airlie <airlied@gmail.com> wrote: > > > > > And apparently nobody bothered to tell me about the semantic conflict > > > with the media tree due to the changed calling convention of > > > cec_notifier_cec_adap_unregister(). Didn't that show up in linux-next? > > > > I can see no mention of it, I've got > > > > Hans saying > > > > "This will only be a problem if a new CEC adapter driver is added to the media > > subsystem for v5.5, but I am not aware of any plans for that." when I > > landed that > > in my tree, but I assume the ao-cec change in the media tree collided with it. > > > > But I hadn't seen any mention of it from -next before you mentioned it now. > > See https://lore.kernel.org/lkml/20191014111225.66b36035@canb.auug.org.au/ Indeed, the misc team didn't remention that to me, when I pulled their tree, perhaps I should make them do so, not sure why my search yesterday failed to find this in my inbox. Thanks, Dave.
Hi Dave, On Fri, 29 Nov 2019 09:13:16 +1000 Dave Airlie <airlied@gmail.com> wrote: > > On Fri, 29 Nov 2019 at 07:55, Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > Hi Dave, > > > > On Thu, 28 Nov 2019 12:37:06 +1000 Dave Airlie <airlied@gmail.com> wrote: > > > > > > > And apparently nobody bothered to tell me about the semantic conflict > > > > with the media tree due to the changed calling convention of > > > > cec_notifier_cec_adap_unregister(). Didn't that show up in linux-next? > > > > > > I can see no mention of it, I've got > > > > > > Hans saying > > > > > > "This will only be a problem if a new CEC adapter driver is added to the media > > > subsystem for v5.5, but I am not aware of any plans for that." when I > > > landed that > > > in my tree, but I assume the ao-cec change in the media tree collided with it. > > > > > > But I hadn't seen any mention of it from -next before you mentioned it now. > > > > See https://lore.kernel.org/lkml/20191014111225.66b36035@canb.auug.org.au/ > > Indeed, the misc team didn't remention that to me, when I pulled their > tree, perhaps I should make them do so, not sure why my search > yesterday failed to find this in my inbox. It was form Oct 14 ... I should have resent it earlier this week (or last) as a reminder.