All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: Scott Wood <scottwood@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH v2] Allow exec on 32-bit from readable, non-exec pages, with a warning.
Date: Tue, 17 Jul 2007 17:44:14 -0500	[thread overview]
Message-ID: <E1IAvmA-00062M-F4@jdl.com> (raw)
In-Reply-To: Your message of "Tue, 17 Jul 2007 17:14:56 CDT." <469D3F60.8000401@freescale.com>

<Top Posting Carnac>

A:  They haven't been posted yet.

Q:  How do we know Segher has new patches?

</Top Posting Carnac>

So, like, the other day Scott Wood mumbled:
> Jon Loeliger wrote:
> > But luckily, this gave me the opportunity to then realize that
> > we should give a great big...
> > 
> > Amen-brother-by: Jon Loeliger <jdl@freescale.com>
> > 
> > to this patch from Scott.
> > 
> > So, an official plea to Paul to apply this to his tree.
> 
> Segher has a newer patch that supersedes this one.  I don't know if he's 
> posted it to the list yet, though.
> 
> -Scott

  reply	other threads:[~2007-07-17 22:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 21:48 [PATCH v2] Allow exec on 32-bit from readable, non-exec pages, with a warning Scott Wood
2007-07-10  3:01 ` Paul Mackerras
2007-07-11  0:16   ` Segher Boessenkool
2007-07-11 15:32     ` Scott Wood
2007-07-12  7:40       ` Kumar Gala
2007-07-16 12:55         ` Segher Boessenkool
2007-07-17 20:46 ` Jon Loeliger
2007-07-17 22:14   ` Scott Wood
2007-07-17 22:44     ` Jon Loeliger [this message]
2007-07-17 22:53       ` Scott Wood
2007-07-18  3:30         ` Segher Boessenkool
2007-07-18  6:02           ` Kumar Gala
2007-07-18 12:07             ` Segher Boessenkool
2007-07-18 14:13               ` Kumar Gala
2007-07-18 18:18       ` Linas Vepstas

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=E1IAvmA-00062M-F4@jdl.com \
    --to=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=scottwood@freescale.com \
    /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.