From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Alexey Charkov <alchark@gmail.com>, Andi Shyti <andi@smida.it>,
ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Andi Shyti <andi.shyti@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: manual merge of the i2c-host tree with the arm-soc tree
Date: Thu, 22 May 2025 08:15:06 +0200 [thread overview]
Message-ID: <455ef8b8-dec5-47e0-94db-611ac399903b@linaro.org> (raw)
In-Reply-To: <20250522121726.0a4350fc@canb.auug.org.au>
On 22/05/2025 04:17, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the i2c-host tree got a conflict in:
>
> MAINTAINERS
>
> between commit:
>
> 47cbd5d8693d ("ARM: vt8500: MAINTAINERS: Include vt8500 soc driver in maintainers entry")
>
> from the arm-soc tree and commit:
>
> 3887d3f64260 ("dt-bindings: i2c: i2c-wmt: Convert to YAML")
>
> from the i2c-host 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.
Arnd,
I forgot to mention that in pull request. There will be a conflict in
MAINTAINERS file in ARM/VT8500 ARM ARCHITECTURE entry:
3425 ARM/VT8500 ARM ARCHITECTURE
3426 M: Alexey Charkov <alchark@gmail.com>
3427 M: Krzysztof Kozlowski <krzk@kernel.org>
between multiple trees - arm-soc, i2c, devicetree and pwm, because
patches went through different trees. This conflict will go to Linus as
well.
Final resolution is like:
-F: Documentation/devicetree/bindings/i2c/i2c-wmt.txt
+F: Documentation/devicetree/bindings/hwinfo/via,vt8500-scc-id.yaml
+F: Documentation/devicetree/bindings/i2c/wm,wm8505-i2c.yaml
+F: Documentation/devicetree/bindings/interrupt-controller/via,vt8500-intc.yaml
+ F: Documentation/devicetree/bindings/pwm/via,vt8500-pwm.yaml
Best regards,
Krzysztof
prev parent reply other threads:[~2025-05-22 6:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 2:17 Stephen Rothwell
2025-05-22 6:15 ` Krzysztof Kozlowski [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=455ef8b8-dec5-47e0-94db-611ac399903b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alchark@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=andi@smida.it \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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®