From: Lee Jones <lee@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Ming Yu <a0282524688@gmail.com>
Subject: Re: linux-next: manual merge of the gpio-brgl tree with the mfd tree
Date: Thu, 25 Sep 2025 11:38:46 +0100 [thread overview]
Message-ID: <20250925103846.GA8757@google.com> (raw)
In-Reply-To: <aNEedsR5CDuVBoyo@finisterre.sirena.org.uk>
On Mon, 22 Sep 2025, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the gpio-brgl tree got a conflict in:
>
> MAINTAINERS
>
> between commit:
>
> 8c13787893fde ("mfd: Add core driver for Nuvoton NCT6694")
>
> from the mfd tree and commits:
>
> 51dad33ede636 ("mfd: Add core driver for Nuvoton NCT6694")
> 611a995e8ae1a ("gpio: Add Nuvoton NCT6694 GPIO support")
> 197e779d29d87 ("hwmon: Add Nuvoton NCT6694 HWMON support")
> c5cf27dbaeb6e ("i2c: Add Nuvoton NCT6694 I2C support")
> 8a204684d0ffd ("can: Add Nuvoton NCT6694 CANFD support")
> d463bb1405836 ("rtc: Add Nuvoton NCT6694 RTC support")
> f9d737a7d84ff ("watchdog: Add Nuvoton NCT6694 WDT support")
>
> from the gpio-brgl 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.
>
>
> diff --cc MAINTAINERS
> index 55288f2ffb6b3,681fbc8258052..0000000000000
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
Missing diff?
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-09-25 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 10:01 linux-next: manual merge of the gpio-brgl tree with the mfd tree Mark Brown
2025-09-25 10:38 ` Lee Jones [this message]
2025-09-25 12:14 ` Mark Brown
2025-09-25 12:15 ` Lee Jones
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=20250925103846.GA8757@google.com \
--to=lee@kernel.org \
--cc=a0282524688@gmail.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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.