From: Helge Deller <deller@gmx.de>
To: Simon Horman <horms@kernel.org>, deller@kernel.org
Cc: netdev@vger.kernel.org, linux-parisc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: tulip: avoid unused variable warning
Date: Wed, 12 Mar 2025 15:08:35 +0100 [thread overview]
Message-ID: <d863db0a-1740-45d5-b8de-746fa9d44fcb@gmx.de> (raw)
In-Reply-To: <20250312131433.GS4159220@kernel.org>
On 3/12/25 14:14, Simon Horman wrote:
> On Sun, Mar 09, 2025 at 10:42:38PM +0100, deller@kernel.org wrote:
>> From: Helge Deller <deller@gmx.de>
>>
>> When compiling with W=1 and CONFIG_TULIP_MWI=n one gets this warning:
>> drivers/net/ethernet/dec/tulip/tulip_core.c: In function ‘tulip_init_one’:
>> drivers/net/ethernet/dec/tulip/tulip_core.c:1309:22: warning: variable ‘force_csr0’ set but not used
>>
>> Avoid it by annotating the variable __maybe_unused, which seems to be
>> the easiest solution.
>>
>> Signed-off-by: Helge Deller <deller@gmx.de>
>
> Hi Helge,
>
> A few thoughts on this:
Hi Simon,
Thanks for following up on this!
> Firstly, thanks for your patch, which I agree addresses the problem you
> have described.
>
> However, AFAIK, this is a rather old driver and I'm not sure that
> addressing somewhat cosmetic problems are worth the churn they cause:
> maybe it's best to leave it be.
Well, the only reason why I sent this patch is, because some people
are interested to get a Linux kernel build without any warnings when "W=1"
option is enabled.
This code in the tulip driver is one of the last 10 places in the kernel where
I see a warning at all, so I think it's worth fixing it, although it's just
cosmetic.
> But if we do want to fix this problem, I do wonder if the following
> solution, which leverages IS_ENABLED, is somehow nicer as
> it slightly reduces the amount of conditionally compiled code,
> thus increasing compile test coverage.
Full Ack from my side!
I wanted to keep my patch small, but your proposed patch is the better one.
I did not compile-test it, but if it builds you may add my:
Acked-by: Helge Deller <deller@gmx.de>
Helge
> diff --git a/drivers/net/ethernet/dec/tulip/tulip_core.c b/drivers/net/ethernet/dec/tulip/tulip_core.c
> index 27e01d780cd0..75eac18ff246 100644
> --- a/drivers/net/ethernet/dec/tulip/tulip_core.c
> +++ b/drivers/net/ethernet/dec/tulip/tulip_core.c
> @@ -1177,7 +1177,6 @@ static void set_rx_mode(struct net_device *dev)
> iowrite32(csr6, ioaddr + CSR6);
> }
>
> -#ifdef CONFIG_TULIP_MWI
> static void tulip_mwi_config(struct pci_dev *pdev, struct net_device *dev)
> {
> struct tulip_private *tp = netdev_priv(dev);
> @@ -1251,7 +1250,6 @@ static void tulip_mwi_config(struct pci_dev *pdev, struct net_device *dev)
> netdev_dbg(dev, "MWI config cacheline=%d, csr0=%08x\n",
> cache, csr0);
> }
> -#endif
>
> /*
> * Chips that have the MRM/reserved bit quirk and the burst quirk. That
> @@ -1463,10 +1461,9 @@ static int tulip_init_one(struct pci_dev *pdev, const struct pci_device_id *ent)
>
> INIT_WORK(&tp->media_work, tulip_tbl[tp->chip_id].media_task);
>
> -#ifdef CONFIG_TULIP_MWI
> - if (!force_csr0 && (tp->flags & HAS_PCI_MWI))
> + if (IS_ENABLED(CONFIG_TULIP_MWI) && !force_csr0 &&
> + (tp->flags & HAS_PCI_MWI))
> tulip_mwi_config (pdev, dev);
> -#endif
>
> /* Stop the chip's Tx and Rx processes. */
> tulip_stop_rxtx(tp);
>
next prev parent reply other threads:[~2025-03-12 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 21:42 deller
2025-03-12 13:14 ` Simon Horman
2025-03-12 14:08 ` Helge Deller [this message]
2025-03-13 10:50 ` Simon Horman
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=d863db0a-1740-45d5-b8de-746fa9d44fcb@gmx.de \
--to=deller@gmx.de \
--cc=deller@kernel.org \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®