All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Rename "struct fence" to "struct dma_fence"
Date: Thu, 20 Oct 2016 16:08:34 +0200	[thread overview]
Message-ID: <CAKMK7uH3B4amPHA1TojbOzEKQrjJqLNOoADVVkH2ObBcOWx5Mg@mail.gmail.com> (raw)
In-Reply-To: <20161020064747.7047-1-chris@chris-wilson.co.uk>

On Thu, Oct 20, 2016 at 8:47 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> 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 (and we wanted
> to wait until after the sw_sync destage), so hopefully it remains a good
> thing!
>
> I've pushed the patch to
>
> https://cgit.freedesktop.org/~ickle/linux-2.6/commit/?h=dma-fence&id=a4a27d87e4fccefb9f9d55f9c73ccab8f2ade3cc
>
> as I suspect it might be too large for the list.
>
> Highlights of the change:
>
>         struct fence -> struct dma_fence (and all fence*() to dma_fence*())
>         struct fence_array -> struct dma_fence_array
>
>         107 files changed, 1174 insertions(+), 1136 deletions(-)
>
> Mostly generated with the provided cocci spatch, but even with
> --include-headers it seemed to miss some headers, and I never quite
> worked out the substition commands for macros, so there is some grep and
> replace.

For merging I think the best would be to do a topic branch on top of
drm-next, with 4.9-rc2, drm-misc and drm-intel all pulled in. Topic
branch (and not drm-misc) so that we can rebase, and give 0day a few
days to crunch through all the combinatorial Kconfigs ...
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-10-20 14:08 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
2016-10-20 14:08 ` Daniel Vetter [this message]
2016-10-20 14:39 ` Rename "struct fence" to "struct dma_fence" 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=CAKMK7uH3B4amPHA1TojbOzEKQrjJqLNOoADVVkH2ObBcOWx5Mg@mail.gmail.com \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.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.