public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Greg KH <gregkh@linuxfoundation.org>, Jiri Slaby <jslaby@suse.cz>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@vger.kernel.org,
	lwn@lwn.net, Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: stable-3.0: s390 build breakage [was: Linux 3.0.24]
Date: Thu, 15 Mar 2012 17:51:38 +0100	[thread overview]
Message-ID: <4F621E1A.5000602@gmail.com> (raw)
In-Reply-To: <20120315164954.GR2264@1wt.eu>

On 03/15/2012 05:49 PM, Willy Tarreau wrote:
> On Thu, Mar 15, 2012 at 09:46:24AM -0700, Greg KH wrote:
>> On Thu, Mar 15, 2012 at 05:27:26PM +0100, Jiri Slaby wrote:
>>> On 03/15/2012 11:48 AM, Jiri Slaby wrote:
>>>> On 03/12/2012 09:34 PM, Greg KH wrote:
>>>>> I'm announcing the release of the 3.0.24 kernel.
>>>> ...
>>>>> Heiko Carstens (1): compat: fix compile breakage on s390
>>>>
>>>> It looks like we need the same fix as for 2.6.32.59:
>>>> arch/s390/kernel/setup.c: In function 'setup_addressing_mode':
>>>> arch/s390/kernel/setup.c:328: error: 'PSW32_ASC_PRIMARY' undeclared
>>>> (first use in this function)
>>>> arch/s390/kernel/setup.c:328: error: (Each undeclared identifier is
>>>> reported only once
>>>> arch/s390/kernel/setup.c:328: error: for each function it appears in.)
>>>
>>> And when that one is fixed, there is another error:
>>> drivers/s390/char/fs3270.c: In function 'fs3270_ioctl':
>>> drivers/s390/char/fs3270.c:335: error: implicit declaration of function
>>> 'compat_ptr'
>>> drivers/s390/char/fs3270.c:335: warning: assignment makes pointer from
>>> integer without a cast
>>
>> Ick, have a patch for this?
> 
> This one is declared in arch/s390/include/asm/compat.h:
> 
> static inline void __user *compat_ptr(compat_uptr_t uptr)
> {
>         return (void __user *)(unsigned long)(uptr & 0x7fffffffUL);
> }
> 
> In 2.6.32, fs3270.c include linux/compat.h. In 3.0 it includes asm/compat.h
> instead. I would have thought the later would have been enough.

But it was changed to linux/compat.h in 3.0.24 -- that's why it doesn't
build. So the same fix as for setup.c should help here.

thanks,
-- 
js

  reply	other threads:[~2012-03-15 16:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 20:34 Linux 3.0.24 Greg KH
2012-03-12 20:35 ` Greg KH
2012-03-15 10:48 ` stable-3.0: s390 build breakage [was: Linux 3.0.24] Jiri Slaby
2012-03-15 15:09   ` Greg KH
2012-03-15 16:42     ` Willy Tarreau
2012-03-15 16:49       ` Greg KH
2012-03-15 16:27   ` Jiri Slaby
2012-03-15 16:46     ` Greg KH
2012-03-15 16:47       ` Jiri Slaby
2012-03-15 16:49       ` Willy Tarreau
2012-03-15 16:51         ` Jiri Slaby [this message]
2012-03-16 12:52           ` Jiri Slaby
2012-03-16 17:22             ` Greg KH
2012-03-15 16:23 ` Linux 3.0.24 Chris Frey
2012-03-15 16:37   ` Greg KH
2012-03-15 16:51     ` Chris Frey
2012-03-15 16:57       ` Jonathan Nieder
2012-03-15 16:58       ` Greg KH
2012-03-15 17:28         ` Chris Frey

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=4F621E1A.5000602@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=w@1wt.eu \
    /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