All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH mm] Remove deprecation of a.out ELF interpreters
Date: Wed, 30 Jan 2008 22:11:38 -0800	[thread overview]
Message-ID: <20080130221138.97cc32f1.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080131030919.GA27115@one.firstfloor.org>

On Thu, 31 Jan 2008 04:09:19 +0100 Andi Kleen <andi@firstfloor.org> wrote:

> On Wed, Jan 30, 2008 at 03:29:15PM -0800, Andrew Morton wrote:
> > On Wed, 30 Jan 2008 09:40:41 +0100
> > Andi Kleen <andi@firstfloor.org> wrote:
> > 
> > > 
> > > Andrew has already queued the patch to remove the support for a.out
> > > ELF interpreters. So remove the deprecation with it too.
> > > 
> > 
> > I'm trying to find which patch I might have queued which did this and came
> > up blank. 
> 
> Sorry I somehow thought you had it queued.
> 
> My patch makes parts of David's patch obsolete because he makes 
> the code ifdef, but I remove the code completely. David also
> does some other cleanups which still make sense. 
> 
> So I think the correct way is to apply my patch first and then David's
> and just ignore all the rejects and refresh.  The result should be correct.
> 
> Basically after that only the core dump changes in David's patch should
> be left over.
> 
> Can you do that or should I resubmit both patches in a merged form?
> (I can do that too) 
> 

Your patch on top of rc8-mm1 would be simplest for me.

I'm at a bit of a loss because I don't appear to have a copy of the patch
which we're discussing handy.


  reply	other threads:[~2008-01-31  6:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30  8:40 [PATCH mm] Remove deprecation of a.out ELF interpreters Andi Kleen
2008-01-30 23:29 ` Andrew Morton
2008-01-31  3:09   ` Andi Kleen
2008-01-31  6:11     ` Andrew Morton [this message]
2008-01-31  7:35       ` Andi Kleen

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=20080130221138.97cc32f1.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.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.