From: Stephen Rothwell <sfr@canb•auug.org.au>
To: John Paul Adrian Glaubitz <glaubitz@physik•fu-berlin.de>,
Helge Deller <deller@gmx•de>
Cc: Parisc List <linux-parisc@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Randy Dunlap <rdunlap@infradead•org>
Subject: linux-next: manual merge of the sh tree with the parisc-hd tree
Date: Fri, 24 Mar 2023 11:15:14 +1100 [thread overview]
Message-ID: <20230324111514.2bbcd64b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
Hi all,
Today's linux-next merge of the sh tree got a conflict in:
Documentation/kbuild/kbuild.rst
between commit:
49deed336ef9 ("parisc: update kbuild doc. aliases for parisc64")
from the parisc-hd tree and commit:
644a9cf0d2a8 ("sh: remove sh5/sh64 last fragments")
from the sh 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 Documentation/kbuild/kbuild.rst
index 84b2d2dc8f78,e22621f4af0b..000000000000
--- a/Documentation/kbuild/kbuild.rst
+++ b/Documentation/kbuild/kbuild.rst
@@@ -160,8 -160,6 +160,7 @@@ directory name found in the arch/ direc
But some architectures such as x86 and sparc have aliases.
- x86: i386 for 32 bit, x86_64 for 64 bit
+- parisc: parisc64 for 64 bit
- - sh: sh for 32 bit, sh64 for 64 bit
- sparc: sparc32 for 32 bit, sparc64 for 64 bit
CROSS_COMPILE
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2023-03-24 0:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230324111514.2bbcd64b@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=deller@gmx$(echo .)de \
--cc=glaubitz@physik$(echo .)fu-berlin.de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-parisc@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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