From: "Danilo Krummrich" <dakr@kernel.org>
To: "Laura Nao" <laura.nao@collabora.com>
Cc: <aliceryhl@google.com>, <airlied@gmail.com>, <simona@ffwll.ch>,
<ojeda@kernel.org>, <boqun@kernel.org>, <gary@garyguo.net>,
<bjorn3_gh@protonmail.com>, <lossin@kernel.org>,
<a.hindborg@kernel.org>, <tmgross@umich.edu>,
<boris.brezillon@collabora.com>,
<dri-devel@lists.freedesktop.org>,
<nouveau@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<rust-for-linux@vger.kernel.org>, <kernel@collabora.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>
Subject: Re: [PATCH v3 1/1] rust: drm: add FEAT_RENDER flag for render node support
Date: Fri, 29 May 2026 00:27:58 +0200 [thread overview]
Message-ID: <DIUNX2Y69INR.HKKUZE3OSEEY@kernel.org> (raw)
In-Reply-To: <20260507080914.95478-2-laura.nao@collabora.com>
On Thu May 7, 2026 at 10:09 AM CEST, Laura Nao wrote:
> diff --git a/drivers/gpu/drm/tyr/driver.rs b/drivers/gpu/drm/tyr/driver.rs
> index e20a5978eed6..f0c2d6e4db3a 100644
> --- a/drivers/gpu/drm/tyr/driver.rs
> +++ b/drivers/gpu/drm/tyr/driver.rs
> @@ -186,6 +186,7 @@ impl drm::Driver for TyrDrmDriver {
> type Object = drm::gem::shmem::Object<BoData>;
>
> const INFO: drm::DriverInfo = INFO;
> + const FEAT_RENDER: bool = true;
In general this should be two separate patches, one adding the feature and
another one using it in the driver.
But in this case it is minor, so fine to leave it as is.
next prev parent reply other threads:[~2026-05-28 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 8:09 [PATCH v3 0/1] DRM 'feature' support for DRM drivers Laura Nao
2026-05-07 8:09 ` [PATCH v3 1/1] rust: drm: add FEAT_RENDER flag for render node support Laura Nao
2026-05-28 22:27 ` Danilo Krummrich [this message]
2026-05-28 22:28 ` [PATCH v3 0/1] DRM 'feature' support for DRM drivers Danilo Krummrich
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=DIUNX2Y69INR.HKKUZE3OSEEY@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=kernel@collabora.com \
--cc=laura.nao@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
/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