linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	kbuild-all@01.org, linux-mm@kvack.org
Subject: Re: [memcg:since-4.15 382/386] arch/m68k/mm/init.c:125:0: warning: "UL" redefined
Date: Thu, 15 Mar 2018 09:39:20 +0100	[thread overview]
Message-ID: <20180315083920.GY23100@dhcp22.suse.cz> (raw)
In-Reply-To: <20180314134445.61e26e6038e5c565f1438a9b@linux-foundation.org>

On Wed 14-03-18 13:44:45, Andrew Morton wrote:
> On Wed, 14 Mar 2018 23:20:21 +0800 kbuild test robot <fengguang.wu@intel.com> wrote:
> 
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git since-4.15
> > head:   5c3f7a041df707417532dd64b1d71fc29b24c0fe
> > commit: 145e9c14cca497b2d02f9edcf9307aad5946172f [382/386] linux/const.h: move UL() macro to include/linux/const.h
> > config: m68k-sun3_defconfig (attached as .config)
> > compiler: m68k-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
> > reproduce:
> >         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> >         chmod +x ~/bin/make.cross
> >         git checkout 145e9c14cca497b2d02f9edcf9307aad5946172f
> >         # save the attached .config to linux build tree
> >         make.cross ARCH=m68k 
> > 
> > All warnings (new ones prefixed by >>):
> > 
> >    arch/m68k/mm/init.c: In function 'print_memmap':
> > >> arch/m68k/mm/init.c:125:0: warning: "UL" redefined
> >     #define UL(x) ((unsigned long) (x))
> >     
> >    In file included from include/linux/list.h:8:0,
> >                     from include/linux/module.h:9,
> >                     from arch/m68k/mm/init.c:11:
> >    include/linux/const.h:6:0: note: this is the location of the previous definition
> >     #define UL(x)  (_UL(x))
> 
> That's OK - an unrelated patch in linux-next.patch removes that
> #define.
> 

I have cherry-picked 445420c31cbba4a218b432bece0b500b6c4f9d63 into my
mmotm git tree. Thanks for pointing that out.

-- 
Michal Hocko
SUSE Labs

      reply	other threads:[~2018-03-15  8:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 15:20 kbuild test robot
2018-03-14 20:44 ` Andrew Morton
2018-03-15  8:39   ` Michal Hocko [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=20180315083920.GY23100@dhcp22.suse.cz \
    --to=mhocko@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    --cc=yamada.masahiro@socionext.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