From: kernel test robot <lkp@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Marc Zyngier <maz@kernel.org>
Subject: drivers/gpio/gpio-xilinx.c:75: warning: Excess struct member 'irqchip' description in 'xgpio_instance'
Date: Fri, 15 Dec 2023 02:29:11 +0800 [thread overview]
Message-ID: <202312150239.IyuTVvrL-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 5bd7ef53ffe5ca580e93e74eb8c81ed191ddc4bd
commit: b4510f8fd5d0e9afa777f115871f5d522540c417 gpio: xilinx: Convert to immutable irq_chip
date: 9 months ago
config: arm-randconfig-r081-20231214 (https://download.01.org/0day-ci/archive/20231215/202312150239.IyuTVvrL-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231215/202312150239.IyuTVvrL-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/202312150239.IyuTVvrL-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpio/gpio-xilinx.c:75: warning: Excess struct member 'irqchip' description in 'xgpio_instance'
vim +75 drivers/gpio/gpio-xilinx.c
74600ee017557b drivers/gpio/gpio-xilinx.c Michal Simek 2013-06-03 43
74600ee017557b drivers/gpio/gpio-xilinx.c Michal Simek 2013-06-03 44 /**
74600ee017557b drivers/gpio/gpio-xilinx.c Michal Simek 2013-06-03 45 * struct xgpio_instance - Stores information about GPIO device
1ebd06871b57a6 drivers/gpio/gpio-xilinx.c Robert Hancock 2019-06-07 46 * @gc: GPIO chip
1ebd06871b57a6 drivers/gpio/gpio-xilinx.c Robert Hancock 2019-06-07 47 * @regs: register block
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 48 * @hw_map: GPIO pin mapping on hardware side
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 49 * @sw_map: GPIO pin mapping on software side
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 50 * @state: GPIO write state shadow register
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 51 * @last_irq_read: GPIO read state register from last interrupt
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 52 * @dir: GPIO direction shadow register
4ae798fae200f1 drivers/gpio/gpio-xilinx.c Ricardo Ribalda 2014-12-17 53 * @gpio_lock: Lock used for synchronization
a32c7caea292c4 drivers/gpio/gpio-xilinx.c Srinivas Neeli 2021-01-29 54 * @irq: IRQ used by GPIO device
a32c7caea292c4 drivers/gpio/gpio-xilinx.c Srinivas Neeli 2021-01-29 55 * @irqchip: IRQ chip
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 56 * @enable: GPIO IRQ enable/disable bitfield
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 57 * @rising_edge: GPIO IRQ rising edge enable/disable bitfield
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 58 * @falling_edge: GPIO IRQ falling edge enable/disable bitfield
65bbe531b54668 drivers/gpio/gpio-xilinx.c Srinivas Neeli 2020-11-12 59 * @clk: clock resource for this driver
74600ee017557b drivers/gpio/gpio-xilinx.c Michal Simek 2013-06-03 60 */
0bcb6069a6e1af drivers/gpio/xilinx_gpio.c John Linn 2008-11-12 61 struct xgpio_instance {
1ebd06871b57a6 drivers/gpio/gpio-xilinx.c Robert Hancock 2019-06-07 62 struct gpio_chip gc;
1ebd06871b57a6 drivers/gpio/gpio-xilinx.c Robert Hancock 2019-06-07 63 void __iomem *regs;
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 64 DECLARE_BITMAP(hw_map, 64);
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 65 DECLARE_BITMAP(sw_map, 64);
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 66 DECLARE_BITMAP(state, 64);
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 67 DECLARE_BITMAP(last_irq_read, 64);
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 68 DECLARE_BITMAP(dir, 64);
37ef3346808002 drivers/gpio/gpio-xilinx.c Srinivas Neeli 2021-01-29 69 spinlock_t gpio_lock; /* For serializing operations */
a32c7caea292c4 drivers/gpio/gpio-xilinx.c Srinivas Neeli 2021-01-29 70 int irq;
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 71 DECLARE_BITMAP(enable, 64);
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 72 DECLARE_BITMAP(rising_edge, 64);
02b3f84d9080b0 drivers/gpio/gpio-xilinx.c Andy Shevchenko 2021-05-10 73 DECLARE_BITMAP(falling_edge, 64);
65bbe531b54668 drivers/gpio/gpio-xilinx.c Srinivas Neeli 2020-11-12 74 struct clk *clk;
749564ffd52d91 drivers/gpio/gpio-xilinx.c Ricardo Ribalda 2014-12-17 @75 };
749564ffd52d91 drivers/gpio/gpio-xilinx.c Ricardo Ribalda 2014-12-17 76
:::::: The code at line 75 was first introduced by commit
:::::: 749564ffd52d91ddf9917315e6fba2a3dcf3137e gpio/xilinx: Convert the driver to platform device interface
:::::: TO: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
:::::: CC: Linus Walleij <linus.walleij@linaro.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-14 18:30 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=202312150239.IyuTVvrL-lkp@intel.com \
--to=lkp@intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--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.