* linux-next: duplicate patch in the rust tree
@ 2023-08-06 23:13 Stephen Rothwell
2023-08-07 9:39 ` Miguel Ojeda
0 siblings, 1 reply; 8+ messages in thread
From: Stephen Rothwell @ 2023-08-06 23:13 UTC (permalink / raw)
To: Miguel Ojeda; +Cc: Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 321 bytes --]
Hi all,
The following commit is also in Linus Torvalds' tree as a different commit
(but the same patch):
10a6032595f4 ("rust: allocator: Prevent mis-aligned allocation")
This is commit
b3d8aa84bbfe ("rust: allocator: Prevent mis-aligned allocation")
in Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: linux-next: duplicate patch in the rust tree
2023-08-06 23:13 linux-next: duplicate patch in the rust tree Stephen Rothwell
@ 2023-08-07 9:39 ` Miguel Ojeda
0 siblings, 0 replies; 8+ messages in thread
From: Miguel Ojeda @ 2023-08-07 9:39 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Miguel Ojeda, Linux Kernel Mailing List, Linux Next Mailing List
Hi Stephen,
On Mon, Aug 7, 2023 at 1:13 AM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
Thanks! I should have pushed the reword to `rust-next` too, sorry.
It is gone now.
Cheers,
Miguel
^ permalink raw reply [flat|nested] 8+ messages in thread
* linux-next: duplicate patch in the rust tree
@ 2024-09-17 4:59 Stephen Rothwell
2024-09-23 19:40 ` Miguel Ojeda
0 siblings, 1 reply; 8+ messages in thread
From: Stephen Rothwell @ 2024-09-17 4:59 UTC (permalink / raw)
To: Miguel Ojeda, Andrew Morton
Cc: Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
Hi all,
The following commit is also in the mm-stable tree as a different commit
(but the same patch):
cc1d98f9fe30 ("kasan: simplify and clarify Makefile")
This is commit
78788c3ede90 ("kasan: simplify and clarify Makefile")
in the mm-stable branch.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: linux-next: duplicate patch in the rust tree
2024-09-17 4:59 Stephen Rothwell
@ 2024-09-23 19:40 ` Miguel Ojeda
0 siblings, 0 replies; 8+ messages in thread
From: Miguel Ojeda @ 2024-09-23 19:40 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Miguel Ojeda, Andrew Morton, Linux Kernel Mailing List,
Linux Next Mailing List
On Tue, Sep 17, 2024 at 6:59 AM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> The following commit is also in the mm-stable tree as a different commit
> (but the same patch):
>
> cc1d98f9fe30 ("kasan: simplify and clarify Makefile")
>
> This is commit
>
> 78788c3ede90 ("kasan: simplify and clarify Makefile")
>
> in the mm-stable branch.
I forgot to reply during the conferences, but Andrew and I were expected this.
Thanks!
Cheers,
Miguel
^ permalink raw reply [flat|nested] 8+ messages in thread
* linux-next: duplicate patch in the rust tree
@ 2025-10-20 1:39 Stephen Rothwell
2025-10-20 2:14 ` Miguel Ojeda
0 siblings, 1 reply; 8+ messages in thread
From: Stephen Rothwell @ 2025-10-20 1:39 UTC (permalink / raw)
To: Miguel Ojeda, Greg KH, Arnd Bergmann
Cc: Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
Hi all,
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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: linux-next: duplicate patch in the rust tree
2025-10-20 1:39 Stephen Rothwell
@ 2025-10-20 2:14 ` Miguel Ojeda
2025-10-20 5:30 ` Greg KH
0 siblings, 1 reply; 8+ messages in thread
From: Miguel Ojeda @ 2025-10-20 2:14 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Miguel Ojeda, Greg KH, Arnd Bergmann, Linux Kernel Mailing List,
Linux Next Mailing List
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.
Thanks!
Cheers,
Miguel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: linux-next: duplicate patch in the rust tree
2025-10-20 2:14 ` Miguel Ojeda
@ 2025-10-20 5:30 ` Greg KH
2025-10-20 11:39 ` Miguel Ojeda
0 siblings, 1 reply; 8+ messages in thread
From: Greg KH @ 2025-10-20 5:30 UTC (permalink / raw)
To: Miguel Ojeda
Cc: Stephen Rothwell, Miguel Ojeda, Arnd Bergmann,
Linux Kernel Mailing List, Linux Next Mailing List
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: linux-next: duplicate patch in the rust tree
2025-10-20 5:30 ` Greg KH
@ 2025-10-20 11:39 ` Miguel Ojeda
0 siblings, 0 replies; 8+ messages in thread
From: Miguel Ojeda @ 2025-10-20 11:39 UTC (permalink / raw)
To: Greg KH
Cc: Stephen Rothwell, Miguel Ojeda, Arnd Bergmann,
Linux Kernel Mailing List, Linux Next Mailing List
On Mon, Oct 20, 2025 at 7:30 AM Greg KH <greg@kroah•com> wrote:
>
> Yes, will send those fixes to Linus for the next -rc release, sorry for
> the delay.
Thanks, no rush!
And sorry, I didn't mean to be pushy -- I checked the last pulls for
char-misc-linus and saw both -rc1 and other -rcs, so I didn't know if
you would wait for the merge window.
Cheers,
Miguel
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2025-10-20 11:40 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-08-06 23:13 linux-next: duplicate patch in the rust tree Stephen Rothwell
2023-08-07 9: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
2025-10-20 1:39 Stephen Rothwell
2025-10-20 2:14 ` Miguel Ojeda
2025-10-20 5:30 ` Greg KH
2025-10-20 11:39 ` Miguel Ojeda
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox