public inbox for chrome-platform@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
	Sebastian Reichel <sre@kernel.org>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Benson Leung <bleung@chromium.org>,
	Tzung-Bi Shih <tzungbi@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	"Oleksij Rempel" <o.rempel@pengutronix.de>,
	"Matti Vaittinen" <matti.vaittinen@fi.rohmeurope.com>,
	"Matti Vaittinen" <mazziesaccount@gmail.com>,
	"Mark Brown" <broonie@kernel.org>,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Zhang Rui" <rui.zhang@intel.com>,
	"Lukasz Luba" <lukasz.luba@arm.com>,
	linux-pm@vger.kernel.org, "Søren Andersen" <san@skov.dk>,
	"Guenter Roeck" <groeck@chromium.org>,
	"Ahmad Fatoum" <a.fatoum@pengutronix.de>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	chrome-platform@lists.linux.dev
Subject: Re: [PATCH v10 2/7] reboot: hw_protection_trigger: use standardized numeric shutdown/reboot reasons instead of strings
Date: Wed, 18 Jun 2025 04:41:41 +0800	[thread overview]
Message-ID: <202506180402.ly0g2TQe-lkp@intel.com> (raw)
In-Reply-To: <20250617094945.3619360-3-o.rempel@pengutronix.de>

Hi Oleksij,

kernel test robot noticed the following build warnings:

[auto build test WARNING on sre-power-supply/for-next]
[also build test WARNING on broonie-regulator/for-next chrome-platform/for-next chrome-platform/for-firmware-next linus/master v6.16-rc2 next-20250617]
[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/Oleksij-Rempel/power-Extend-power_on_reason-h-for-upcoming-PSCRR-framework/20250617-175433
base:   https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git for-next
patch link:    https://lore.kernel.org/r/20250617094945.3619360-3-o.rempel%40pengutronix.de
patch subject: [PATCH v10 2/7] reboot: hw_protection_trigger: use standardized numeric shutdown/reboot reasons instead of strings
config: hexagon-randconfig-001-20250618 (https://download.01.org/0day-ci/archive/20250618/202506180402.ly0g2TQe-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250618/202506180402.ly0g2TQe-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/202506180402.ly0g2TQe-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/regulator/core.c:5280:2: warning: unannotated fall-through between switch labels [-Wimplicit-fallthrough]
    5280 |         default:
         |         ^
   drivers/regulator/core.c:5280:2: note: insert '__attribute__((fallthrough));' to silence this warning
    5280 |         default:
         |         ^
         |         __attribute__((fallthrough)); 
   drivers/regulator/core.c:5280:2: note: insert 'break;' to avoid fall-through
    5280 |         default:
         |         ^
         |         break; 
   1 warning generated.


vim +5280 drivers/regulator/core.c

  5253	
  5254	/**
  5255	 * regulator_handle_critical - Handle events for system-critical regulators.
  5256	 * @rdev: The regulator device.
  5257	 * @event: The event being handled.
  5258	 *
  5259	 * This function handles critical events such as under-voltage, over-current,
  5260	 * and unknown errors for regulators deemed system-critical. On detecting such
  5261	 * events, it triggers a hardware protection shutdown with a defined timeout.
  5262	 */
  5263	static void regulator_handle_critical(struct regulator_dev *rdev,
  5264					      unsigned long event)
  5265	{
  5266		enum psc_reason pscr;
  5267	
  5268		if (!rdev->constraints->system_critical)
  5269			return;
  5270	
  5271		switch (event) {
  5272		case REGULATOR_EVENT_UNDER_VOLTAGE:
  5273			pscr = PSCR_UNDER_VOLTAGE;
  5274			break;
  5275		case REGULATOR_EVENT_OVER_CURRENT:
  5276			pscr = PSCR_OVER_CURRENT;
  5277			break;
  5278		case REGULATOR_EVENT_FAIL:
  5279			pscr = PSCR_REGULATOR_FAILURE;
> 5280		default:
  5281			pscr = PSCR_UNKNOWN;
  5282		}
  5283	
  5284		hw_protection_trigger(pscr,
  5285				      rdev->constraints->uv_less_critical_window_ms);
  5286	}
  5287	

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

  reply	other threads:[~2025-06-17 20:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17  9:49 [PATCH v10 0/7] Introduction of PSCR Framework and Related Components Oleksij Rempel
2025-06-17  9:49 ` [PATCH v10 1/7] power: Extend power_on_reason.h for upcoming PSCRR framework Oleksij Rempel
2025-06-17  9:49 ` [PATCH v10 2/7] reboot: hw_protection_trigger: use standardized numeric shutdown/reboot reasons instead of strings Oleksij Rempel
2025-06-17 20:41   ` kernel test robot [this message]
2025-06-17  9:49 ` [PATCH v10 3/7] power: reset: Introduce PSCR Recording Framework for Non-Volatile Storage Oleksij Rempel
2025-06-17  9:49 ` [PATCH v10 4/7] nvmem: provide consumer access to cell size metrics Oleksij Rempel
2025-06-17  9:49 ` [PATCH v10 5/7] nvmem: add support for device and sysfs-based cell lookups Oleksij Rempel
2025-06-17  9:49 ` [PATCH v10 6/7] power: reset: add PSCR NVMEM Driver for Recording Power State Change Reasons Oleksij Rempel
2025-06-17  9:49 ` [PATCH v10 7/7] Documentation: Add sysfs documentation for PSCRR reboot reason tracking Oleksij Rempel

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=202506180402.ly0g2TQe-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=bleung@chromium.org \
    --cc=broonie@kernel.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=daniel.lezcano@linaro.org \
    --cc=groeck@chromium.org \
    --cc=kernel@pengutronix.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=lukasz.luba@arm.com \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=mazziesaccount@gmail.com \
    --cc=o.rempel@pengutronix.de \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=san@skov.dk \
    --cc=sre@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=tzungbi@kernel.org \
    /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