devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Tzuyi Chang <tychang@realtek.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Andy Shevchenko <andy@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	TY Chang <tychang@realtek.com>
Subject: Re: [PATCH v2 2/2] Add GPIO support for Realtek DHC(Digital Home Center) RTD SoCs.
Date: Fri, 17 Nov 2023 06:56:58 +0800	[thread overview]
Message-ID: <202311170603.TawAUggC-lkp@intel.com> (raw)
In-Reply-To: <20231116111441.2339-3-tychang@realtek.com>

Hi Tzuyi,

kernel test robot noticed the following build warnings:

[auto build test WARNING on brgl/gpio/for-next]
[also build test WARNING on robh/for-next linus/master v6.7-rc1 next-20231116]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Tzuyi-Chang/dt-bindings-gpio-realtek-Add-realtek-rtd-gpio/20231116-191928
base:   https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
patch link:    https://lore.kernel.org/r/20231116111441.2339-3-tychang%40realtek.com
patch subject: [PATCH v2 2/2] Add GPIO support for Realtek DHC(Digital Home Center) RTD SoCs.
config: arm-allmodconfig (https://download.01.org/0day-ci/archive/20231117/202311170603.TawAUggC-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/20231117/202311170603.TawAUggC-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/202311170603.TawAUggC-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpio/gpio-rtd.c:71: warning: Function parameter or member 'num_dir' not described in 'rtd_gpio_info'
>> drivers/gpio/gpio-rtd.c:71: warning: Function parameter or member 'num_dato' not described in 'rtd_gpio_info'
>> drivers/gpio/gpio-rtd.c:71: warning: Function parameter or member 'num_dati' not described in 'rtd_gpio_info'
>> drivers/gpio/gpio-rtd.c:71: warning: Function parameter or member 'num_ie' not described in 'rtd_gpio_info'
>> drivers/gpio/gpio-rtd.c:71: warning: Function parameter or member 'num_dp' not described in 'rtd_gpio_info'
>> drivers/gpio/gpio-rtd.c:71: warning: Function parameter or member 'num_gpa' not described in 'rtd_gpio_info'
>> drivers/gpio/gpio-rtd.c:71: warning: Function parameter or member 'num_gpda' not described in 'rtd_gpio_info'
>> drivers/gpio/gpio-rtd.c:71: warning: Function parameter or member 'num_deb' not described in 'rtd_gpio_info'


vim +71 drivers/gpio/gpio-rtd.c

    34	
    35	/**
    36	 * struct rtd_gpio_info - Specific GPIO register information
    37	 * @name: GPIO device name
    38	 * @type: RTD GPIO ID
    39	 * @gpio_base: GPIO base number
    40	 * @num_gpios: Number of GPIOs
    41	 * @dir_offset: Offset for GPIO direction registers
    42	 * @dato_offset: Offset for GPIO data output registers
    43	 * @dati_offset: Offset for GPIO data input registers
    44	 * @ie_offset: Offset for GPIO interrupt enable registers
    45	 * @dp_offset: Offset for GPIO detection polarity registers
    46	 * @gpa_offset: Offset for GPIO assert interrupt status registers
    47	 * @gpda_offset: Offset for GPIO deassert interrupt status registers
    48	 * @deb_offset: Offset for GPIO debounce registers
    49	 */
    50	struct rtd_gpio_info {
    51		const char		*name;
    52		enum rtd_gpio_type	type;
    53		unsigned int		gpio_base;
    54		unsigned int		num_gpios;
    55		u8			*dir_offset;
    56		u8			num_dir;
    57		u8			*dato_offset;
    58		u8			num_dato;
    59		u8			*dati_offset;
    60		u8			num_dati;
    61		u8			*ie_offset;
    62		u8			num_ie;
    63		u8			*dp_offset;
    64		u8			num_dp;
    65		u8			*gpa_offset;
    66		u8			num_gpa;
    67		u8			*gpda_offset;
    68		u8			num_gpda;
    69		u8			*deb_offset;
    70		u8			num_deb;
  > 71	};
    72	

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

  reply	other threads:[~2023-11-16 22:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 11:14 [PATCH v2 0/2] Add gpio driver support for Realtek DHC SoCs Tzuyi Chang
2023-11-16 11:14 ` [PATCH v2 1/2] dt-bindings: gpio: realtek: Add realtek,rtd-gpio Tzuyi Chang
2023-11-16 12:01   ` Krzysztof Kozlowski
2023-11-21  7:07     ` TY_Chang[張子逸]
2023-11-16 11:14 ` [PATCH v2 2/2] Add GPIO support for Realtek DHC(Digital Home Center) RTD SoCs Tzuyi Chang
2023-11-16 22:56   ` kernel test robot [this message]
2023-11-24  9:38   ` Linus Walleij
2023-11-24 11:31     ` Andy Shevchenko
2023-12-01  1:50       ` TY_Chang[張子逸]
2023-12-01  1:44     ` TY_Chang[張子逸]

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=202311170603.TawAUggC-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andy@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=robh+dt@kernel.org \
    --cc=tychang@realtek.com \
    /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).