All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Thomas Hellström" <thomas@shipmail.org>
Cc: Dave Airlie <airlied@gmail.com>, David Airlie <airlied@linux.ie>,
	Thomas Hellstrom <thellstrom@vmware.com>,
	dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	Richard Purdie <rpurdie@linux.intel.com>
Subject: Re: [patch 0/5] Intel Poulsbo/Morrestown DRM driver and DRM core changes
Date: Thu, 19 Mar 2009 13:11:36 -0700	[thread overview]
Message-ID: <20090319201136.GB17094@kroah.com> (raw)
In-Reply-To: <49C21B0B.4060809@shipmail.org>

On Thu, Mar 19, 2009 at 11:14:35AM +0100, Thomas Hellström wrote:
>> First off, the non-staging patches need more complete changelog entries,
>> a bit of meaning goes a long way. I'll ack them if they are documented and
>> make sense. The unlocked ioctl hook makes sense to me at least!
>>   
>
> For the non-staging patches, (which also sit in the modesetting-newttm 
> tree), I can add some more elaborate comments. However I think all of
> them are targeted to support functionality for TTM, so unless the TTM
> code goes into staging or mainstream, there is little point in merging
> them to core drm before other drivers find them useful.
>
> Although I see the patch adding TTM is including some backwards
> compatibility defines (In particular the PAT compat stuff) that needs
> to be stripped.

Great, care to respin it and send it to me?

thanks,

greg k-h

  parent reply	other threads:[~2009-03-19 20:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090319035834.875839585@mini.kroah.org>
2009-03-19  4:08 ` [patch 0/5] Intel Poulsbo/Morrestown DRM driver and DRM core changes Greg KH
2009-03-19  4:08   ` [patch 1/5] drm: Split out the mm declarations in a separate header. Add atomic operations Greg KH
2009-03-19  4:08   ` [patch 4/5] drm: Add unlocked IOCTL functionality from the drm repo Greg KH
2009-03-19  4:08   ` [patch 3/5] drm: Export hash table functionality Greg KH
2009-03-19  4:08   ` [patch 2/5] drm: Add a tracker for global objects Greg KH
2009-03-19  6:48   ` [patch 0/5] Intel Poulsbo/Morrestown DRM driver and DRM core changes Dave Airlie
2009-03-19 10:14     ` Thomas Hellström
2009-03-19 10:39       ` Alan Cox
2009-03-19 20:13         ` Greg KH
2009-03-19 20:11       ` Greg KH [this message]
2009-03-19 20:40         ` Thomas Hellström
2009-03-20  0:23           ` Greg KH
2009-03-20 14:17             ` Thomas Hellström
2009-03-19 10:43     ` Richard Purdie
2009-03-19 20:10     ` Greg KH
2009-03-19 16:03   ` Sindhudweep Sarkar
2009-03-19 16:27     ` Greg KH
2009-03-19 18:11       ` Sindhudweep Sarkar
2009-03-19 20:14         ` Greg KH
2009-03-19 18:53       ` Matthew Garrett
2009-03-19 19:02         ` Greg KH
2009-03-19 19:05           ` Matthew Garrett
2009-03-19 19:20             ` Greg KH
2009-03-20  6:08       ` Daniel Stone
2009-03-20 14:53         ` Greg KH
2009-03-20 15:00           ` Alan Cox
2009-03-20 15:50             ` Greg KH
2009-03-20 16:59               ` Thomas Hellström
2009-03-19 17:12     ` Richard Purdie
2009-03-19 20:15       ` Corbin Simpson
2009-03-19 21:14         ` Sindhudweep Sarkar
2009-03-21  2:39   ` 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=20090319201136.GB17094@kroah.com \
    --to=greg@kroah.com \
    --cc=airlied@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@linux.intel.com \
    --cc=thellstrom@vmware.com \
    --cc=thomas@shipmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.