All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
	 Linus Walleij <linusw@kernel.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 Linux Next Mailing List <linux-next@vger.kernel.org>,
	 Rob Herring <robh@kernel.org>
Subject: Re: linux-next: manual merge of the mtd tree with the origin tree
Date: Thu, 22 Jan 2026 16:42:44 +0100	[thread overview]
Message-ID: <87sebxodqj.fsf@bootlin.com> (raw)
In-Reply-To: <aXJCtrMEK8vhp7wc@sirena.org.uk> (Mark Brown's message of "Thu, 22 Jan 2026 15:31:02 +0000")

Hello,

On 22/01/2026 at 15:31:02 GMT, Mark Brown <broonie@kernel.org> wrote:

> Hi all,
>
> Today's linux-next merge of the mtd tree got a conflict in:
>
>   Documentation/devicetree/bindings/mtd/partitions/seama.yaml
>
> between commit:
>
>   54de247a0efa4 ("dt-bindings: Updates Linus Walleij's mail address")
>
> from the origin tree and commit:
>
>   125981ffa1674 ("dt-bindings: mtd: partitions: Combine simple partition bindings")
>
> from the mtd 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.
>
> [Dropped the removed file]

This is indeed the correct fix, as brought up by Rob already. I use to
avoid these cases but for this one it is apparently trivial enough so I
decided to pick the series as-is.

Miquèl

      reply	other threads:[~2026-01-22 15:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 15:31 linux-next: manual merge of the mtd tree with the origin tree Mark Brown
2026-01-22 15:42 ` Miquel Raynal [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=87sebxodqj.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=broonie@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    --cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.