From: "Neftin, Sasha" <sasha.neftin@intel.com>
To: Wei Yongjun <weiyongjun1@huawei.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net-next] igc: Make function igc_write_rss_indir_tbl() static
Date: Sun, 17 Feb 2019 12:06:21 +0200 [thread overview]
Message-ID: <6ef2f327-8dc6-4c86-f42d-4aa7508d19f5@intel.com> (raw)
In-Reply-To: <20190216020442.14206-1-weiyongjun1@huawei.com>
On 2/16/2019 04:04, Wei Yongjun wrote:
> Fixes the following sparse warning:
>
> drivers/net/ethernet/intel/igc/igc_ethtool.c:646:6: warning:
> symbol 'igc_write_rss_indir_tbl' was not declared. Should it be static?
>
> Fixes: 8c5ad0dae93c ("igc: Add ethtool support")
> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
> ---
> drivers/net/ethernet/intel/igc/igc_ethtool.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/igc/igc_ethtool.c b/drivers/net/ethernet/intel/igc/igc_ethtool.c
> index eff37a6c0afa..544239422577 100644
> --- a/drivers/net/ethernet/intel/igc/igc_ethtool.c
> +++ b/drivers/net/ethernet/intel/igc/igc_ethtool.c
> @@ -643,7 +643,7 @@ static int igc_set_coalesce(struct net_device *netdev,
> return 0;
> }
>
> -void igc_write_rss_indir_tbl(struct igc_adapter *adapter)
> +static void igc_write_rss_indir_tbl(struct igc_adapter *adapter)
> {
> struct igc_hw *hw = &adapter->hw;
> u32 reg = IGC_RETA(0);
>
>
> NACK
'igc_write_rss_indir_tbl' method declared in igc.h file. This method
used in both igc_ethtool.c and igc_main.c and can't be a 'static'
next prev parent reply other threads:[~2019-02-17 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 2:04 [PATCH net-next] igc: Make function igc_write_rss_indir_tbl() static Wei Yongjun
2019-02-17 10:06 ` Neftin, Sasha [this message]
2019-02-17 10:59 ` [Intel-wired-lan] " Neftin, Sasha
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=6ef2f327-8dc6-4c86-f42d-4aa7508d19f5@intel.com \
--to=sasha.neftin@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=weiyongjun1@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;
as well as URLs for NNTP newsgroup(s).