From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754478AbXGGEwJ (ORCPT ); Sat, 7 Jul 2007 00:52:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750962AbXGGEv7 (ORCPT ); Sat, 7 Jul 2007 00:51:59 -0400 Received: from gw.goop.org ([64.81.55.164]:42179 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750751AbXGGEv6 (ORCPT ); Sat, 7 Jul 2007 00:51:58 -0400 Message-ID: <468F1BEC.5080508@goop.org> Date: Fri, 06 Jul 2007 21:51:56 -0700 From: Jeremy Fitzhardinge User-Agent: Thunderbird 2.0.0.4 (X11/20070615) MIME-Version: 1.0 To: William Lee Irwin III CC: Andrew Morton , Linux Kernel Mailing List , Andi Kleen Subject: Re: state of stack patches References: <468D55D1.7070308@goop.org> <20070706213121.GI11781@holomorphy.com> In-Reply-To: <20070706213121.GI11781@holomorphy.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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