From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 1860/2084] include/linux/mm.h:1602:2: note: in expansion of macro 'spin_lock_init'
Date: Fri, 29 Jan 2016 09:23:52 +1100 [thread overview]
Message-ID: <20160129092352.7b60a7e0@canb.auug.org.au> (raw)
In-Reply-To: <56AA5126.2030101@suse.cz>
Hi Vlastimil,
On Thu, 28 Jan 2016 18:34:30 +0100 Vlastimil Babka <vbabka@suse.cz> wrote:
>
> On 01/28/2016 08:23 AM, kbuild test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 888c8375131656144c1605071eab2eb6ac49abc3
> > commit: cec08ed70d3d5209368a435fed278ae667117a0c [1860/2084] mm, printk: introduce new format string for flags
> > config: s390-allyesconfig (attached as .config)
> > reproduce:
> > wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > git checkout cec08ed70d3d5209368a435fed278ae667117a0c
> > # save the attached .config to linux build tree
> > make.cross ARCH=s390
> >
> > All error/warnings (new ones prefixed by >>):
> >
> > In file included from include/linux/spinlock.h:81:0,
> > from include/linux/rcupdate.h:38,
> > from include/linux/tracepoint.h:19,
> > from include/linux/mmdebug.h:7,
> > from arch/s390/include/asm/cmpxchg.h:10,
> > from arch/s390/include/asm/atomic.h:19,
> > from include/linux/atomic.h:4,
> > from include/linux/debug_locks.h:5,
> > from include/linux/lockdep.h:23,
> > from include/linux/hardirq.h:5,
> > from include/linux/kvm_host.h:10,
> > from arch/s390/kernel/asm-offsets.c:10:
> >>> include/linux/spinlock_types.h:30:21: error: field 'dep_map' has incomplete type
> > struct lockdep_map dep_map;
> > ^
>
> Damn, a rebasing mistake in my series, sorry about that.
> This should help. Can it be applied to -next? I think Andrew said he
> would be travelling...
Added to linux-next by hand today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-01-28 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 7:23 [linux-next:master 1860/2084] include/linux/mm.h:1602:2: note: in expansion of macro 'spin_lock_init' kbuild test robot
2016-01-28 17:34 ` Vlastimil Babka
2016-01-28 22:23 ` Stephen Rothwell [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=20160129092352.7b60a7e0@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
/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).