From: Greg KH <gregkh@linuxfoundation.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net
Subject: Re: [stable 3.0] s390 build breakage [was: Linux 3.0.75]
Date: Thu, 2 May 2013 07:08:55 -0700 [thread overview]
Message-ID: <20130502140855.GA24348@kroah.com> (raw)
In-Reply-To: <51826176.2070104@suse.cz>
On Thu, May 02, 2013 at 02:52:06PM +0200, Jiri Slaby wrote:
> On 04/26/2013 06:30 AM, Greg KH wrote:
> > Linus Torvalds (5): vm: add vm_iomap_memory() helper function
>
> Hi, this one breaks s390 on 3.0:
> mm/memory.c: In function 'vm_iomap_memory':
> mm/memory.c:2363: error: implicit declaration of function
> 'io_remap_pfn_range'
>
> It looks like 4f2e29031e6c67802e7370292dd050fd62f337ee is needed:
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Wed Apr 17 08:46:19 2013 -0700
>
> s390: move dummy io_remap_pfn_range() to asm/pgtable.h
>
>
> But it depends on the s390 PCI support...
>
> Whatever, it should be OK to take only the second hunk from that
> patch, it seems.
Ah, sorry about that, for some reason I didn't think this patch was
needed on s390. I'll queue this up for the next stable release.
thanks,
greg k-h
next prev parent reply other threads:[~2013-05-02 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 4:30 Linux 3.0.75 Greg KH
2013-04-26 4:30 ` Greg KH
2013-05-02 12:52 ` [stable 3.0] s390 build breakage [was: Linux 3.0.75] Jiri Slaby
2013-05-02 14:08 ` Greg KH [this message]
2013-05-10 4:08 ` Ben Hutchings
2013-05-02 13:02 ` [stable 3.0] ppc " Jiri Slaby
2013-05-02 14:10 ` Greg KH
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=20130502140855.GA24348@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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