dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joonyoung Shim <jy0922.shim@samsung.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 0/3] drm/cma: use prime helpers instead GEM CMA specific dma_buf functionality
Date: Mon, 08 Jul 2013 18:14:49 +0900	[thread overview]
Message-ID: <51DA8309.8010504@samsung.com> (raw)
In-Reply-To: <2060924.EWeBKl2sJ9@avalon>

On 07/05/2013 10:03 PM, Laurent Pinchart wrote:
> Hi Joonyoung,
>
> On Friday 05 July 2013 15:30:25 Joonyoung Shim wrote:
>> On 07/05/2013 02:38 PM, Dave Airlie wrote:
>>> On Thu, Jul 4, 2013 at 5:14 PM, Joonyoung Shim wrote:
>>>> On 07/04/2013 07:11 AM, Laurent Pinchart wrote:
>>>>> On Friday 28 June 2013 14:24:43 Joonyoung Shim wrote:
>>>>>> Hello,
>>>>>>
>>>>>> This is the second version patchset.
>>>>>>
>>>>>> GEM CMA supports dma_buf but it needs GEM CMA specific functionality
>>>>>> for dma_buf. We can use prime helpers for dma_buf by commit
>>>>>> 89177644a7b6306e6084a89eab7e290f4bfef397 "drm: add prime helpers", so
>>>>>> this patchset is to replace from using GEM CMA specific functions to
>>>>>> using prime helpers.
>>>>>>
>>>>>>
>>>>>> To Laurent,
>>>>>>
>>>>>> It is merged a patch to cache mapping from DRM Prime, can this patchset
>>>>>> get your ack?
>>>>> There you go (and sorry for the late reply)
>>>>>
>>>>> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>>>>>
>>>>> By the way, between the initial version of the GEM CMA PRIME patch and
>>>>> the version that got merged in v3.10, commit
>>>>> 011c2282c74db120f01a8414edc66c3f217f5511 ("drm: prime: fix refcounting
>>>>> on the dmabuf import error path") was introduced. The GEM CMA PRIME code
>>>>> in v3.10 thus has a refcounting bug :-(
>>>>>
>>>>> Should this patch set go to -stable, or should we cook up a special fix
>>>>> ?
>>>> I'm not sure it's better to choose which way.
>>>>
>>>> Dave, how we should do about that problem?
>>> I think a special fix for stable once we get these merged to Linus.
>> OK, i will post a patch for a special fix.
> Thank you.
>
> We need to fix the problem for v3.11 as well, by applying either this set or
> the fix you have just sent. I have no strong preference regarding which
> patches to pick.
>

I also don't care, but i can report v3 patchset based on a patch for a
special fix for commit consistency.

      reply	other threads:[~2013-07-08  9:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28  5:24 [PATCH v2 0/3] drm/cma: use prime helpers instead GEM CMA specific dma_buf functionality Joonyoung Shim
2013-07-03 22:11 ` Laurent Pinchart
2013-07-04  7:14   ` Joonyoung Shim
2013-07-05  5:38     ` Dave Airlie
2013-07-05  6:30       ` Joonyoung Shim
2013-07-05 13:03         ` Laurent Pinchart
2013-07-08  9:14           ` Joonyoung Shim [this message]

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=51DA8309.8010504@samsung.com \
    --to=jy0922.shim@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --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