From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: "Sachin P. Sant" <sachinp@in.ibm.com>
Cc: linux-s390@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
heiko.carstens@de.ibm.com, Mel Gorman <mel@csn.ul.ie>
Subject: Re: [Patch] [s390] Fix init irq proc build break.
Date: Tue, 10 Feb 2009 12:40:58 +0100 [thread overview]
Message-ID: <1234266058.23901.0.camel@localhost> (raw)
In-Reply-To: <499161C3.2070407@in.ibm.com>
On Tue, 2009-02-10 at 16:45 +0530, Sachin P. Sant wrote:
> * Embed init_irq_proc(s390) within CONFIG_PROC_FS to fix a build
> break.
>
> Signed-off-by : Sachin Sant <sachinp@in.ibm.com>
I'll queue the patch to git390.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2009-02-10 11:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 8:41 linux-next: Tree for February 10 Stephen Rothwell
2009-02-10 9:23 ` next Feb 10: mm/slqb build break Sachin P. Sant
2009-02-10 9:54 ` Sachin P. Sant
2009-02-10 11:53 ` Pekka Enberg
2009-02-12 1:45 ` Nick Piggin
2009-02-12 1:47 ` David Miller
2009-02-12 11:28 ` Sachin P. Sant
2009-02-12 11:28 ` Sachin P. Sant
2009-02-12 11:28 ` Sachin P. Sant
2009-02-10 10:30 ` Next Feb 10 : build/break arch/s390kernel.irq.o Sachin P. Sant
2009-02-10 11:15 ` [Patch] [s390] Fix init irq proc build break Sachin P. Sant
2009-02-10 11:40 ` Martin Schwidefsky [this message]
2009-02-10 10:45 ` Next Feb 10 build break on s390 : mm/shmem.c Sachin P. Sant
2009-02-10 13:40 ` Mimi Zohar
2009-02-10 19:55 ` linux-next: Tree for February 10 (security/audit/ima) Randy Dunlap
2009-02-10 22:40 ` Stephen Rothwell
2009-02-11 0:30 ` Mimi Zohar
2009-02-12 17:54 ` [PATCH -next] security/audit/ima: fix build error Randy Dunlap
2009-02-12 18:24 ` Mimi Zohar
2009-02-12 18:30 ` Randy Dunlap
2009-02-12 22:31 ` James Morris
2009-02-11 1:29 ` linux-next: Tree for February 10 (security/audit/ima) Al Viro
2009-02-11 2:27 ` Stephen Rothwell
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=1234266058.23901.0.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=sachinp@in.ibm.com \
--cc=sfr@canb.auug.org.au \
/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).