From: Philipp Stanner <phasta@mailbox.org>
To: "Philipp Stanner" <phasta@kernel.org>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Russell King" <linux+etnaviv@armlinux.org.uk>,
"Christian Gmeiner" <christian.gmeiner@gmail.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>
Cc: etnaviv@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/etnaviv: etnaviv_fence: Put base class first
Date: Fri, 30 Oct 2026 11:37:48 +0100 [thread overview]
Message-ID: <ec1799db63823edadc573cd162e721d60fc87bb6.camel@mailbox.org> (raw)
In-Reply-To: <20261028103129.1036380-2-phasta@kernel.org>
On Wed, 2026-10-28 at 11:31 +0100, Philipp Stanner wrote:
> struct etnaviv_fence contains a struct dma_fence, which is its base
> class. The base class should always be the first member of a class.
>
> This allows for removing a deprecated callback in a subsequent patch.
>
> Make struct dma_fence base the first member of struct etnaviv_fence.
Applied this and the following one to drm-misc-next
Thx guys
prev parent reply other threads:[~2026-10-30 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 10:31 Philipp Stanner
2026-10-28 10:31 ` [PATCH 2/2] drm/etnaviv: Remove deprecated fence_ops->release() Philipp Stanner
2026-10-29 10:30 ` Lucas Stach
2026-10-28 10:34 ` [PATCH 1/2] drm/etnaviv: etnaviv_fence: Put base class first Christian König
2026-10-29 10:29 ` Lucas Stach
2026-10-30 10:37 ` Philipp Stanner [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=ec1799db63823edadc573cd162e721d60fc87bb6.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=airlied@gmail.com \
--cc=christian.gmeiner@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=l.stach@pengutronix.de \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=phasta@kernel.org \
--cc=simona@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®