From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Kishon Vijay Abraham I <kishon@kernel.org>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Networking <netdev@vger.kernel.org>,
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 phy-next tree with the net-next tree
Date: Mon, 15 Jul 2024 17:17:12 +0200 [thread overview]
Message-ID: <ZpU9eOsMq_ogA7Nr@lore-desk> (raw)
In-Reply-To: <ZpTBCUXx5e24izzR@matsya>
[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]
> Hi Stephen,
>
> On 15-07-24, 15:12, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the phy-next tree got a conflict in:
> >
> > MAINTAINERS
> >
> > between commit:
> >
> > 23020f049327 ("net: airoha: Introduce ethernet support for EN7581 SoC")
> >
> > from the net-next tree and commit:
> >
> > d7d2818b9383 ("phy: airoha: Add PCIe PHY driver for EN7581 SoC.")
> >
> > from the phy-next tree.
>
> lgtm, thanks for letting us know
Hi Stephen,
LGTM as well. I forgot to mention this conflict, sorry for that.
Regards,
Lorenzo
>
> >
> > 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 d739d07fb234,269c2144bedb..000000000000
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@@ -693,15 -682,14 +693,23 @@@ S: Supporte
> > F: fs/aio.c
> > F: include/linux/*aio*.h
> >
> > +AIROHA ETHERNET DRIVER
> > +M: Lorenzo Bianconi <lorenzo@kernel.org>
> > +L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> > +L: linux-mediatek@lists.infradead.org (moderated for non-subscribers)
> > +L: netdev@vger.kernel.org
> > +S: Maintained
> > +F: Documentation/devicetree/bindings/net/airoha,en7581-eth.yaml
> > +F: drivers/net/ethernet/mediatek/airoha_eth.c
> > +
> > + AIROHA PCIE PHY DRIVER
> > + M: Lorenzo Bianconi <lorenzo@kernel.org>
> > + L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> > + S: Maintained
> > + F: Documentation/devicetree/bindings/phy/airoha,en7581-pcie-phy.yaml
> > + F: drivers/phy/phy-airoha-pcie-regs.h
> > + F: drivers/phy/phy-airoha-pcie.c
> > +
> > AIROHA SPI SNFI DRIVER
> > M: Lorenzo Bianconi <lorenzo@kernel.org>
> > M: Ray Liu <ray.liu@airoha.com>
>
>
>
> --
> ~Vinod
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-07-15 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 5:12 linux-next: manual merge of the phy-next tree with the net-next tree Stephen Rothwell
2024-07-15 6:26 ` Vinod Koul
2024-07-15 15:17 ` Lorenzo Bianconi [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-11 3:42 Stephen Rothwell
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=ZpU9eOsMq_ogA7Nr@lore-desk \
--to=lorenzo@kernel.org \
--cc=davem@davemloft.net \
--cc=kishon@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=vkoul@kernel.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