From: Jeremy Fitzhardinge <jeremy@goop.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@suse.de>
Subject: Re: state of stack patches
Date: Fri, 06 Jul 2007 21:51:56 -0700 [thread overview]
Message-ID: <468F1BEC.5080508@goop.org> (raw)
In-Reply-To: <20070706213121.GI11781@holomorphy.com>
William Lee Irwin III wrote:
> On Thu, Jul 05, 2007 at 01:34:25PM -0700, Jeremy Fitzhardinge wrote:
>
>> What's the state of your stack patches? I'm still using the ones you
>> posted some time ago, and they seem like useful things to have in the
>> kernel. Is there anything preventing you from pushing them upstream?
>>
>
> Just one thing: 2.6.22. I can, of course, do updating for -mm, -ak, et al.
>
Yes, I was thinking they're the just the thing to cook in -mm for a
while, until the appropriate upstream time comes.
J
prev parent reply other threads:[~2007-07-07 4:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 20:34 state of stack patches Jeremy Fitzhardinge
2007-07-06 21:31 ` William Lee Irwin III
2007-07-07 4:51 ` Jeremy Fitzhardinge [this message]
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=468F1BEC.5080508@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox