linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dejin Zheng <zhengdejin5@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Mark Brown <broonie@kernel.org>
Subject: Re: drivers/reset/reset-intel-gw.c:18: warning: "REG_OFFSET" redefined
Date: Thu, 4 Jun 2020 23:35:18 +0800	[thread overview]
Message-ID: <20200604153518.GA23034@nuc8i5> (raw)
In-Reply-To: <202006041903.Mwlo5QJ5%lkp@intel.com>

On Thu, Jun 04, 2020 at 07:37:06PM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   6929f71e46bdddbf1c4d67c2728648176c67c555
> commit: e44ab4e14d6f4c448ae555132090c1a116b19e5c regmap: Simplify implementation of the regmap_read_poll_timeout() macro
> date:   6 weeks ago
> config: arm-randconfig-r035-20200604 (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
>         git checkout e44ab4e14d6f4c448ae555132090c1a116b19e5c
>         # 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>
>
Hi

Thanks very much for report this issue to me, and very very sorry for
that. I submit a commit to fix it. it is in here:
https://lkml.org/lkml/2020/6/4/606

BR,
Dejin

> All warnings (new ones prefixed by >>, old ones prefixed by <<):
> 
> >> drivers/reset/reset-intel-gw.c:18: warning: "REG_OFFSET" redefined
> 18 | #define REG_OFFSET GENMASK(31, 16)
> |
> 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/iopoll.h:14,
> from include/linux/regmap.h:20,
> from drivers/reset/reset-intel-gw.c:12:
> arch/arm/mach-ixp4xx/include/mach/platform.h:25: note: this is the location of the previous definition
> 25 | #define REG_OFFSET 3
> |
> 
> vim +/REG_OFFSET +18 drivers/reset/reset-intel-gw.c
> 
> c9aef213e38cde Dilip Kota 2020-01-03  17  
> c9aef213e38cde Dilip Kota 2020-01-03 @18  #define REG_OFFSET	GENMASK(31, 16)
> c9aef213e38cde Dilip Kota 2020-01-03  19  #define BIT_OFFSET	GENMASK(15, 8)
> c9aef213e38cde Dilip Kota 2020-01-03  20  #define STAT_BIT_OFFSET	GENMASK(7, 0)
> c9aef213e38cde Dilip Kota 2020-01-03  21  
> 
> :::::: The code at line 18 was first introduced by commit
> :::::: c9aef213e38cde27d4689a5cbe25a7c1b1db9fad reset: intel: Add system reset controller driver
> 
> :::::: TO: Dilip Kota <eswara.kota@linux.intel.com>
> :::::: CC: Philipp Zabel <p.zabel@pengutronix.de>
> 
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org



      reply	other threads:[~2020-06-04 15:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 11:37 drivers/reset/reset-intel-gw.c:18: warning: "REG_OFFSET" redefined kernel test robot
2020-06-04 15:35 ` Dejin Zheng [this message]

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=20200604153518.GA23034@nuc8i5 \
    --to=zhengdejin5@gmail.com \
    --cc=broonie@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.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).