All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Douglas Anderson <dianders@chromium.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH] PM: clk: Avoid lockdep warning between prepare lock and &psd->lock
Date: Fri, 23 Sep 2022 13:53:37 +0800	[thread overview]
Message-ID: <202209231304.p14ZsMhw-lkp@intel.com> (raw)
In-Reply-To: <20220922084941.RFC.1.I206ec946a190e3de9fd13be806498821e9a6612d@changeid>

Hi Douglas,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on clk/clk-next pavel-leds/for-next linus/master v6.0-rc6 next-20220921]
[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/Douglas-Anderson/PM-clk-Avoid-lockdep-warning-between-prepare-lock-and-psd-lock/20220922-235116
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: hexagon-randconfig-r045-20220922 (https://download.01.org/0day-ci/archive/20220923/202209231304.p14ZsMhw-lkp@intel.com/config)
compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 791a7ae1ba3efd6bca96338e10ffde557ba83920)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/intel-lab-lkp/linux/commit/ca0a9a41d27b3cabb3a7f6f4300011844aea2a68
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Douglas-Anderson/PM-clk-Avoid-lockdep-warning-between-prepare-lock-and-psd-lock/20220922-235116
        git checkout ca0a9a41d27b3cabb3a7f6f4300011844aea2a68
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash drivers/clk/

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> drivers/clk/clk.c:153:6: warning: no previous prototype for function '__clk_prepare_lock' [-Wmissing-prototypes]
   void __clk_prepare_lock(void)
        ^
   drivers/clk/clk.c:153:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   void __clk_prepare_lock(void)
   ^
   static 
>> drivers/clk/clk.c:159:6: warning: no previous prototype for function '__clk_prepare_unlock' [-Wmissing-prototypes]
   void __clk_prepare_unlock(void)
        ^
   drivers/clk/clk.c:159:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   void __clk_prepare_unlock(void)
   ^
   static 
   2 warnings generated.


vim +/__clk_prepare_lock +153 drivers/clk/clk.c

   151	
   152	/* Non-static wrapper of lock function for drivers/base/power/clock_ops.c */
 > 153	void __clk_prepare_lock(void)
   154	{
   155		clk_prepare_lock();
   156	}
   157	
   158	/* Non-static wrapper of unlock function for drivers/base/power/clock_ops.c */
 > 159	void __clk_prepare_unlock(void)
   160	{
   161		clk_prepare_unlock();
   162	}
   163	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

  reply	other threads:[~2022-09-23  5:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 15:49 [RFC PATCH] PM: clk: Avoid lockdep warning between prepare lock and &psd->lock Douglas Anderson
2022-09-23  5:53 ` kernel test robot [this message]
2022-09-23 13:59 ` kernel test robot

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=202209231304.p14ZsMhw-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dianders@chromium.org \
    --cc=kbuild-all@lists.01.org \
    --cc=llvm@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.