From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Joe Perches <joe@perches.com>
Subject: linux-next: manual merge of the realtek tree with Linus' tree
Date: Mon, 13 Apr 2020 08:50:34 +1000 [thread overview]
Message-ID: <20200413085034.5e77f236@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Hi all,
Today's linux-next merge of the realtek tree got a conflict in:
MAINTAINERS
between commit:
3b50142d8528 ("MAINTAINERS: sort field names for all entries")
from Linus' tree and commit:
d6656fa4c621 ("ARM: Prepare Realtek RTD1195")
from the realtek 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.
--
Cheers,
Stephen Rothwell
diff --cc MAINTAINERS
index 6851ef7cf1bd,1b15d2dd2535..000000000000
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -2269,8 -2203,10 +2269,9 @@@ M: Andreas Färber <afaerber@suse.de
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
L: linux-realtek-soc@lists.infradead.org (moderated for non-subscribers)
S: Maintained
-F: arch/arm/boot/dts/rtd*
+F: Documentation/devicetree/bindings/arm/realtek.yaml
+ F: arch/arm/mach-realtek/
F: arch/arm64/boot/dts/realtek/
-F: Documentation/devicetree/bindings/arm/realtek.yaml
ARM/RENESAS ARM64 ARCHITECTURE
M: Geert Uytterhoeven <geert+renesas@glider.be>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-04-12 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 22:50 Stephen Rothwell [this message]
2020-04-13 0:22 ` Andreas Färber
2020-04-13 0:27 ` Joe Perches
2020-04-13 0:52 ` Andreas Färber
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=20200413085034.5e77f236@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=afaerber@suse.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®