From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>, Michael Ellerman <mpe@ellerman•id.au>
Cc: PowerPC <linuxppc-dev@lists•ozlabs.org>,
Christophe Leroy <christophe.leroy@csgroup•eu>,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
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 tty tree with the powerpc tree
Date: Fri, 18 Aug 2023 14:58:26 +1000 [thread overview]
Message-ID: <20230818145826.00c7ead1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]
Hi all,
Today's linux-next merge of the tty tree got a conflict in:
arch/powerpc/include/asm/fs_pd.h
between commits:
e6e077cb2aa4 ("powerpc/include: Declare mpc8xx_immr in 8xx_immap.h")
fecc436a97af ("powerpc/include: Remove mpc8260.h and m82xx_pci.h")
fbbf4280dae4 ("powerpc/8xx: Remove immr_map() and immr_unmap()")
7768716d2f19 ("powerpc/cpm2: Remove cpm2_map() and cpm2_unmap()")
from the powerpc tree and commit:
c2d6c1b4f034 ("serial: cpm_uart: Use get_baudrate() instead of uart_baudrate()")
from the tty 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.
Note that after all the above are applied, it looks like this file can
be removed completely as nothing in the tree includes it any more.
--
Cheers,
Stephen Rothwell
diff --cc arch/powerpc/include/asm/fs_pd.h
index d530f68b4eef,7b61b80f212d..000000000000
--- a/arch/powerpc/include/asm/fs_pd.h
+++ b/arch/powerpc/include/asm/fs_pd.h
@@@ -14,14 -14,26 +14,4 @@@
#include <sysdev/fsl_soc.h>
#include <asm/time.h>
- static inline int uart_baudrate(void)
- {
- return get_baudrate();
- }
-#ifdef CONFIG_CPM2
-#include <asm/cpm2.h>
--
- static inline int uart_clock(void)
- {
- return ppc_proc_freq;
- }
-#if defined(CONFIG_8260)
-#include <asm/mpc8260.h>
-#endif
-
-#define cpm2_map(member) (&cpm2_immr->member)
-#define cpm2_map_size(member, size) (&cpm2_immr->member)
-#define cpm2_unmap(addr) do {} while(0)
-#endif
-
-#ifdef CONFIG_PPC_8xx
-#include <asm/8xx_immap.h>
-
-extern immap_t __iomem *mpc8xx_immr;
-
-#define immr_map(member) (&mpc8xx_immr->member)
-#define immr_map_size(member, size) (&mpc8xx_immr->member)
-#define immr_unmap(addr) do {} while (0)
-#endif
--
#endif
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-08-18 4:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 4:58 Stephen Rothwell [this message]
2023-08-22 11:51 ` linux-next: manual merge of the tty tree with the powerpc tree Greg KH
2023-08-23 6:08 ` Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2023-11-27 0:49 Stephen Rothwell
2023-11-27 11:00 ` Michael Ellerman
2023-11-27 11:17 ` Uwe Kleine-König
2011-09-21 5:01 Stephen Rothwell
2011-09-21 14:06 ` Greg KH
2011-09-21 4:50 Stephen Rothwell
2011-09-21 14:06 ` Greg KH
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=20230818145826.00c7ead1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=christophe.leroy@csgroup$(echo .)eu \
--cc=greg@kroah$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
/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