From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
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 asm-generic tree with Linus' tree
Date: Fri, 8 Oct 2021 09:38:34 +1100 [thread overview]
Message-ID: <20211008093834.6ce64bb7@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
Hi all,
Today's linux-next merge of the asm-generic tree got a conflict in:
drivers/firmware/Kconfig
between commit:
4382c73a12b4 ("firmware: qcom_scm: QCOM_SCM should depend on ARCH_QCOM")
from Linus' tree and commit:
7efbbe6e1414 ("qcom_scm: hide Kconfig symbol")
from the asm-generic tree.
I fixed it up (I just used the latter) 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-10-07 22:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 22:38 Stephen Rothwell [this message]
2021-10-08 8:29 ` linux-next: manual merge of the asm-generic tree with Linus' tree Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2018-04-02 23:22 Stephen Rothwell
2016-11-09 22:38 Stephen Rothwell
2009-06-12 6:49 Stephen Rothwell
2009-06-12 8:05 ` Arnd Bergmann
2009-06-12 8:18 ` Stephen Rothwell
2009-06-12 6:43 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=20211008093834.6ce64bb7@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=geert+renesas@glider.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).