From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Frederic Weisbecker <frederic@kernel.org>,
Valentin Schneider <valentin.schneider@arm.com>
Subject: drivers/rtc/rtc-pcf8523.c:35: warning: "REG_OFFSET" redefined
Date: Sun, 3 Jan 2021 07:11:12 +0800 [thread overview]
Message-ID: <202101030708.2I9miC6g-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2724 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: eda809aef53426d044b519405d25d9da55319b76
commit: 7fd70c65faacd39628ba5f670be6490010c8132f ARM: irqstat: Get rid of duplicated declaration
date: 6 weeks ago
config: arm-randconfig-p001-20210103 (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
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://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7fd70c65faacd39628ba5f670be6490010c8132f
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 7fd70c65faacd39628ba5f670be6490010c8132f
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/rtc/rtc-pcf8523.c:35: warning: "REG_OFFSET" redefined
35 | #define REG_OFFSET 0x0e
|
In file included from arch/arm/mach-ixp4xx/include/mach/hardware.h:30,
from arch/arm/mach-ixp4xx/include/mach/io.h:15,
from arch/arm/include/asm/io.h:198,
from include/linux/io.h:13,
from include/linux/irq.h:20,
from include/asm-generic/hardirq.h:13,
from arch/arm/include/asm/hardirq.h:10,
from include/linux/hardirq.h:10,
from include/linux/interrupt.h:11,
from include/linux/rtc.h:17,
from drivers/rtc/rtc-pcf8523.c:9:
arch/arm/mach-ixp4xx/include/mach/platform.h:23: note: this is the location of the previous definition
23 | #define REG_OFFSET 0
|
vim +/REG_OFFSET +35 drivers/rtc/rtc-pcf8523.c
f803f0d079ded4 Thierry Reding 2012-12-17 34
bc3bee02527252 Russell King 2017-09-29 @35 #define REG_OFFSET 0x0e
bc3bee02527252 Russell King 2017-09-29 36 #define REG_OFFSET_MODE BIT(7)
bc3bee02527252 Russell King 2017-09-29 37
:::::: The code at line 35 was first introduced by commit
:::::: bc3bee0252725240ffa62180d387cc245179c549 rtc: pcf8523: add support for trimming the RTC oscillator
:::::: TO: Russell King <rmk+kernel@armlinux.org.uk>
:::::: CC: Alexandre Belloni <alexandre.belloni@free-electrons.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 36350 bytes --]
next reply other threads:[~2021-01-02 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-02 23:11 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-09 6:23 drivers/rtc/rtc-pcf8523.c:35: warning: "REG_OFFSET" redefined kernel test robot
2021-06-05 20:49 kernel test robot
2021-06-19 2:30 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=202101030708.2I9miC6g-lkp@intel.com \
--to=lkp@intel.com \
--cc=frederic@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.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