rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: JaimeFine <jaimefine6@gmail.com>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	ojeda@kernel.org
Subject: Re: [PATCH] rust: auxiliary: Fix 'initialialized' typo
Date: Mon, 15 Sep 2025 14:14:59 +0200	[thread overview]
Message-ID: <2025091515-prison-eats-cb1e@gregkh> (raw)
In-Reply-To: <20250915120235.1942-1-jaimefine6@gmail.com>

On Mon, Sep 15, 2025 at 08:02:27PM +0800, JaimeFine wrote:
> From: Jaime Fine <jaimefine6@gmail.com>
> 
> Suggested-by: onur-ozkan

What specific "typo" is being changed here?

> Link: https://github.com/Rust-for-Linux/linux/issues/1187
> Signed-off-by: Jaime Fine <jaimefine6@gmail.com>
> ---
>  rust/kernel/auxiliary.rs | 357 +++++++++++++++++++++++++++++++++++++++
>  1 file changed, 357 insertions(+)
>  create mode 100644 rust/kernel/auxiliary.rs
> 
> diff --git a/rust/kernel/auxiliary.rs b/rust/kernel/auxiliary.rs
> new file mode 100644
> index 0000000..3626072
> --- /dev/null
> +++ b/rust/kernel/auxiliary.rs

You added a whole file, you did not modify an existing one :(

Also, please use scripts/get_maintainer.pl to determine who to send
patches to.

thanks,

greg k-h

  reply	other threads:[~2025-09-15 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15 12:02 [PATCH] rust: auxiliary: Fix 'initialialized' typo JaimeFine
2025-09-15 12:14 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-16 12:41 [PATCH] rust: auxiliary: fix "initialialized" typo JaimeF
2025-09-16 12:46 ` Greg KH
     [not found]   ` <CAL-mriLdm9NiNBvAqV3BEKVELJ1B1FsZtZL=NOsM_2RipoU0FA@mail.gmail.com>
2025-09-16 13:12     ` Greg KH
2025-09-16 16:31       ` Ira Weiny
2025-09-16 16:19 ` 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=2025091515-prison-eats-cb1e@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jaimefine6@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).