From: Bartosz Golaszewski <brgl@bgdev.pl>
To: kernel test robot <lkp@intel.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
oe-kbuild-all@lists.linux.dev, linux-gpio@vger.kernel.org
Subject: Re: [brgl:gpio/for-next 38/38] drivers/gpio/gpio-virtuser.c:400:24: warning: variable 'trimmed' set but not used
Date: Tue, 9 Jul 2024 17:13:17 +0200 [thread overview]
Message-ID: <CAMRc=Mf_j0qTk8_q37uvbRyWHK_5M2D-dF_6hiELSBRGcy5KKg@mail.gmail.com> (raw)
In-Reply-To: <202407092245.BPnW2mr6-lkp@intel.com>
On Tue, Jul 9, 2024 at 4:22 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
> head: 337049890b8cbbb4fb527c58976ea19f4dc747a0
> commit: 91581c4b3f29e2e22aeb1a62e842d529ca638b2d [38/38] gpio: virtuser: new virtual testing driver for the GPIO API
> config: microblaze-allmodconfig (https://download.01.org/0day-ci/archive/20240709/202407092245.BPnW2mr6-lkp@intel.com/config)
> compiler: microblaze-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240709/202407092245.BPnW2mr6-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202407092245.BPnW2mr6-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> drivers/gpio/gpio-virtuser.c: In function 'gpio_virtuser_direction_do_write':
> >> drivers/gpio/gpio-virtuser.c:400:24: warning: variable 'trimmed' set but not used [-Wunused-but-set-variable]
> 400 | char buf[32], *trimmed;
> | ^~~~~~~
>
>
> vim +/trimmed +400 drivers/gpio/gpio-virtuser.c
>
Fix sent out.
Bart
prev parent reply other threads:[~2024-07-09 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 14:21 [brgl:gpio/for-next 38/38] drivers/gpio/gpio-virtuser.c:400:24: warning: variable 'trimmed' set but not used kernel test robot
2024-07-09 15:13 ` Bartosz Golaszewski [this message]
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='CAMRc=Mf_j0qTk8_q37uvbRyWHK_5M2D-dF_6hiELSBRGcy5KKg@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=bartosz.golaszewski@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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).