From: "luobin (L)" <luobin9@huawei.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <luoxianjun@huawei.com>,
<chiqijun@huawei.com>, <yin.yinshi@huawei.com>,
<cloud.wangxiaoyun@huawei.com>
Subject: Re: [PATCH net-next 5/5] hinic: add support to get eeprom information
Date: Thu, 4 Jun 2020 11:08:43 +0800 [thread overview]
Message-ID: <1a2dbd8d-9e93-4dcf-dfb0-5a7186fd8729@huawei.com> (raw)
In-Reply-To: <20200603200145.41cf76fd@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On 2020/6/4 11:01, Jakub Kicinski wrote:
> On Wed, 3 Jun 2020 14:20:15 +0800 Luo bin wrote:
>> add support to get eeprom information from the plug-in module
>> with ethtool -m cmd.
>>
>> Signed-off-by: Luo bin <luobin9@huawei.com>
>
> drivers/net/ethernet/huawei/hinic/hinic_port.c:1386:5: warning: variable port_id set but not used [-Wunused-but-set-variable]
> 1386 | u8 port_id;
> | ^~~~~~~
> .
>
Will fix. Thanks.
next prev parent reply other threads:[~2020-06-04 3:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 6:20 [PATCH net-next 0/5] hinic: add some ethtool ops support Luo bin
2020-06-03 6:20 ` [PATCH net-next 1/5] hinic: add support to set and get pause params Luo bin
2020-06-03 6:20 ` [PATCH net-next 2/5] hinic: add support to set and get irq coalesce Luo bin
2020-06-03 6:20 ` [PATCH net-next 3/5] hinic: add self test support Luo bin
2020-06-03 6:20 ` [PATCH net-next 4/5] hinic: add support to identify physical device Luo bin
2020-06-03 6:20 ` [PATCH net-next 5/5] hinic: add support to get eeprom information Luo bin
2020-06-04 3:01 ` Jakub Kicinski
2020-06-04 3:08 ` luobin (L) [this message]
2020-06-03 17:41 ` [PATCH net-next 0/5] hinic: add some ethtool ops support David Miller
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=1a2dbd8d-9e93-4dcf-dfb0-5a7186fd8729@huawei.com \
--to=luobin9@huawei.com \
--cc=chiqijun@huawei.com \
--cc=cloud.wangxiaoyun@huawei.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luoxianjun@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=yin.yinshi@huawei.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
all inboxes | Powered by JetHome®