linux-s390.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Guenter Roeck <linux@roeck-us.net>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Cc: Michal Hocko <mhocko@suse.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-s390 <linux-s390@vger.kernel.org>,
	Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: Build failures (s390) in -next due to 'mm, printk: introduce new format string for flags'
Date: Fri, 29 Jan 2016 16:40:46 +0100	[thread overview]
Message-ID: <56AB87FE.8010800@suse.cz> (raw)
In-Reply-To: <56AB86BA.8020507@roeck-us.net>

On 01/29/2016 04:35 PM, Guenter Roeck wrote:
> Hi,
> 
> s390 builds in -next fail with lots of errors such as:
> 
> include/linux/jump_label.h: In function 'static_key_count':
> include/linux/jump_label.h:122:2: error: implicit declaration of function 'atomic_read' [-Werror=implicit-function-declaration]
>    return atomic_read(&key->enabled);
> ...
> ./arch/s390/include/asm/atomic.h: At top level:
> ./arch/s390/include/asm/atomic.h:74:19: error: static declaration of 'atomic_read' follows non-static declaration
>   static inline int atomic_read(const atomic_t *v)
> 
> As far as I can see this is due to recursive inclusion of linux/atomic.h
> (which in turn is triggered by recursive inclusion of linux/mmdebug.h).
> 
> I was able to "fix" the problem by removing the inclusion of mmdebug.h from
> arch/s390/include/asm/cmpxchg.h. That is not a proper fix, though, since the file
> uses VM_BUG_ON(), which is defined in mmdebug.h.
> 
> The problem was introduced with 'mm, printk: introduce new format string for flags'.

Yeah sorry about that, I sent a fixed fix:

http://marc.info/?l=linux-mm&m=145406672221395&w=2

      reply	other threads:[~2016-01-29 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 15:35 Build failures (s390) in -next due to 'mm, printk: introduce new format string for flags' Guenter Roeck
2016-01-29 15:40 ` Vlastimil Babka [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=56AB87FE.8010800@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mhocko@suse.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).