linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: herculoxz <abhinav.ogl@gmail.com>
Cc: 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,
	dakr@kernel.org, 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 08:31:11 +0200	[thread overview]
Message-ID: <2025081228-deskwork-runaround-3c99@gregkh> (raw)
In-Reply-To: <20250812035420.8123-1-abhinav.ogl@gmail.com>

On Tue, Aug 12, 2025 at 09:24:21AM +0530, herculoxz wrote:
> From: Abhinav Ananthu <abhinav.ogl@gmail.com>
> 
>  Update auxiliary FFI callback signatures to reference the `c_` types
>  provided by the kernel prelude, rather than accessing them via
>  `kernel::ffi::`.

Why is this indented?

Also, note that your "From:" line in your email client doesn't reflect
your name here.  That might be fine, but it's a bit odd and triggers my
checks.

thanks,

greg k-h

  reply	other threads:[~2025-08-12  6:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-12  3:54 [PATCH] rust: auxiliary: Use `c_` types from prelude instead of herculoxz
2025-08-12  6:31 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-12  7:51 Abhinav Ananthu
2025-08-12  8:27 ` Greg KH
2025-08-12 17:21 ` Danilo Krummrich
2025-08-15 18:08 ` 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=2025081228-deskwork-runaround-3c99@gregkh \
    --to=gregkh@linuxfoundation.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=dakr@kernel.org \
    --cc=david.m.ertman@intel.com \
    --cc=gary@garyguo.net \
    --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).