From: kernel test robot <lkp@intel.com>
To: linux@treblig.org, rogerq@kernel.org, tony@atomide.com, krzk@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Dr. David Alan Gilbert" <linux@treblig.org>
Subject: Re: [PATCH] memory: omap-gpmc: deadcode a pair of functions
Date: Wed, 11 Dec 2024 19:26:47 +0800 [thread overview]
Message-ID: <202412111932.lp8jHbeT-lkp@intel.com> (raw)
In-Reply-To: <20241210220628.237604-1-linux@treblig.org>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on krzk-mem-ctrl/for-next]
[also build test WARNING on linus/master v6.13-rc2 next-20241211]
[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/linux-treblig-org/memory-omap-gpmc-deadcode-a-pair-of-functions/20241211-062027
base: https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git for-next
patch link: https://lore.kernel.org/r/20241210220628.237604-1-linux%40treblig.org
patch subject: [PATCH] memory: omap-gpmc: deadcode a pair of functions
config: i386-buildonly-randconfig-002-20241211 (https://download.01.org/0day-ci/archive/20241211/202412111932.lp8jHbeT-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241211/202412111932.lp8jHbeT-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/202412111932.lp8jHbeT-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/memory/omap-gpmc.c:361:21: warning: 'gpmc_clk_ticks_to_ns' defined but not used [-Wunused-function]
361 | static unsigned int gpmc_clk_ticks_to_ns(unsigned int ticks, int cs,
| ^~~~~~~~~~~~~~~~~~~~
vim +/gpmc_clk_ticks_to_ns +361 drivers/memory/omap-gpmc.c
a3551f5b0c3ca7a arch/arm/mach-omap2/gpmc.c Adrian Hunter 2010-12-09 360
3950fffdf0c088d drivers/memory/omap-gpmc.c Baoyou Xie 2016-08-28 @361 static unsigned int gpmc_clk_ticks_to_ns(unsigned int ticks, int cs,
7f2e8c58ae9e352 drivers/memory/omap-gpmc.c Robert ABEL 2015-02-27 362 enum gpmc_clk_domain cd)
7f2e8c58ae9e352 drivers/memory/omap-gpmc.c Robert ABEL 2015-02-27 363 {
7f2e8c58ae9e352 drivers/memory/omap-gpmc.c Robert ABEL 2015-02-27 364 return ticks * gpmc_get_clk_period(cs, cd) / 1000;
7f2e8c58ae9e352 drivers/memory/omap-gpmc.c Robert ABEL 2015-02-27 365 }
7f2e8c58ae9e352 drivers/memory/omap-gpmc.c Robert ABEL 2015-02-27 366
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-12-11 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 22:06 [PATCH] memory: omap-gpmc: deadcode a pair of functions linux
2024-12-11 11:26 ` kernel test robot [this message]
2024-12-11 12:05 ` Dr. David Alan Gilbert
2024-12-11 21:43 ` Dr. David Alan Gilbert
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=202412111932.lp8jHbeT-lkp@intel.com \
--to=lkp@intel.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@treblig.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rogerq@kernel.org \
--cc=tony@atomide.com \
/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