linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: davidm@hpl.hp.com
Cc: Patrick Gefre <pfg@sgi.com>,
	linux-kernel@vger.kernel.org, davidm@napali.hpl.hp.com
Subject: Re: [PATCH] Altix I/O code cleanup
Date: Fri, 10 Oct 2003 16:51:02 -0700	[thread overview]
Message-ID: <20031010235102.GA6198@sgi.com> (raw)
In-Reply-To: <16263.14277.278807.472247@napali.hpl.hp.com>

On Fri, Oct 10, 2003 at 03:50:45PM -0700, David Mosberger wrote:
> >>>>> On Fri, 10 Oct 2003 14:51:53 -0700, jbarnes@sgi.com (Jesse Barnes) said:
> 
>   Jesse> David, please apply this set of patches from Pat.
> 
> Unfortunately, the 2.6 tree is closed for cleanups.  I would _like_ to
> see the patch applied, though.  Perhaps you could talk to Andrew and
> see if you can get an exception?

Ok, I'll talk to Pat.  I know that at least part of this is bugfixes.

>   Jesse> Btw, any estimate as to when your BK tree will be updated?
> 
> Just did a short while ago.  It's not the final stuff, but getting closer.
> (I just merged your discontig fixes, btw.)

Kick ass!  I've been waiting for this day! :)

Thanks,
Jesse

  reply	other threads:[~2003-10-10 23:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10 21:49 [PATCH] Altix I/O code cleanup Patrick Gefre
2003-10-10 21:51 ` Jesse Barnes
2003-10-10 22:50   ` David Mosberger
2003-10-10 23:51     ` Jesse Barnes [this message]
2003-10-13  8:58     ` Christoph Hellwig
2003-10-13 10:55       ` Andrew Morton
2003-10-13 14:06         ` Christoph Hellwig
2003-10-13  8:56 ` Christoph Hellwig
2003-10-15  8:07   ` Jes Sorensen
2003-10-15 12:55     ` Christoph Hellwig
2003-10-16 13:08       ` Jes Sorensen
2003-10-16 16:40         ` Colin Ngam
2003-10-17  8:11           ` Christoph Hellwig
2003-10-17 13:36             ` Jes Sorensen

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=20031010235102.GA6198@sgi.com \
    --to=jbarnes@sgi.com \
    --cc=davidm@hpl.hp.com \
    --cc=davidm@napali.hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pfg@sgi.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;
as well as URLs for NNTP newsgroup(s).