From: Jakub Kicinski <kuba@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: Andrew Lunn <andrew@lunn.ch>, <davem@davemloft.net>,
<pabeni@redhat.com>, <edumazet@google.com>,
<netdev@vger.kernel.org>, Kurt Kanzenbach <kurt@linutronix.de>,
<sasha.neftin@intel.com>,
Naama Meir <naamax.meir@linux.intel.com>
Subject: Re: [PATCH net-next] igc: Add support for LEDs on i225/i226
Date: Tue, 13 Feb 2024 18:20:26 -0800 [thread overview]
Message-ID: <20240213182026.7c14d7d4@kernel.org> (raw)
In-Reply-To: <11004b9c-97df-fb6f-efb8-9550ea2b6c03@intel.com>
On Tue, 13 Feb 2024 13:05:43 -0800 Tony Nguyen wrote:
> > 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
FWIW I think it's one of those things where particular cases may look
odd, but for those on the patch handling path always following the same
procedure make the life *so* much easier :(
next prev parent reply other threads:[~2024-02-14 2:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 18:41 [PATCH net-next] igc: Add support for LEDs on i225/i226 Tony Nguyen
2024-02-13 18:49 ` Andrew Lunn
2024-02-13 19:09 ` Tony Nguyen
2024-02-13 20:28 ` Andrew Lunn
2024-02-13 21:05 ` Tony Nguyen
2024-02-14 2:20 ` Jakub Kicinski [this message]
2024-02-15 12:50 ` patchwork-bot+netdevbpf
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=20240213182026.7c14d7d4@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kurt@linutronix.de \
--cc=naamax.meir@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sasha.neftin@intel.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).