From: Gaston Gonzalez <gascoar@gmail.com>
To: linux-staging@lists.linux.dev
Cc: dpenkler@gmail.com, gregkh@linuxfoundation.org, arnd@arndb.de,
dan.carpenter@linaro.org, ajithpv.linux@gmail.com,
roheetchavan@gmail.com, niharchaithanya@gmail.com,
eleanor15x@gmail.com, everestkc@everestkc.com.np,
kees@ijzerbout.nl, skhan@linuxfoundation.org,
linux-kernel@vger.kernel.org, gascoar@gmail.com
Subject: [PATCH v2 0/5] staging: gpib: remove unused variables
Date: Fri, 14 Feb 2025 16:54:38 -0300 [thread overview]
Message-ID: <20250214195456.104075-1-gascoar@gmail.com> (raw)
Remove some unused variables found compiling with W=1.
v1 -> v2:
Address Kees Bakker review:
- Keep the post increment expression (i++) in patch 3.
- Keep the call to nec7210_update_status_nolock() in patch 4.
Gaston Gonzalez (5):
staging: gpib: cb7210: remove unused variable
staging: gpib: eastwood: remove unused variable
staging: gpib: ni_usb: remove unused variable
staging: gpib: tnt4882: remove unused variable
staging: gpib: ines: remove unused variable
drivers/staging/gpib/cb7210/cb7210.c | 2 --
drivers/staging/gpib/eastwood/fluke_gpib.c | 2 --
drivers/staging/gpib/ines/ines_gpib.c | 2 --
drivers/staging/gpib/ni_usb/ni_usb_gpib.c | 3 +--
drivers/staging/gpib/tnt4882/tnt4882_gpib.c | 3 +--
5 files changed, 2 insertions(+), 10 deletions(-)
--
2.48.1
next reply other threads:[~2025-02-14 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 19:54 Gaston Gonzalez [this message]
2025-02-14 19:54 ` [PATCH v2 1/5] staging: gpib: cb7210: remove unused variable Gaston Gonzalez
2025-02-14 19:54 ` [PATCH v2 2/5] staging: gpib: eastwood: " Gaston Gonzalez
2025-02-14 19:54 ` [PATCH v2 3/5] staging: gpib: ni_usb: " Gaston Gonzalez
2025-02-14 19:54 ` [PATCH v2 4/5] staging: gpib: tnt4882: " Gaston Gonzalez
2025-02-14 19:54 ` [PATCH v2 5/5] staging: gpib: ines: " Gaston Gonzalez
2025-02-16 15:11 ` [PATCH v2 0/5] staging: gpib: remove unused variables Dan Carpenter
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=20250214195456.104075-1-gascoar@gmail.com \
--to=gascoar@gmail.com \
--cc=ajithpv.linux@gmail.com \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=dpenkler@gmail.com \
--cc=eleanor15x@gmail.com \
--cc=everestkc@everestkc.com.np \
--cc=gregkh@linuxfoundation.org \
--cc=kees@ijzerbout.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=niharchaithanya@gmail.com \
--cc=roheetchavan@gmail.com \
--cc=skhan@linuxfoundation.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