From: Greg KH <greg@kroah•com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Miguel Ojeda <ojeda@kernel•org>, Arnd Bergmann <arnd@arndb•de>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: duplicate patch in the rust tree
Date: Mon, 20 Oct 2025 07:30:13 +0200 [thread overview]
Message-ID: <2025102057-wolverine-morbidly-7f51@gregkh> (raw)
In-Reply-To: <CANiq72kHWgsvmxPYSAHpM5HaxCSf73t4NkPsBRXiPMTTe_u51w@mail.gmail.com>
On Mon, Oct 20, 2025 at 04:14:31AM +0200, Miguel Ojeda wrote:
> On Mon, Oct 20, 2025 at 3:39 AM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > The following commit is also in the char-misc.curent tree as a different
> > commit (but the same patch):
> >
> > abae8f3c8374 ("[TEMPORARY] rust_binder: clean `clippy::mem_replace_with_default` warning")
> >
> > This is commit
> >
> > 7e69a24b6b35 ("rust_binder: clean `clippy::mem_replace_with_default` warning")
> >
> > in the char-misc.current tree.
>
> Yeah, I added it at the top to be able to have the `rust-next`
> Clippy-clean, but I don't plan to submit it.
>
> Since you detect them, I will remove it to avoid confusion.
>
> Greg: it would be nice to get that one submitted to Linus during the
> -rcs, rather than the next merge window.
Yes, will send those fixes to Linus for the next -rc release, sorry for
the delay.
greg k-h
next prev parent reply other threads:[~2025-10-20 5:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 1:39 linux-next: duplicate patch in the rust tree Stephen Rothwell
2025-10-20 2:14 ` Miguel Ojeda
2025-10-20 5:30 ` Greg KH [this message]
2025-10-20 11:39 ` Miguel Ojeda
-- strict thread matches above, loose matches on Subject: below --
2024-09-17 4:59 Stephen Rothwell
2024-09-23 19:40 ` Miguel Ojeda
2023-08-06 23:13 Stephen Rothwell
2023-08-07 9:39 ` 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=2025102057-wolverine-morbidly-7f51@gregkh \
--to=greg@kroah$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=miguel.ojeda.sandonis@gmail$(echo .)com \
--cc=ojeda@kernel$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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