From: Greg KH <greg@kroah.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Miguel Ojeda <ojeda@kernel.org>,
stable@vger.kernel.org, Benno Lossin <benno.lossin@proton.me>,
Alice Ryhl <aliceryhl@google.com>,
Andreas Hindborg <a.hindborg@kernel.org>
Subject: Re: [PATCH 6.6.y] rust: init: fix `Zeroable` implementation for `Option<NonNull<T>>` and `Option<Box<T>>`
Date: Tue, 18 Mar 2025 14:21:53 +0100 [thread overview]
Message-ID: <2025031810-untoasted-email-5a46@gregkh> (raw)
In-Reply-To: <CANiq72=vBzBYkq617zpa2StEN9PYshG3cVPKjqC2-Q3KZSpEmw@mail.gmail.com>
On Mon, Mar 17, 2025 at 09:54:03PM +0100, Miguel Ojeda wrote:
> On Mon, Mar 17, 2025 at 9:39 PM Miguel Ojeda
> <miguel.ojeda.sandonis@gmail.com> wrote:
> >
> > So I reworded accordingly: I renamed `KBox` and `Box` in the title and
>
> s/and/to/
>
> Anyway, if the policy is to keep titles and original log intact even
> in Option 3, I assume one should avoid [ ] comments in the log, and
> only use the one-line-before-my-SoB style for [ ], since I assume you
> keep the tags.
Yeah, that is good, but really it's not that big of a deal, we can parse
text pretty easily and handle it when it's not "perfect" :)
greg k-h
next prev parent reply other threads:[~2025-03-18 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-16 7:16 FAILED: patch "[PATCH] rust: init: fix `Zeroable` implementation for" failed to apply to 6.6-stable tree gregkh
2025-03-16 16:09 ` [PATCH 6.6.y] rust: init: fix `Zeroable` implementation for `Option<NonNull<T>>` and `Option<Box<T>>` Miguel Ojeda
2025-03-16 16:13 ` Miguel Ojeda
2025-03-16 16:32 ` Greg KH
2025-03-17 18:21 ` Miguel Ojeda
2025-03-17 20:24 ` Greg KH
2025-03-17 20:39 ` Miguel Ojeda
2025-03-17 20:54 ` Miguel Ojeda
2025-03-18 13:21 ` Greg KH [this message]
2025-03-17 12:24 ` Sasha Levin
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=2025031810-untoasted-email-5a46@gregkh \
--to=greg@kroah.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=stable@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