From: sunliming@linux.dev
To: dpenkler@gmail.com, gregkh@linuxfoundation.org, arnd@arndb.de,
dan.carpenter@linaro.org, everestkc@everestkc.com.np,
niharchaithanya@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: sunliming <sunliming@kylinos.cn>, kernel test robot <lkp@intel.com>
Subject: [PATCH] staging: gpib: warning: variable 'nec_priv' set but not used warning
Date: Fri, 21 Mar 2025 09:06:49 +0800 [thread overview]
Message-ID: <20250321010649.10918-1-sunliming@linux.dev> (raw)
From: sunliming <sunliming@kylinos.cn>
Fix below kernel warning:
drivers/staging/gpib/eastwood/fluke_gpib.c:196:23: warning: variable 'nec_priv' set but not
used [-Wunused-but-set-variable]
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: sunliming <sunliming@kylinos.cn>
---
drivers/staging/gpib/eastwood/fluke_gpib.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/gpib/eastwood/fluke_gpib.c b/drivers/staging/gpib/eastwood/fluke_gpib.c
index 0304c5de4ccd..6854a745ccff 100644
--- a/drivers/staging/gpib/eastwood/fluke_gpib.c
+++ b/drivers/staging/gpib/eastwood/fluke_gpib.c
@@ -194,10 +194,8 @@ static int fluke_line_status(const gpib_board_t *board)
int status = ValidALL;
int bsr_bits;
struct fluke_priv *e_priv;
- struct nec7210_priv *nec_priv;
e_priv = board->private_data;
- nec_priv = &e_priv->nec7210_priv;
bsr_bits = fluke_paged_read_byte(e_priv, BUS_STATUS, BUS_STATUS_PAGE);
--
2.25.1
next reply other threads:[~2025-03-21 1:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 1:06 sunliming [this message]
2025-04-03 14:08 ` [PATCH] staging: gpib: warning: variable 'nec_priv' set but not used warning Greg KH
2025-04-04 6:08 ` Sunliming
2025-04-04 7:53 ` Dan Carpenter
2025-04-04 9:15 ` sunliming
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=20250321010649.10918-1-sunliming@linux.dev \
--to=sunliming@linux.dev \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=dpenkler@gmail.com \
--cc=everestkc@everestkc.com.np \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lkp@intel.com \
--cc=niharchaithanya@gmail.com \
--cc=sunliming@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.