From: Paul Mundt <lethal@linux-sh.org>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@osdl.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, uclinux-dev@uclinux.org,
Daisuke HATAYAMA <d.hatayama@jp.fujitsu.com>
Subject: Re: [PATCH 4/4] elf_fdpic_core_dump(): fix build break in 2.6.33-rc1
Date: Thu, 7 Jan 2010 02:26:39 +0900 [thread overview]
Message-ID: <20100106172638.GA20417@linux-sh.org> (raw)
In-Reply-To: <20100106172333.25862.40963.stgit@warthog.procyon.org.uk>
On Wed, Jan 06, 2010 at 05:23:33PM +0000, David Howells wrote:
> From: Daisuke HATAYAMA <d.hatayama@jp.fujitsu.com>
>
> Commit f6151dfea21496d43dbaba32cfcd9c9f404769bc causes ELF-FDPIC to break
> during building, so this patch fixes it together with a correction for the
> printk format.
>
> Signed-off-by: Daisuke HATAYAMA <d.hatayama@jp.fujitsu.com>
> Reviewed-by: Masami Hiramatsu <mhiramat@redhat.com>
> Acked-by: Paul Mundt <lethal@linux-sh.org>
> Signed-off-by: David Howells <dhowells@redhat.com>
I already pushed this through my tree, so you can just ignore this one.
next prev parent reply other threads:[~2010-01-06 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 17:23 [PATCH 1/4] FDPIC: Respect PT_GNU_STACK exec protection markings when creating NOMMU stack David Howells
2010-01-06 17:23 ` [PATCH 2/4] NOMMU: Avoiding duplicate icache flushes of shared maps David Howells
2010-01-06 17:23 ` [PATCH 3/4] NOMMU: Use copy_*_user_page() in access_process_vm() David Howells
2010-01-06 17:23 ` [PATCH 4/4] elf_fdpic_core_dump(): fix build break in 2.6.33-rc1 David Howells
2010-01-06 17:26 ` Paul Mundt [this message]
2010-01-06 18:45 ` Linus Torvalds
2010-01-07 0:12 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2009-12-22 17:17 [PATCH 1/4] FDPIC: Respect PT_GNU_STACK exec protection markings when creating NOMMU stack David Howells
2009-12-22 17:17 ` [PATCH 4/4] elf_fdpic_core_dump(): fix build break in 2.6.33-rc1 David Howells
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=20100106172638.GA20417@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=d.hatayama@jp.fujitsu.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=uclinux-dev@uclinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.