From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Simona Vetter <simona.vetter@ffwll.ch>,
Danilo Krummrich <dakr@kernel.org>,
Vitaly Wool <vitaly.wool@konsulko.se>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.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 mm-unstable tree with the drm-misc-fixes tree
Date: Tue, 12 Aug 2025 20:59:46 -0700 [thread overview]
Message-ID: <20250812205946.2db0d8645f3c2ed6c8828ae2@linux-foundation.org> (raw)
In-Reply-To: <20250813111151.6a261ca1@canb.auug.org.au>
On Wed, 13 Aug 2025 11:11:51 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Today's linux-next merge of the mm-unstable tree got a conflict in:
>
> rust/kernel/alloc/allocator.rs
>
> between commit:
>
> fde578c86281 ("rust: alloc: replace aligned_size() with Kmalloc::aligned_layout()")
>
> from the drm-misc-fixes tree and commit:
>
> cda097b07bce ("rust: support large alignments in allocations")
>
> from the mm-unstable tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
Thanks.
Well that's messy.
Is it intended that the containing series ("Alloc and drm::Device
fixes") be merged into 6.17-rcX?
next prev parent reply other threads:[~2025-08-13 3:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 1:11 Stephen Rothwell
2025-08-13 3:59 ` Andrew Morton [this message]
2025-08-13 9:07 ` Danilo Krummrich
2025-08-13 8:50 ` Danilo Krummrich
2026-07-20 13:31 Mark Brown
2026-07-20 14:41 ` Christoph Hellwig
2026-07-20 14:46 ` Matthew Wilcox
2026-07-20 22:08 ` Matthew Brost
2026-07-21 16:55 ` Matthew Brost
2026-08-03 12:55 ` Christian König
2026-08-03 19:02 ` Matthew Brost
2026-07-20 21:58 ` Matthew Brost
2026-07-21 4:54 ` Christoph Hellwig
2026-07-21 6:06 ` Matthew Brost
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=20250812205946.2db0d8645f3c2ed6c8828ae2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=simona.vetter@ffwll.ch \
--cc=vitaly.wool@konsulko.se \
/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
all inboxes | Powered by JetHome®