From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18-2026-09 14/14] drivers/pinctrl/renesas/pinctrl-rzt2h.c:670:25: warning: variable 'j' set but not used
Date: Thu, 17 Sep 2026 22:10:07 +0800 [thread overview]
Message-ID: <202609172124.kLi32PmY-lkp@intel.com> (raw)
Hi Thierry,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android17-6.18-2026-09
head: ee03b8f987e082acff09f2c63b41ab66e0fd8208
commit: 34d4d093077a5c60d452a2f42d0c1a08e55b8614 [14/14] pinctrl: renesas: Add support for RZ/T2H
config: arm64-defconfig (https://download.01.org/0day-ci/archive/20260917/202609172124.kLi32PmY-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260917/202609172124.kLi32PmY-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
| Fixes: 34d4d093077a ("pinctrl: renesas: Add support for RZ/T2H")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609172124.kLi32PmY-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/pinctrl/renesas/pinctrl-rzt2h.c: In function 'rzt2h_pinctrl_register':
>> drivers/pinctrl/renesas/pinctrl-rzt2h.c:670:25: warning: variable 'j' set but not used [-Wunused-but-set-variable=]
670 | unsigned int i, j;
| ^
vim +/j +670 drivers/pinctrl/renesas/pinctrl-rzt2h.c
664
665 static int rzt2h_pinctrl_register(struct rzt2h_pinctrl *pctrl)
666 {
667 struct pinctrl_desc *desc = &pctrl->desc;
668 struct device *dev = pctrl->dev;
669 struct pinctrl_pin_desc *pins;
> 670 unsigned int i, j;
671 int ret;
672
673 desc->name = DRV_NAME;
674 desc->npins = pctrl->data->n_port_pins;
675 desc->pctlops = &rzt2h_pinctrl_pctlops;
676 desc->pmxops = &rzt2h_pinctrl_pmxops;
677 desc->owner = THIS_MODULE;
678
679 pins = devm_kcalloc(dev, desc->npins, sizeof(*pins), GFP_KERNEL);
680 if (!pins)
681 return -ENOMEM;
682
683 pctrl->pins = pins;
684 desc->pins = pins;
685
686 for (i = 0, j = 0; i < pctrl->data->n_port_pins; i++) {
687 pins[i].number = i;
688 pins[i].name = rzt2h_gpio_names[i];
689 if (i && !(i % RZT2H_PINS_PER_PORT))
690 j++;
691 }
692
693 ret = devm_pinctrl_register_and_init(dev, desc, pctrl, &pctrl->pctl);
694 if (ret)
695 return dev_err_probe(dev, ret, "pinctrl registration failed\n");
696
697 ret = pinctrl_enable(pctrl->pctl);
698 if (ret)
699 return dev_err_probe(dev, ret, "pinctrl enable failed\n");
700
701 return rzt2h_gpio_register(pctrl);
702 }
703
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-17 14:11 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=202609172124.kLi32PmY-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.