From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Networking <netdev@vger.kernel.org>,
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 net-next tree with the powerpc tree
Date: Wed, 30 Aug 2023 09:28:14 +1000 [thread overview]
Message-ID: <20230830092814.71cb6911@canb.auug.org.au> (raw)
In-Reply-To: <20230818111707.2714e8cb@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
Hi all,
On Fri, 18 Aug 2023 11:17:07 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the net-next tree got a conflict in:
>
> drivers/net/ethernet/freescale/fs_enet/fs_enet.h
>
> between commit:
>
> 60bc069c433f ("powerpc/include: Remove unneeded #include <asm/fs_pd.h>")
>
> from the powerpc tree and commit:
>
> 7a76918371fe ("net: fs_enet: Move struct fs_platform_info into fs_enet.h")
>
> from the net-next 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 drivers/net/ethernet/freescale/fs_enet/fs_enet.h
> index aad96cb2ab4e,d371072fff60..000000000000
> --- a/drivers/net/ethernet/freescale/fs_enet/fs_enet.h
> +++ b/drivers/net/ethernet/freescale/fs_enet/fs_enet.h
> @@@ -9,8 -10,8 +10,6 @@@
> #include <linux/phy.h>
> #include <linux/dma-mapping.h>
>
> - #include <linux/fs_enet_pd.h>
> -#include <asm/fs_pd.h>
> --
> #ifdef CONFIG_CPM1
> #include <asm/cpm1.h>
> #endif
This is now a conflict between the powerpc tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-08-29 23:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 1:17 linux-next: manual merge of the net-next tree with the powerpc tree Stephen Rothwell
2023-08-29 23:28 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-05 23:21 Stephen Rothwell
2020-04-01 23:09 ` Stephen Rothwell
2012-03-09 2:36 Stephen Rothwell
2012-03-09 6:15 ` David Miller
2012-03-09 6:44 ` Stephen Rothwell
2012-03-11 22:56 ` David Miller
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=20230830092814.71cb6911@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).