From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-kernel@vger.kernel.org,
Frederic Weisbecker <frederic@kernel.org>,
Valentin Schneider <valentin.schneider@arm.com>
Subject: drivers/rtc/rtc-pcf8523.c:35:9: warning: 'REG_OFFSET' macro redefined
Date: Sun, 14 Feb 2021 15:11:37 +0800 [thread overview]
Message-ID: <202102141533.f61jk3s7-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2351 bytes --]
Hi Thomas,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ac30d8ce28d61c05ac3a8b1452e889371136f3af
commit: 7fd70c65faacd39628ba5f670be6490010c8132f ARM: irqstat: Get rid of duplicated declaration
date: 3 months ago
config: arm-randconfig-r003-20210214 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project c9439ca36342fb6013187d0a69aef92736951476)
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
# install arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# 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=clang 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:9: warning: 'REG_OFFSET' macro redefined [-Wmacro-redefined]
#define REG_OFFSET 0x0e
^
arch/arm/mach-ixp4xx/include/mach/platform.h:23:9: note: previous definition is here
#define REG_OFFSET 0
^
1 warning generated.
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: 29726 bytes --]
next reply other threads:[~2021-02-14 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 7:11 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-08 14:45 drivers/rtc/rtc-pcf8523.c:35:9: warning: 'REG_OFFSET' macro redefined kernel test robot
2021-04-25 12:31 kernel test robot
2021-01-06 6:53 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=202102141533.f61jk3s7-lkp@intel.com \
--to=lkp@intel.com \
--cc=clang-built-linux@googlegroups.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;
as well as URLs for NNTP newsgroup(s).