mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Kyungmin Park <kmpark@infradead.org>
Cc: Rob Clark <rob.clark@linaro.org>,
	linaro-dev@lists.linaro.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org
Subject: Re: Linux 3.4-rc1
Date: Mon, 2 Apr 2012 10:41:52 +0200	[thread overview]
Message-ID: <20120402084152.GA4612@phenom.ffwll.local> (raw)
In-Reply-To: <CAH9JG2VujPUQfJ=7nyqM90jzuf60qqNYVi4fN40F1SpDua75gg@mail.gmail.com>

On Mon, Apr 02, 2012 at 12:40:39PM +0900, Kyungmin Park wrote:
> On Mon, Apr 2, 2012 at 12:34 AM, Rob Clark <rob.clark@linaro.org> wrote:
> > On Sat, Mar 31, 2012 at 6:58 PM, Linus Torvalds
> > <torvalds@linux-foundation.org> wrote:
> >>  - drm dma-buf prime support. Dave Airlie sent me the pull request but
> >> didn't push very hard for it, it's in my "ok, I can still pull it for
> >> 3.4 if individual DRM driver people tell me that it will make their
> >> lives easier." So this is in limbo - I have nothing against it, but I
> >> won't pull unless I get a few people say "yes, please".
> >
> > yes, please :-)
> >
> > Note that the core drm dma-buf/prime support has already been reviewed
> > by a lot of folks, and tested with a few different drivers (exynos,
> > omapdrm, i915, nouveau, udl) with some driver support that could be
> > pushed for 3.5 cycle if the core support makes it in for 3.4 cycle.
> Yes, Please.
> 
> It's used for exynos display and multimedia.

Thirded.

There are a lot of loose pieces to juggle until we have everything in
place for buffer sharing (and quite a few of this involve contentious
topics). But this core piece for integrating dma-buf with drm here has
been acked/reviewd by all the relevant people and merging it would imo
greatly help in wiring up all the other loose ends.

Cheers, Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-04-02  8:42 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-31 23:58 Linus Torvalds
2012-04-01  0:09 ` Christoph Hellwig
2012-04-01  1:46 ` Shea Levy
2012-04-01  3:11   ` Linus Torvalds
2012-04-01  1:48 ` Shea Levy
2012-04-01  2:07   ` Shea Levy
2012-04-01  8:34 ` Ingo Molnar
2012-04-01 12:03 ` Stephen Rothwell
2012-04-01 19:19   ` David Miller
2012-04-01 13:14 ` linux-next stats (Was: Linux 3.4-rc1) Stephen Rothwell
2012-04-01 15:34 ` Linux 3.4-rc1 Rob Clark
2012-04-02  3:40   ` Kyungmin Park
2012-04-02  8:41     ` Daniel Vetter [this message]
2012-04-04 12:24       ` Subash Patel
2012-04-04 12:33         ` Anca Emanuel
2012-04-05  7:41           ` Marek Szyprowski
2012-04-02 12:31   ` Alex Deucher
2012-04-02  9:15 ` Artem Bityutskiy
2012-04-02  9:20   ` Shubhrajyoti Datta
2012-04-02 15:48 ` Linus Walleij
2012-04-02 20:30 ` Carlos Chinea
2012-04-03  2:57 ` Kyungmin Park
2012-04-03  3:57   ` Linus Torvalds
2012-04-03  6:29     ` Hiroshi Doyu
2012-04-03  9:07   ` Arnd Bergmann
2012-04-03 14:58     ` Jerome Glisse
2012-04-03 15:35       ` Arnd Bergmann
2012-04-03 19:26     ` Krishna Reddy
2012-04-04 12:10       ` Anca Emanuel

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=20120402084152.GA4612@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kmpark@infradead.org \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.clark@linaro.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

Powered by JetHome