linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	Tzung-Bi Shih <tzungbi@kernel.org>
Subject: [linux-next:master 5497/9113] drivers/pwm/pwm-cros-ec.c:32: warning: Excess struct member 'dev' description in 'cros_ec_pwm_device'
Date: Tue, 19 Dec 2023 07:47:33 +0800	[thread overview]
Message-ID: <202312190757.O4M9dsln-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   ceb2fe0d438644e1de06b9a6468a1fb8e2199c70
commit: ffb150737feec5fec221022cbb4ca62ca60092b5 [5497/9113] pwm: cros-ec: Drop unused member from driver private data
config: arm-randconfig-c003-20211105 (https://download.01.org/0day-ci/archive/20231219/202312190757.O4M9dsln-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/20231219/202312190757.O4M9dsln-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/202312190757.O4M9dsln-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/pwm/pwm-cros-ec.c:32: warning: Excess struct member 'dev' description in 'cros_ec_pwm_device'


vim +32 drivers/pwm/pwm-cros-ec.c

3d593b6e80ad2c Fabio Baltieri   2022-04-28  17  
1f0d3bb02785f6 Brian Norris     2016-07-15  18  /**
1f0d3bb02785f6 Brian Norris     2016-07-15  19   * struct cros_ec_pwm_device - Driver data for EC PWM
1f0d3bb02785f6 Brian Norris     2016-07-15  20   *
1f0d3bb02785f6 Brian Norris     2016-07-15  21   * @dev: Device node
1f0d3bb02785f6 Brian Norris     2016-07-15  22   * @ec: Pointer to EC device
1f0d3bb02785f6 Brian Norris     2016-07-15  23   * @chip: PWM controller chip
3d593b6e80ad2c Fabio Baltieri   2022-04-28  24   * @use_pwm_type: Use PWM types instead of generic channels
82adc1b2688b02 Uwe Kleine-König 2023-07-05  25   * @channel: array with per-channel data
1f0d3bb02785f6 Brian Norris     2016-07-15  26   */
1f0d3bb02785f6 Brian Norris     2016-07-15  27  struct cros_ec_pwm_device {
1f0d3bb02785f6 Brian Norris     2016-07-15  28  	struct cros_ec_device *ec;
1f0d3bb02785f6 Brian Norris     2016-07-15  29  	struct pwm_chip chip;
3d593b6e80ad2c Fabio Baltieri   2022-04-28  30  	bool use_pwm_type;
82adc1b2688b02 Uwe Kleine-König 2023-07-05  31  	struct cros_ec_pwm *channel;
1f0d3bb02785f6 Brian Norris     2016-07-15 @32  };
1f0d3bb02785f6 Brian Norris     2016-07-15  33  

:::::: The code at line 32 was first introduced by commit
:::::: 1f0d3bb02785f698dc273b9006a473194c32f874 pwm: Add ChromeOS EC PWM driver

:::::: TO: Brian Norris <briannorris@chromium.org>
:::::: CC: Thierry Reding <thierry.reding@gmail.com>

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


                 reply	other threads:[~2023-12-18 23:47 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=202312190757.O4M9dsln-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=thierry.reding@gmail.com \
    --cc=tzungbi@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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