From: "Danilo Krummrich" <dakr@kernel.org>
To: "Abhinav Ananthu" <abhinav.ogl@gmail.com>
Cc: <gregkh@linuxfoundation.org>, <david.m.ertman@intel.com>,
<ira.weiny@intel.com>, <leon@kernel.org>, <ojeda@kernel.org>,
<alex.gaynor@gmail.com>, <boqun.feng@gmail.com>,
<gary@garyguo.net>, <bjorn3_gh@protonmail.com>,
<lossin@kernel.org>, <a.hindborg@kernel.org>,
<aliceryhl@google.com>, <tmgross@umich.edu>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rust: auxiliary: Use `c_` types from prelude instead of
Date: Tue, 12 Aug 2025 19:21:23 +0200 [thread overview]
Message-ID: <DC0MEWPXV9NJ.3HQEPBFID0YD9@kernel.org> (raw)
In-Reply-To: <20250812075109.4099-1-abhinav.ogl@gmail.com>
On Tue Aug 12, 2025 at 9:51 AM CEST, Abhinav Ananthu wrote:
> Update auxiliary FFI callback signatures to reference the `c_` types
> provided by the kernel prelude, rather than accessing them via
> `kernel::ffi::`.
>
> Signed-off-by: Abhinav Ananthu <abhinav.ogl@gmail.com>
This looks good now, I'll later on pick this one up.
One additional note, when sending updates on previous patches, please make sure
to increase the version number of the patch, see also [1].
Also, please add a note about what changes you made between versions below the
'---' line of the commit.
- Danilo
[1] https://docs.kernel.org/process/submitting-patches.html#subject-line
next prev parent reply other threads:[~2025-08-12 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 7:51 [PATCH] rust: auxiliary: Use `c_` types from prelude instead of Abhinav Ananthu
2025-08-12 8:27 ` Greg KH
2025-08-12 17:21 ` Danilo Krummrich [this message]
2025-08-15 18:08 ` Danilo Krummrich
-- strict thread matches above, loose matches on Subject: below --
2025-08-12 3:54 herculoxz
2025-08-12 6:31 ` Greg KH
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=DC0MEWPXV9NJ.3HQEPBFID0YD9@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=abhinav.ogl@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=david.m.ertman@intel.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).