From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Miguel Ojeda <ojeda@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patch in the rust tree
Date: Mon, 7 Aug 2023 09:13:02 +1000 [thread overview]
Message-ID: <20230807091302.6370fc50@canb.auug.org.au> (raw)
[-- 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 --]
next reply other threads:[~2023-08-06 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 23:13 Stephen Rothwell [this message]
2023-08-07 9:39 ` linux-next: duplicate patch in the rust tree 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
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=20230807091302.6370fc50@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=ojeda@kernel$(echo .)org \
/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