All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] dma-buf: Rename struct fence to dma_fence
Date: Fri, 21 Oct 2016 14:22:53 +0200	[thread overview]
Message-ID: <20161021122253.GX20761@phenom.ffwll.local> (raw)
In-Reply-To: <CAO_48GH_507Pi8y-w6nEnbzvPfA=NRdYeEkoyQyit--rED7j7g@mail.gmail.com>

On Thu, Oct 20, 2016 at 10:45:34PM +0530, Sumit Semwal wrote:
> Hi Chris,
> 
> Thanks for the patch!
> 
> On 20 October 2016 at 17:38, Gustavo Padovan <gustavo@padovan.org> wrote:
> > 2016-10-20 Chris Wilson <chris@chris-wilson.co.uk>:
> >
> >> I plan to usurp the short name of struct fence for a core kernel struct,
> >> and so I need to rename the specialised fence/timeline for DMA
> >> operations to make room.
> >>
> >> A consensus was reached in
> >> https://lists.freedesktop.org/archives/dri-devel/2016-July/113083.html
> >> that making clear this fence applies to DMA operations was a good thing.
> >> Since then the patch has grown a bit as usage increases, so hopefully it
> >>  (
> >>  ...
> >>  )
> >>
> >> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> 
> Acked-by: Sumit Semwal <sumit.semwal@linaro.org>
> 
> Daniel,
> As we agreed, we should perhaps take it via the drm tree?

Yeah, see my other reply. After -rc2 is out I'll send a drm-misc and
drm-intel pull to Dave, and then I'll ask Chris to regen the patch on top
of Dave's drm-next and stuff that into a topic branch. Since we don't yet
have users outside of drm that's probably the easiest (and only) way to
land this.
-Daniel

> 
> >
> > Reviewed-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> >
> > Gustavo
> >
> 
> Best regards,
> Sumit.
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-10-21 12:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20  6:47 Rename "struct fence" to "struct dma_fence" Chris Wilson
2016-10-20  6:47 ` [PATCH] dma-buf: Rename struct fence to dma_fence Chris Wilson
2016-10-20  7:48   ` Christian König
2016-10-20 12:08   ` Gustavo Padovan
2016-10-20 17:15     ` Sumit Semwal
2016-10-21 12:22       ` Daniel Vetter [this message]
2016-10-20 14:08 ` Rename "struct fence" to "struct dma_fence" Daniel Vetter
2016-10-20 14:39 ` Sean Paul
2016-10-20 14:57   ` Chris Wilson
2016-10-20 15:03     ` Sean Paul
2016-10-25  9:25 ` [PATCH v2] dma-buf: Rename struct fence to dma_fence Chris Wilson
2016-10-25 10:21   ` Daniel Vetter
2016-10-25 11:32   ` [PATCH v3] " Chris Wilson
2016-10-25 12:00   ` [PATCH v4] " Chris Wilson
2016-10-25 12:49     ` Daniel Vetter
2016-10-25 10:16 ` ✗ Fi.CI.BAT: warning for " Patchwork
2016-10-25 12:16 ` ✓ Fi.CI.BAT: success for dma-buf: Rename struct fence to dma_fence (rev2) Patchwork
2016-10-25 12:46 ` ✗ Fi.CI.BAT: warning for dma-buf: Rename struct fence to dma_fence (rev3) Patchwork

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=20161021122253.GX20761@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=sumit.semwal@linaro.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.