From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: dhowells@redhat.com, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, uclinux-dev@uclinux.org,
Mike Frysinger <vapier@gentoo.org>
Subject: Re: [PATCH 1/4] FDPIC: Respect PT_GNU_STACK exec protection markings when creating NOMMU stack
Date: Thu, 31 Dec 2009 11:15:39 +0000 [thread overview]
Message-ID: <24434.1262258139@redhat.com> (raw)
In-Reply-To: <20091230135704.ccd0a129.akpm@linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> wrote:
> So these patches and the MN10300 ones didn't get merged. Presumably
> because they're a grabbag of fixes and non-fixes and kinda-fixes with
> no particular ordering or precedence and they arrived newly-minted
> several days after the release of -rc1.
>
> I could suggest that you go back and sort them into 2.6.33-appropriate
> fixes and 2.6.34-appropriate non-fixes.
>
> Or you could try to cook up a good-sounding reason why the whole lot
> needs to go into 2.6.33. If you believe that ;)
I did send them, plus others, during the merge window (albeit near the end).
I then sent this lot after filtering out the extensions that should probably
wait for the next merge window.
David
next prev parent reply other threads:[~2009-12-31 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 2/4] NOMMU: Avoiding duplicate icache flushes of shared maps David Howells
2009-12-22 17:17 ` [PATCH 3/4] NOMMU: Use copy_*_user_page() in access_process_vm() David Howells
2009-12-22 17:17 ` [PATCH 4/4] elf_fdpic_core_dump(): fix build break in 2.6.33-rc1 David Howells
2009-12-30 21:57 ` [PATCH 1/4] FDPIC: Respect PT_GNU_STACK exec protection markings when creating NOMMU stack Andrew Morton
2009-12-31 11:15 ` David Howells [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-06 17:23 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=24434.1262258139@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=uclinux-dev@uclinux.org \
--cc=vapier@gentoo.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.