Linux IIO development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Claudiu <claudiu.beznea@tuxon.dev>,
	gregkh@linuxfoundation.org, rafael@kernel.org, dakr@kernel.org,
	len.brown@intel.com, pavel@kernel.org, ulf.hansson@linaro.org,
	jic23@kernel.org, daniel.lezcano@linaro.org,
	dmitry.torokhov@gmail.com
Cc: oe-kbuild-all@lists.linux.dev, claudiu.beznea@tuxon.dev,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-iio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	bhelgaas@google.com, geert@linux-m68k.org,
	Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Subject: Re: [PATCH v2 1/2] PM: domains: Add devres variant for dev_pm_domain_attach()
Date: Tue, 27 May 2025 04:34:27 +0800	[thread overview]
Message-ID: <202505270434.ft8ekK9H-lkp@intel.com> (raw)
In-Reply-To: <20250526122054.65532-2-claudiu.beznea.uj@bp.renesas.com>

Hi Claudiu,

kernel test robot noticed the following build warnings:

[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on rafael-pm/bleeding-edge driver-core/driver-core-testing driver-core/driver-core-next driver-core/driver-core-linus amd-pstate/linux-next amd-pstate/bleeding-edge linus/master v6.15 next-20250526]
[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/Claudiu/PM-domains-Add-devres-variant-for-dev_pm_domain_attach/20250526-202318
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link:    https://lore.kernel.org/r/20250526122054.65532-2-claudiu.beznea.uj%40bp.renesas.com
patch subject: [PATCH v2 1/2] PM: domains: Add devres variant for dev_pm_domain_attach()
config: arm-randconfig-002-20250527 (https://download.01.org/0day-ci/archive/20250527/202505270434.ft8ekK9H-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250527/202505270434.ft8ekK9H-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/202505270434.ft8ekK9H-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from drivers/amba/bus.c:15:0:
>> include/linux/pm_domain.h:534:12: warning: 'devm_pm_domain_attach' defined but not used [-Wunused-function]
    static int devm_pm_domain_attach(struct device *dev, bool attach_power_on,
               ^~~~~~~~~~~~~~~~~~~~~


vim +/devm_pm_domain_attach +534 include/linux/pm_domain.h

   533	
 > 534	static int devm_pm_domain_attach(struct device *dev, bool attach_power_on,
   535					 bool detach_power_off)
   536	{
   537		return 0;
   538	}
   539	

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

  reply	other threads:[~2025-05-26 20:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26 12:20 [PATCH v2 0/2] PM: domains: add devm_pm_domain_attach() Claudiu
2025-05-26 12:20 ` [PATCH v2 1/2] PM: domains: Add devres variant for dev_pm_domain_attach() Claudiu
2025-05-26 20:34   ` kernel test robot [this message]
2025-05-27 21:27   ` Dmitry Torokhov
2025-05-28  9:31     ` Ulf Hansson
2025-05-28 12:19       ` Claudiu Beznea
2025-05-28 12:18     ` Claudiu Beznea
2025-05-28 16:04       ` Ulf Hansson
2025-05-28 16:09         ` Dmitry Torokhov
2025-05-30  9:17           ` Ulf Hansson
2025-05-26 12:20 ` [PATCH v2 2/2] driver core: platform: Use devm_pm_domain_attach() Claudiu

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=202505270434.ft8ekK9H-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bhelgaas@google.com \
    --cc=claudiu.beznea.uj@bp.renesas.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=dakr@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=len.brown@intel.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pavel@kernel.org \
    --cc=rafael@kernel.org \
    --cc=ulf.hansson@linaro.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