All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Daniel Palmer <daniel@0x0f.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chenxing:mstar_v6_5_reorder 290/700] drivers/gpio/gpio-ssd210.c:448:22: warning: unused variable 'offset'
Date: Sat, 01 Aug 2026 17:41:58 +0800	[thread overview]
Message-ID: <202608011730.fftfW3p0-lkp@intel.com> (raw)

tree:   https://github.com/linux-chenxing/linux.git mstar_v6_5_reorder
head:   1a5c60e65ea399670a5384b869c4958338af2799
commit: 2833a14b64ac977478b34e1993f75fe0a2aaa4b9 [290/700] gpio: mstar: ssd210 gpio support
config: nios2-allmodconfig (https://download.01.org/0day-ci/archive/20260801/202608011730.fftfW3p0-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260801/202608011730.fftfW3p0-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/202608011730.fftfW3p0-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/gpio/gpio-ssd210.c: In function 'ssd210_gpio_child_to_parent_hwirq':
>> drivers/gpio/gpio-ssd210.c:448:22: warning: unused variable 'offset' [-Wunused-variable]
     448 |         unsigned int offset = priv->gpio_data->offsets[child];
         |                      ^~~~~~


vim +/offset +448 drivers/gpio/gpio-ssd210.c

   440	
   441	static int ssd210_gpio_child_to_parent_hwirq(struct gpio_chip *chip,
   442						     unsigned int child,
   443						     unsigned int child_type,
   444						     unsigned int *parent,
   445						     unsigned int *parent_type)
   446	{
   447		struct ssd210_gpio *priv = gpiochip_get_data(chip);
 > 448		unsigned int offset = priv->gpio_data->offsets[child];
   449	
   450		return -EINVAL;
   451	}
   452	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-08-01  9:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202608011730.fftfW3p0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=daniel@0x0f.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 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.