[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZH22jS7KPPBEVS2a@shell.armlinux.org.uk>
Date: Mon, 5 Jun 2023 11:18:53 +0100
From: "Russell King (Oracle)" <linux@...linux.org.uk>
To: 'Wolfram Sang' <wsa@...nel.org>
Cc: Jiawen Wu <jiawenwu@...stnetic.com>, netdev@...r.kernel.org,
jarkko.nikula@...ux.intel.com, andriy.shevchenko@...ux.intel.com,
mika.westerberg@...ux.intel.com, jsd@...ihalf.com,
Jose.Abreu@...opsys.com, andrew@...n.ch, hkallweit1@...il.com,
linux-i2c@...r.kernel.org, linux-gpio@...r.kernel.org,
mengyuanlou@...-swift.com,
'Piotr Raczynski' <piotr.raczynski@...el.com>
Subject: Re: [PATCH net-next v11 2/9] i2c: designware: Add driver support for
Wangxun 10Gb NIC
On Mon, Jun 05, 2023 at 12:05:35PM +0200, 'Wolfram Sang' wrote:
>
> > Yes, other patches will build even without this patch. But SFP will not work.
> > This patch series implement I2C, GPIO, SFP and PHYLINK. The support of SFP
> > is dependent on I2C and GPIO. If these patches will be end up merging in the
> > same upstream version, it's not a problem to merge them in different trees,
> > I think.
>
> That's how I saw it as well.
>
> Applied to for-next, thanks!
Be careful... net-next uses patchwork, and I suspect as this is posted
as a series which the subject line states as being destined by the
author for the "net-next" tree, the entire series will end up being
slurped into the net-next tree.
https://www.kernel.org/doc/html/v5.10/networking/netdev-FAQ.html#q-how-do-i-indicate-which-tree-net-vs-net-next-my-patch-should-be-in
This patch is still marked as "new" in patchwork:
https://patchwork.kernel.org/project/netdevbpf/patch/20230605025211.743823-3-jiawenwu@trustnetic.com/
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists