public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-acpi@vger.kernel.org,
	devel@acpica.org, linux-pm@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: [rafael-pm:bleeding-edge 1764/1779] drivers/thermal/thermal_debugfs.c:149: warning: Function parameter or member 'tz_episodes' not described in 'tz_debugfs'
Date: Wed, 10 Jan 2024 15:17:24 +0800	[thread overview]
Message-ID: <202401101509.DstqlL7i-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
head:   335ccbd84e3d5491e06eaf60e3f6be2ef657a495
commit: 15c1b25dd5fa2735060be35c7022bfbea4978a55 [1764/1779] thermal/debugfs: Add thermal debugfs information for mitigation episodes
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20240110/202401101509.DstqlL7i-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240110/202401101509.DstqlL7i-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/202401101509.DstqlL7i-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/thermal/thermal_debugfs.c:149: warning: Function parameter or member 'tz_episodes' not described in 'tz_debugfs'


vim +149 drivers/thermal/thermal_debugfs.c

   129	
   130	/**
   131	 * struct tz_debugfs - Store all mitigation episodes for a thermal zone
   132	 *
   133	 * The tz_debugfs structure contains the list of the mitigation
   134	 * episodes and has to track which trip point has been crossed in
   135	 * order to handle correctly nested trip point mitigation episodes.
   136	 *
   137	 * We keep the history of the trip point crossed in an array and as we
   138	 * can go back and forth inside this history, eg. trip 0,1,2,1,2,1,0,
   139	 * we keep track of the current position in the history array.
   140	 *
   141	 * @tz_episode: a list of thermal mitigation episodes
   142	 * @trips_crossed: an array of trip points crossed by id
   143	 * @nr_trips: the number of trip points currently being crossed
   144	 */
   145	struct tz_debugfs {
   146		struct list_head tz_episodes;
   147		int *trips_crossed;
   148		int nr_trips;
 > 149	};
   150	

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

                 reply	other threads:[~2024-01-10  7:28 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=202401101509.DstqlL7i-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devel@acpica.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rjw@rjwysocki.net \
    /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