From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the tty tree with the powerpc tree
Date: Tue, 22 Aug 2023 13:51:50 +0200 [thread overview]
Message-ID: <2023082218-pecan-chef-e4bc@gregkh> (raw)
In-Reply-To: <20230818145826.00c7ead1@canb.auug.org.au>
On Fri, Aug 18, 2023 at 02:58:26PM +1000, Stephen Rothwell wrote:
> 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.
Thanks for the notice, I'll let the ppc developers remove it as it's in
their tree.
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-22 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 4:58 linux-next: manual merge of the tty tree with the powerpc tree Stephen Rothwell
2023-08-22 11:51 ` Greg KH [this message]
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=2023082218-pecan-chef-e4bc@gregkh \
--to=greg@kroah.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/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).