From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Walleij <linus.walleij@linaro.org>, Marc Zyngier <maz@kernel.org>
Cc: Jianqun Xu <jay.xu@rock-chips.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the pinctrl tree with the irqchip tree
Date: Tue, 17 Aug 2021 20:04:12 +1000 [thread overview]
Message-ID: <20210817200412.799bd992@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
Hi all,
Today's linux-next merge of the pinctrl tree got a conflict in:
drivers/pinctrl/pinctrl-rockchip.c
between commit:
a9cb09b7be84 ("pinctrl: Bulk conversion to generic_handle_domain_irq()")
from the irqchip tree and commit:
9ce9a02039de ("pinctrl/rockchip: drop the gpio related codes")
from the pinctrl tree.
I fixed it up (the latter removed the code changed by the former, so I
did that) 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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-08-17 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 10:04 Stephen Rothwell [this message]
2021-08-17 20:14 ` linux-next: manual merge of the pinctrl tree with the irqchip tree Linus Walleij
2021-08-18 19:59 ` Marc Zyngier
-- strict thread matches above, loose matches on Subject: below --
2022-02-21 22:32 broonie
2022-02-28 7:04 ` Stephen Rothwell
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=20210817200412.799bd992@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jay.xu@rock-chips.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maz@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