The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm for 5.5-rc1
Date: Fri, 29 Nov 2019 10:53:23 +1100	[thread overview]
Message-ID: <20191129105323.4ff56629@canb.auug.org.au> (raw)
In-Reply-To: <CAPM=9txFZ+sCXXV3WA0CtFjsmLrY7qziJqrGfr1h+5B-fsqWRA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]

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.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-11-28 23:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28  0:59 [git pull] drm for 5.5-rc1 Dave Airlie
2019-11-28  1:50 ` Linus Torvalds
2019-11-28  2:37   ` Dave Airlie
2019-11-28 21:55     ` Stephen Rothwell
2019-11-28 23:13       ` Dave Airlie
2019-11-28 23:53         ` Stephen Rothwell [this message]
2019-11-28  1:55 ` pr-tracker-bot

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=20191129105323.4ff56629@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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