From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] staging: mt7621-eth: Fix sparse warning in ethtool.c
Date: Thu, 29 Mar 2018 11:56:37 +0200 [thread overview]
Message-ID: <20180329095637.GA16778@kroah.com> (raw)
In-Reply-To: <20180328211848.11085-1-cmc@babblebit.net>
On Wed, Mar 28, 2018 at 10:18:48PM +0100, Chris Coffey wrote:
> Include the local ethtool.h header file in mtk_eth_soc.h so
> implementation files have centralized access to it.
>
> This fixes the following sparse warning:
>
> drivers/staging/mt7621-eth/ethtool.c:213:6: warning: symbol
> 'mtk_set_ethtool_ops' was not declared. Should it be static?
>
> Signed-off-by: Chris Coffey <cmc@babblebit.net>
> ---
> drivers/staging/mt7621-eth/mtk_eth_soc.c | 1 -
> drivers/staging/mt7621-eth/mtk_eth_soc.h | 1 +
> 2 files changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/mt7621-eth/mtk_eth_soc.c b/drivers/staging/mt7621-eth/mtk_eth_soc.c
> index cbc7339843..0574e71573 100644
> --- a/drivers/staging/mt7621-eth/mtk_eth_soc.c
> +++ b/drivers/staging/mt7621-eth/mtk_eth_soc.c
> @@ -35,7 +35,6 @@
>
> #include "mtk_eth_soc.h"
> #include "mdio.h"
> -#include "ethtool.h"
How about just moving ethtool.h above the mtk_eth_soc.h include?
Putting .h file dependancies in other .h files is generally not a good
idea if at all possible. Keeping them "clean" is better, and this
driver has a bunch of work to go there, so let's not make it worse :)
thanks,
greg k-h
next prev parent reply other threads:[~2018-03-29 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 21:18 [PATCH] staging: mt7621-eth: Fix sparse warning in ethtool.c Chris Coffey
2018-03-29 9:56 ` Greg Kroah-Hartman [this message]
2018-03-29 12:47 ` [PATCH v2] " Chris Coffey
2018-04-01 23:34 ` NeilBrown
2018-04-02 3:04 ` Sean Wang
2018-04-02 3:41 ` NeilBrown
2018-04-02 11:41 ` Christian Lütke-Stetzkamp
2018-04-02 22:39 ` NeilBrown
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=20180329095637.GA16778@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).