From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Michael Holzheu <holzheu@linux.vnet.ibm.com>, linux-next@vger.kernel.org
Subject: Re: [next] new fail in linux-next s390 smp
Date: Mon, 29 Jun 2015 11:09:47 +0200 [thread overview]
Message-ID: <20150629110947.62df85b2@mschwide> (raw)
In-Reply-To: <20150626174901.GB4633@windriver.com>
On Fri, 26 Jun 2015 13:49:01 -0400
Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> Seen in allnoconfig:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/12450623/
>
> arch/s390/kernel/setup.c: In function 'setup_arch':
> arch/s390/kernel/setup.c:875:2: error: implicit declaration of function
> 'smp_save_dump_cpus'
> make[2]: *** [arch/s390/kernel/setup.o] Error 1
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [arch/s390/kernel] Error 2
> make: *** [arch/s390] Error 2
> make: *** Waiting for unfinished jobs....
I have added a patch from Heiko to the s390 tree. Should be fixed
with tomorrows -next tree.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2015-06-29 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 17:49 [next] new fail in linux-next s390 smp Paul Gortmaker
2015-06-29 9:09 ` Martin Schwidefsky [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=20150629110947.62df85b2@mschwide \
--to=schwidefsky@de.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=linux-next@vger.kernel.org \
--cc=paul.gortmaker@windriver.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