From: Alan Cox <alan@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: gma500: Kill the GEM glue layer
Date: Thu, 23 Aug 2012 11:52:06 +0100 [thread overview]
Message-ID: <20120823115206.153f01b7@bob.linux.org.uk> (raw)
In-Reply-To: <7356048.5QipIapJLh@avalon>
On Thu, 23 Aug 2012 12:03:59 +0200
Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
> Hi Alan,
>
> On Tuesday 17 July 2012 17:21:06 Alan Cox wrote:
> > On Tue, 17 Jul 2012 17:09:25 +0200 Laurent Pinchart wrote:
> > > On Wednesday 16 May 2012 16:10:37 Alan Cox wrote:
> > > > On Wed, 16 May 2012 16:59:44 +0200 Laurent Pinchart wrote:
> > > > > The private gem_create_mmap_offset() function is now
> > > > > implemented in the DRM core as drm_gem_create_mmap_offset().
> > > > > Use it and kill the private copy.
> > > >
> > > > That was always then plan so yes - I'll fold this into my tree
> > > > and test it.
> > >
> > > Any update ?
> >
> > Sorry it fell off the bottom of the job list. I'll do it right now
> > so it doesn't escape
>
> I still can't find the patch in drm-next. Does it have a bad tendency
> to fell off ? :-)
I sent to Dave along with the mode setting fixes and DP/eDP support.
None of them are yet in the tree but I've not re-sent again as Dave
seemed to be busy to trying to mend the -rc tree.
Alan
next prev parent reply other threads:[~2012-08-23 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 14:59 [PATCH] drm: gma500: Kill the GEM glue layer Laurent Pinchart
2012-05-16 15:10 ` Alan Cox
2012-07-17 15:09 ` Laurent Pinchart
2012-07-17 16:21 ` Alan Cox
2012-07-17 16:12 ` Laurent Pinchart
2012-08-23 10:03 ` Laurent Pinchart
2012-08-23 10:52 ` Alan Cox [this message]
2012-08-23 23:30 ` Dave Airlie
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=20120823115206.153f01b7@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
/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