From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jiawen Wu <jiawenwu@trustnetic.com>, <dev@dpdk.org>
Subject: Re: [PATCH 7/9] net: add LED OEM support for wangxun devices
Date: Tue, 8 Feb 2022 17:41:54 +0000 [thread overview]
Message-ID: <2959b4b4-98be-9b20-4674-8a045b443be1@intel.com> (raw)
In-Reply-To: <20220208101129.69173-8-jiawenwu@trustnetic.com>
On 2/8/2022 10:11 AM, Jiawen Wu wrote:
> Support custom LED OEM for ngbe and txgbe driver.
>
Can you please split patch for ngbe and txgbe?
Btw, both drivers seems hav LED support (at least '.dev_led_on', '.dev_led_off'
dev ops implemented), can you please add some details in the commit log
what exactly added in this patch?
Also 'doc/guides/nics/features/txgbe.ini' seems missing the 'LED' feature
although dev_ops implemented, can you fix that too.
> Signed-off-by: Jiawen Wu <jiawenwu@trustnetic.com>
<...>
next prev parent reply other threads:[~2022-02-08 17:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 10:11 [PATCH 0/9] Wangxun fixes and supports Jiawen Wu
2022-02-08 10:11 ` [PATCH 1/9] net/ngbe: fix failed to receive packets Jiawen Wu
2022-02-08 10:11 ` [PATCH 2/9] net/ngbe: fix link interrupt sometimes lost Jiawen Wu
2022-02-08 10:11 ` [PATCH 3/9] net/ngbe: fix Tx pending Jiawen Wu
2022-02-08 17:38 ` Ferruh Yigit
2022-02-08 10:11 ` [PATCH 4/9] net/ngbe: fix RxTx packet statistics Jiawen Wu
2022-02-08 17:38 ` Ferruh Yigit
2022-02-08 10:11 ` [PATCH 5/9] net/ngbe: optimize the PHY initialization process Jiawen Wu
2022-02-08 17:39 ` Ferruh Yigit
2022-02-09 2:38 ` Jiawen Wu
2022-02-08 10:11 ` [PATCH 6/9] net/ngbe: add support to custom PHY interfaces Jiawen Wu
2022-02-08 17:41 ` Ferruh Yigit
2022-02-09 6:17 ` Jiawen Wu
2022-02-08 10:11 ` [PATCH 7/9] net: add LED OEM support for wangxun devices Jiawen Wu
2022-02-08 17:41 ` Ferruh Yigit [this message]
2022-02-08 10:11 ` [PATCH 8/9] net/txgbe: fix to set link up and down Jiawen Wu
2022-02-08 10:11 ` [PATCH 9/9] net/txgbe: fix KR auto-negotiation Jiawen Wu
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=2959b4b4-98be-9b20-4674-8a045b443be1@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jiawenwu@trustnetic.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).