[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11004b9c-97df-fb6f-efb8-9550ea2b6c03@intel.com>
Date: Tue, 13 Feb 2024 13:05:43 -0800
From: Tony Nguyen <anthony.l.nguyen@...el.com>
To: Andrew Lunn <andrew@...n.ch>
CC: <davem@...emloft.net>, <kuba@...nel.org>, <pabeni@...hat.com>,
<edumazet@...gle.com>, <netdev@...r.kernel.org>, Kurt Kanzenbach
<kurt@...utronix.de>, <sasha.neftin@...el.com>, Naama Meir
<naamax.meir@...ux.intel.com>
Subject: Re: [PATCH net-next] igc: Add support for LEDs on i225/i226
On 2/13/2024 12:28 PM, Andrew Lunn wrote:
>
> v3 is still in patchworks:
>
> https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=393838
I think you crossed the URLs. This one is for IWL which is marked as
Under Review. I would change this to Accepted upon netdev acceptance.
netdev:
https://patchwork.kernel.org/project/netdevbpf/list/?series=823612&state=*
> State: Awaiting Upstream
For Awaiting Upstream:
"
patch should be reviewed and handled by appropriate sub-maintainer, who
will send it on to the networking trees; patches set to Awaiting
upstream in netdev's patchwork will usually remain in this state,
whether the sub-maintainer requested changes, accepted or rejected the patch
"
https://docs.kernel.org/process/maintainer-netdev.html#patch-status
Thanks,
Tony
> Does that mean you? Would not just giving an Acked-by be enough? Now
> we have it twice in patchworks, and you did not mark your version as
> v4, so is there a danger we get the different versions mixed up?
>
> Andrew
>
Powered by blists - more mailing lists