From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Rahul Rameshbabu <sergeantsagara@protonmail.com>
Cc: rust-for-linux@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>
Subject: Re: [RFC PATCH 1/3] rust: drm: fix C header references in doc comments
Date: Mon, 18 Aug 2025 09:58:29 +0200 [thread overview]
Message-ID: <CANiq72ns_17Z8=T7eTyquPG-x4WEZ8W4wa8nXBpMv04hKqD5oA@mail.gmail.com> (raw)
In-Reply-To: <20250818050251.102399-3-sergeantsagara@protonmail.com>
On Mon, Aug 18, 2025 at 7:04 AM Rahul Rameshbabu
<sergeantsagara@protonmail.com> wrote:
>
> The Rust DRM abstractions would incorrectly reference headers using the
> non-existent path include/linux/drm. Correct the path to include/drm.
>
> Signed-off-by: Rahul Rameshbabu <sergeantsagara@protonmail.com>
> Fixes: 9a69570682b1 ("rust: drm: ioctl: Add DRM ioctl abstraction")
> Fixes: 07c9016085f9 ("rust: drm: add driver abstractions")
> Fixes: 1e4b8896c0f3 ("rust: drm: add device abstraction")
> Fixes: a98a73be9ee9 ("rust: drm: file: Add File abstraction")
> Fixes: c284d3e42338 ("rust: drm: gem: Add GEM object abstraction")
This is https://lore.kernel.org/rust-for-linux/20250730130716.3278285-3-ojeda@kernel.org/
Cheers,
Miguel
next prev parent reply other threads:[~2025-08-18 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 5:04 [RFC PATCH 0/3] Initial plumbing for implementing DRM connector APIs in Rust Rahul Rameshbabu
2025-08-18 5:04 ` [RFC PATCH 1/3] rust: drm: fix C header references in doc comments Rahul Rameshbabu
2025-08-18 7:58 ` Miguel Ojeda [this message]
2025-08-18 5:04 ` [RFC PATCH 2/3] rust: pci: fix incorrect platform " Rahul Rameshbabu
2025-08-18 5:04 ` [RFC PATCH 3/3] rust: drm: Introduce a Connector abstraction Rahul Rameshbabu
2025-08-18 8:23 ` [RFC PATCH 0/3] Initial plumbing for implementing DRM connector APIs in Rust Miguel Ojeda
2025-08-19 9:06 ` Maxime Ripard
2025-08-20 4:46 ` Rahul Rameshbabu
2025-08-27 6:57 ` Maxime Ripard
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='CANiq72ns_17Z8=T7eTyquPG-x4WEZ8W4wa8nXBpMv04hKqD5oA@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=lossin@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sergeantsagara@protonmail.com \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).