From: Ira Weiny <ira.weiny@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>, Jaime Fine <jaimefine6@gmail.com>
Cc: <ojeda@kernel.org>, <alex.gaynor@gmail.com>,
<david.m.ertman@intel.com>, <ira.weiny@intel.com>,
<leon@kernel.org>, <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>,
onur-ozkan <work@onurozkan.dev>
Subject: Re: [PATCH] rust: auxiliary: fix "initialialized" typo
Date: Tue, 16 Sep 2025 11:31:00 -0500 [thread overview]
Message-ID: <68c990c49ffb2_17e96f2947b@iweiny-mobl.notmuch> (raw)
In-Reply-To: <2025091642-goofiness-camper-683a@gregkh>
Greg KH wrote:
> On Tue, Sep 16, 2025 at 09:01:49PM +0800, Jaime Fine wrote:
> > Fixed!
>
> Please slow down and relax. Take a day at the very least between patch
> submissions to fully read the responses and then do a new version.
> There is no rush here.
+1
And perhaps check out the b4 tool[*] which can help with tracking changes
to a patch set and help with patch submissions.
[*] https://git.kernel.org/pub/scm/utils/b4/b4.git
See the prep option.
Ira
next prev parent reply other threads:[~2025-09-16 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2025-09-16 16:19 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2025-09-15 12:02 [PATCH] rust: auxiliary: Fix 'initialialized' typo JaimeFine
2025-09-15 12:14 ` 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=68c990c49ffb2_17e96f2947b@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=a.hindborg@kernel.org \
--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=gregkh@linuxfoundation.org \
--cc=jaimefine6@gmail.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 \
--cc=work@onurozkan.dev \
/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).