From: "Danilo Krummrich" <dakr@kernel.org>
To: "Mark Brown" <broonie@kernel.org>
Cc: "Greg KH" <greg@kroah.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the driver-core tree with the rust-alloc tree
Date: Thu, 21 May 2026 14:10:42 +0200 [thread overview]
Message-ID: <DIOCENK4QFRB.2G7UT0CQLRZMC@kernel.org> (raw)
In-Reply-To: <ag71mqpl_sgr_hsk@sirena.org.uk>
On Thu May 21, 2026 at 2:07 PM CEST, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the driver-core tree got a conflict in:
>
> rust/kernel/alloc/kbox.rs
>
> between commit:
>
> 9b25d4111e913 ("rust: alloc: cleanup imports and use "kernel vertical" style")
>
> from the rust-alloc tree and commit:
>
> abb21500e7e5d ("rust: alloc: add Box::zeroed()")
>
> from the driver-core tree.
Looks good, thanks!
prev parent reply other threads:[~2026-05-21 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 12:07 linux-next: manual merge of the driver-core tree with the rust-alloc tree Mark Brown
2026-05-21 12:10 ` Danilo Krummrich [this message]
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=DIOCENK4QFRB.2G7UT0CQLRZMC@kernel.org \
--to=dakr@kernel.org \
--cc=broonie@kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rafael@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