From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>
Cc: linux-next@vger•kernel.org,
Thomas Hellstrom <thellstrom@vmware•com>,
Richard Purdie <rpurdie@linux•intel.com>,
Ben Gamari <bgamari@gmail•com>, Eric Anholt <eric@anholt•net>,
Dave Airlie <airlied@linux•ie>
Subject: Re: linux-next: manual merge of the staging tree with the drm tree
Date: Fri, 20 Mar 2009 16:42:14 +1100 [thread overview]
Message-ID: <20090320164214.c625a4c6.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090320051501.GB3698@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
Hi Greg,
On Thu, 19 Mar 2009 22:15:01 -0700 Greg KH <greg@kroah•com> wrote:
>
> > However, I do need to wonder why changes to drivers/gpu are appearing in
> > the staging tree - I assumed that its updates would be restricted to the
> > drivers/staging directory (as much as possible).
>
> There is a driver in the staging directory that needs these drm core
> changes. I've posted these to David and the drm list and lkml, and we
> are currently discussing their future. If David ends up rejecting them,
> I'll drop them from my tree.
Right. I need more time to read LKML :-(
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-20 5:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 4:38 linux-next: manual merge of the staging tree with the drm tree Stephen Rothwell
2009-03-20 5:15 ` Greg KH
2009-03-20 5:42 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-19 4:22 Stephen Rothwell
2016-06-20 4:33 Stephen Rothwell
2016-07-25 6:29 ` Stephen Rothwell
2018-11-20 2:16 Stephen Rothwell
2018-11-20 8:54 ` Greg KH
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=20090320164214.c625a4c6.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=airlied@linux$(echo .)ie \
--cc=bgamari@gmail$(echo .)com \
--cc=eric@anholt$(echo .)net \
--cc=greg@kroah$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rpurdie@linux$(echo .)intel.com \
--cc=thellstrom@vmware$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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