From: Andrew Morton <akpm@linux-foundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: Greg KH <greg@kroah.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
LiuJunyuan <2058432396@qq.com>, Mike Rapoport <rppt@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>
Subject: Re: linux-next: manual merge of the staging.current tree with the mm-fixes tree
Date: Mon, 2 Nov 2026 11:02:14 -0800 [thread overview]
Message-ID: <20261102110214.26627fcf298c77b8ceee12b8@linux-foundation.org> (raw)
In-Reply-To: <auib_crbWYfKZw9V@sirena.org.uk>
On Mon, 2 Nov 2026 14:19:41 +0000 Mark Brown <broonie@kernel.org> wrote:
> Today's linux-next merge of the staging.current tree got a conflict in:
>
> MAINTAINERS
>
> between commit:
>
> 88c41b4cb3432 ("MAINTAINERS: sort component entries alphabetically")
>
> from the mm-fixes tree and commit:
>
> 24934cb6b8cd9 ("staging: vme_user: delete driver")
>
> from the staging.current tree, the rare delete/delete conflict.
>
> 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.
>
> diff --combined MAINTAINERS
OK, thanks, that's nuts. I'll make those two patches go away for now.
It's not exactly important stuff - think about it later.
next prev parent reply other threads:[~2026-11-02 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 14:19 Mark Brown
2026-11-02 19:02 ` Andrew Morton [this message]
2026-11-02 19:17 ` Mark Brown
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=20261102110214.26627fcf298c77b8ceee12b8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=2058432396@qq.com \
--cc=broonie@kernel.org \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=vbabka@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
all inboxes | Powered by JetHome®