public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>
Subject: Re: Build failures in v3.2-stable-queue
Date: Wed, 22 Jul 2015 00:11:32 +0100	[thread overview]
Message-ID: <1437520292.29812.26.camel@decadent.org.uk> (raw)
In-Reply-To: <55AEC9A4.5060103@roeck-us.net>

[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]

On Tue, 2015-07-21 at 15:37 -0700, Guenter Roeck wrote:
> Building s390:defconfig ... failed
> Building s390:allmodconfig ... failed
> --------------
> Error log:
> fs/read_write.c: In function 'rw_copy_check_uvector':
> fs/read_write.c:684:16: warning: unused variable 'buf' [-Wunused-variable]
> arch/s390/kernel/suspend.c: In function 'pfn_is_nosave':
> arch/s390/kernel/suspend.c:140:30: error: '_eshared' undeclared (first use in this function)
> arch/s390/kernel/suspend.c:140:30: note: each undeclared identifier is reported only once for each function it appears in
> arch/s390/kernel/suspend.c:141:28: error: '_stext' undeclared (first use in this function)
> arch/s390/kernel/suspend.c:150:10: error: 'ipl_info' undeclared (first use in this function)
> arch/s390/kernel/suspend.c:150:27: error: 'IPL_TYPE_NSS' undeclared (first use in this function)

Thanks, I spotted that and worked out I need to add some #includes but
haven't pushed the change yet.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

  reply	other threads:[~2015-07-21 23:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 22:37 Build failures in v3.2-stable-queue Guenter Roeck
2015-07-21 23:11 ` Ben Hutchings [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-05 14:35 Guenter Roeck
2017-09-08 16:48 Guenter Roeck
2017-09-08 17:22 ` Ben Hutchings

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=1437520292.29812.26.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=linux@roeck-us.net \
    --cc=stable@vger.kernel.org \
    /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