From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: ojeda@kernel.org, alex.gaynor@gmail.com,
rust-for-linux@vger.kernel.org, boqun.feng@gmail.com,
gary@garyguo.net, bjorn3_gh@protonmail.com,
benno.lossin@proton.me, a.hindborg@kernel.org,
aliceryhl@google.com, tmgross@umich.edu,
Luis Chamberlain <mcgrof@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Daniel Gomez <da.gomez@samsung.com>,
linux-modules@vger.kernel.org
Subject: Re: [PATCH v1] rust: module: place cleanup_module() in .exit.text section
Date: Fri, 9 May 2025 09:27:55 +0200 [thread overview]
Message-ID: <CANiq72n_ySP_K_2m28C9L3FOqRtqn8ohkWqtX1Fe9L0szGxSzA@mail.gmail.com> (raw)
In-Reply-To: <20250509.131622.164788613577030480.fujita.tomonori@gmail.com>
On Fri, May 9, 2025 at 6:16 AM FUJITA Tomonori
<fujita.tomonori@gmail.com> wrote:
>
> Do I need to update the commit message and submit a v2 of this patch?
I think it is OK, i.e. we can add what you wrote above when applying
(though it always helps to do it on your side when it is a non-trivial
change).
By the way, Cc'ing MODULE SUPPORT in case they want to say something
(or even take it themselves).
Thanks!
Cheers,
Miguel
next prev parent reply other threads:[~2025-05-09 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 4:45 [PATCH v1] rust: module: place cleanup_module() in .exit.text section FUJITA Tomonori
2025-03-08 5:23 ` Jarkko Sakkinen
2025-03-08 5:32 ` Boqun Feng
2025-03-08 5:39 ` FUJITA Tomonori
2025-03-24 19:18 ` Miguel Ojeda
2025-05-09 4:16 ` FUJITA Tomonori
2025-05-09 7:27 ` Miguel Ojeda [this message]
2025-05-22 9:47 ` Miguel Ojeda
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=CANiq72n_ySP_K_2m28C9L3FOqRtqn8ohkWqtX1Fe9L0szGxSzA@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=da.gomez@samsung.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=samitolvanen@google.com \
--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).