From: Gustavo Padovan <gustavo.padovan@collabora.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Sean Paul" <seanpaul@google.com>,
"Christian König" <christian.koenig@amd.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
"alexander.deucher@amd.com" <alexander.deucher@amd.com>,
"Gustavo Padovan" <gustavo.padovan@collabora.co.uk>
Subject: Re: [RFC] dma-buf: Rename struct fence to dma_fence
Date: Wed, 13 Jul 2016 17:19:40 -0300 [thread overview]
Message-ID: <20160713201940.GD7619@joana> (raw)
In-Reply-To: <CAKMK7uFMbtwugrvsGTwPXat8QnH21CPyN=zM+ZPjeuAR3DzhtA@mail.gmail.com>
2016-07-13 Daniel Vetter <daniel@ffwll.ch>:
> On Wed, Jul 13, 2016 at 03:10:45PM +0100, Chris Wilson 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.
> >
> > As an indication of the scale of the flag day:
> >
> > 91 files changed, 904 insertions(+), 880 deletions(-)
> >
> > with the greatest victim being amdgpu.
> >
> > Just the highlights shown below.
>
> +1 on dma_fence, for more consistency with dma_buf and everything else
> dma_*. I think if we land this right before/after 4.8-rc1 through the drm
> tree it should be minimally invasive. Worst case we'll have a fun merge
> between drm.git and drm-intel.git (since drm-intel-next-queued doesn't get
> closed while the merge window is open).
+1 from me, we just need to make sure we don't create any merge issue.
Gustavo
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-07-13 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 14:10 [RFC] dma-buf: Rename struct fence to dma_fence Chris Wilson
2016-07-13 14:46 ` Daniel Vetter
2016-07-13 15:07 ` Sean Paul
2016-07-13 15:19 ` Sumit Semwal
2016-07-13 20:19 ` Gustavo Padovan [this message]
2016-07-13 14:54 ` Inki Dae
2016-07-13 15:12 ` Chris Wilson
2016-07-13 15:12 ` Emil Velikov
2016-07-13 15:55 ` Christian König
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=20160713201940.GD7619@joana \
--to=gustavo.padovan@collabora.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=seanpaul@google.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