From: Andrew Lunn <andrew@lunn.ch>
To: Salil Mehta <salil.mehta@huawei.com>
Cc: davem@davemloft.net, yisen.zhuang@huawei.com,
huangdaode@hisilicon.com, lipeng321@huawei.com,
mehta.salil.lnk@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
linuxarm@huawei.com
Subject: Re: [PATCH V5 net-next 7/8] net: hns3: Add Ethtool support to HNS3 driver
Date: Sat, 29 Jul 2017 01:49:22 +0200 [thread overview]
Message-ID: <20170728234922.GC16080@lunn.ch> (raw)
In-Reply-To: <20170728222652.118448-8-salil.mehta@huawei.com>
On Fri, Jul 28, 2017 at 11:26:51PM +0100, Salil Mehta wrote:
> +static const struct hns3_link_mode_mapping hns3_lm_map[] = {
> + {HNS3_LM_FIBRE_BIT, ETHTOOL_LINK_MODE_FIBRE_BIT, FLG},
> + {HNS3_LM_AUTONEG_BIT, ETHTOOL_LINK_MODE_Autoneg_BIT, FLG},
> + {HNS3_LM_TP_BIT, ETHTOOL_LINK_MODE_TP_BIT, FLG},
> + {HNS3_LM_PAUSE_BIT, ETHTOOL_LINK_MODE_Pause_BIT, FLG},
> + {HNS3_LM_BACKPLANE_BIT, ETHTOOL_LINK_MODE_Backplane_BIT, FLG},
> + {HNS3_LM_10BASET_HALF_BIT, ETHTOOL_LINK_MODE_10baseT_Half_BIT, FLG},
> + {HNS3_LM_10BASET_FULL_BIT, ETHTOOL_LINK_MODE_10baseT_Full_BIT, FLG},
> + {HNS3_LM_100BASET_HALF_BIT, ETHTOOL_LINK_MODE_100baseT_Half_BIT, FLG},
> + {HNS3_LM_100BASET_FULL_BIT, ETHTOOL_LINK_MODE_100baseT_Full_BIT, FLG},
> + {HNS3_LM_1000BASET_FULL_BIT, ETHTOOL_LINK_MODE_1000baseT_Full_BIT, FLG},
> +};
It seems like all entries have link_mode_ksettings set to FLG. Which
probably indicates it is pointless.
> +
> +static inline void hns3_driv_to_eth_caps(u32 caps,
> + struct ethtool_link_ksettings *cmd)
Please don't use inline anywhere except in header file stub
functions. Let the compiler decide.
> +static int hns3_get_link_ksettings(struct net_device *netdev,
> + struct ethtool_link_ksettings *cmd)
> +{
> + struct hns3_nic_priv *priv = netdev_priv(netdev);
> + struct hnae3_handle *h = priv->ae_handle;
> + u32 supported_caps;
> + u32 advertised_caps;
> + u8 media_type;
> + u8 link_stat;
> + u8 auto_neg;
> + u8 duplex;
> + u32 speed;
> +
> + if (!h->ae_algo || !h->ae_algo->ops)
> + return -ESRCH;
#define ESRCH 3 /* No such process */
No such process ????
Andrew
next prev parent reply other threads:[~2017-07-28 23:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 22:26 [PATCH V5 net-next 0/8] Hisilicon Network Subsystem 3 Ethernet Driver Salil Mehta
2017-07-28 22:26 ` [PATCH V5 net-next 1/8] net: hns3: Add support of HNS3 Ethernet Driver for hip08 SoC Salil Mehta
2017-07-28 22:26 ` [PATCH V5 net-next 2/8] net: hns3: Add support of the HNAE3 framework Salil Mehta
[not found] ` <20170728222652.118448-3-salil.mehta-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-07-30 9:58 ` Leon Romanovsky
2017-07-31 9:04 ` Salil Mehta
[not found] ` <20170728222652.118448-1-salil.mehta-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-07-28 22:26 ` [PATCH V5 net-next 3/8] net: hns3: Add HNS3 IMP(Integrated Mgmt Proc) Cmd Interface Support Salil Mehta
2017-07-28 22:26 ` [PATCH V5 net-next 4/8] net: hns3: Add HNS3 Acceleration Engine & Compatibility Layer Support Salil Mehta
2017-07-28 22:26 ` [PATCH V5 net-next 5/8] net: hns3: Add support of TX Scheduler & Shaper to HNS3 driver Salil Mehta
2017-07-28 22:26 ` [PATCH V5 net-next 6/8] net: hns3: Add MDIO support to HNS3 Ethernet driver for hip08 SoC Salil Mehta
2017-07-28 23:24 ` Andrew Lunn
[not found] ` <20170728232428.GA16080-g2DYL2Zd6BY@public.gmane.org>
2017-07-28 23:50 ` Salil Mehta
[not found] ` <20170728222652.118448-7-salil.mehta-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-07-28 23:28 ` Andrew Lunn
2017-07-28 23:52 ` Salil Mehta
2017-07-28 22:26 ` [PATCH V5 net-next 7/8] net: hns3: Add Ethtool support to HNS3 driver Salil Mehta
2017-07-28 23:49 ` Andrew Lunn [this message]
2017-07-28 23:57 ` Salil Mehta
2017-07-31 15:05 ` Salil Mehta
2017-07-28 22:26 ` [PATCH V5 net-next 8/8] net: hns3: Add HNS3 driver to kernel build framework & MAINTAINERS Salil Mehta
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=20170728234922.GC16080@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=huangdaode@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lipeng321@huawei.com \
--cc=mehta.salil.lnk@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=yisen.zhuang@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