From: Steven Rostedt <rostedt@goodmis.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Dave Airlie <airlied@gmail.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Including drm-intel tree to linux-next
Date: Thu, 14 Feb 2013 09:28:24 -0500 [thread overview]
Message-ID: <1360852104.23152.45.camel@gandalf.local.home> (raw)
In-Reply-To: <20130214141953.GA5746@pd.tnic>
On Thu, 2013-02-14 at 15:19 +0100, Borislav Petkov wrote:
> On Thu, Feb 14, 2013 at 03:12:02PM +0100, Daniel Vetter wrote:
> > Hi Steven,
> >
> > Since about a year ago we've switched drm/i915 to buffer around 2
> > weeks worth of patches so that we can do decent QA before breaking
> > everyone's tree when things land in Dave's drm-next. But that also
> > means we'll miss out a bit in the integration testing -next provides,
> > which did hurt a bit in recent efforts. Hence can you please include
> >
> > git://people.freedesktop.org/~danvet/drm-intel drm-intel-next-queued
> >
> > into linux-next? Probably best to merge it after drm-next. Note that
> > drm-intel-next are the QA'ed chunks I send off to Dave. Also, any
> > mailing lists I'm supposed to follow? And if possible please cc
> > intel-gfx@lists.freedesktop.org besides dri-devel/lkml when conflicts
> > with that tree pop up (you won't get moderation spam any more, we've
> > fixed that up).
>
> I think you want to send this here to Stephen Rothwell. CCed.
>
This is why I tell people to call me Steve or Steven, but never Stephen,
otherwise people might confuse me with one of the Stephens that also do
kernel development.
Note, this is not the first time I've been confused with someone else.
So don't feel bad ;-)
-- Steve
next prev parent reply other threads:[~2013-02-14 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 14:12 Daniel Vetter
2013-02-14 14:19 ` Borislav Petkov
2013-02-14 14:28 ` Steven Rostedt [this message]
2013-02-14 15:33 ` Daniel Vetter
2013-02-14 23:27 ` Stephen Rothwell
2013-02-15 9:43 ` Daniel Vetter
2013-02-15 14:26 ` Stephen Rothwell
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=1360852104.23152.45.camel@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=airlied@gmail.com \
--cc=bp@alien8.de \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®