From: Greg KH <greg@kroah.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: Pat Gefre <pfg@sgi.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Altix I/O code reorganization
Date: Thu, 05 Aug 2004 21:36:57 +0000 [thread overview]
Message-ID: <20040805213657.GA16360@kroah.com> (raw)
In-Reply-To: <200408051432.36240.jbarnes@engr.sgi.com>
On Thu, Aug 05, 2004 at 02:32:36PM -0700, Jesse Barnes wrote:
>
> A few of the patches at that URL are very large (one is over 400k). That
> said, some of the others could probably be posted.
Exactly. They _should_ be posted.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: Pat Gefre <pfg@sgi.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Altix I/O code reorganization
Date: Thu, 5 Aug 2004 14:36:57 -0700 [thread overview]
Message-ID: <20040805213657.GA16360@kroah.com> (raw)
In-Reply-To: <200408051432.36240.jbarnes@engr.sgi.com>
On Thu, Aug 05, 2004 at 02:32:36PM -0700, Jesse Barnes wrote:
>
> A few of the patches at that URL are very large (one is over 400k). That
> said, some of the others could probably be posted.
Exactly. They _should_ be posted.
greg k-h
next prev parent reply other threads:[~2004-08-05 21:36 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 20:14 Altix I/O code reorganization Pat Gefre
2004-08-04 20:14 ` Pat Gefre
2004-08-05 0:31 ` Grant Grundler
2004-08-05 0:31 ` Grant Grundler
2004-08-05 18:16 ` Greg KH
2004-08-05 18:16 ` Greg KH
2004-08-05 20:51 ` Pat Gefre
2004-08-05 20:51 ` Pat Gefre
2004-08-05 21:08 ` Greg KH
2004-08-05 21:08 ` Greg KH
2004-08-05 21:32 ` Jesse Barnes
2004-08-05 21:32 ` Jesse Barnes
2004-08-05 21:36 ` Greg KH [this message]
2004-08-05 21:36 ` Greg KH
2004-08-06 13:18 ` Christoph Hellwig
2004-08-06 13:18 ` Christoph Hellwig
2004-08-06 16:19 ` Jesse Barnes
2004-08-06 16:19 ` Jesse Barnes
2004-08-07 10:58 ` Christoph Hellwig
2004-08-07 10:58 ` Christoph Hellwig
2004-08-11 23:24 ` Patrick Gefre
2004-08-11 23:24 ` Patrick Gefre
2004-08-12 9:15 ` Christoph Hellwig
2004-08-12 9:15 ` Christoph Hellwig
2004-08-12 14:47 ` Jesse Barnes
2004-08-12 14:47 ` Jesse Barnes
2004-08-12 15:21 ` Christoph Hellwig
2004-08-12 15:21 ` Christoph Hellwig
2004-08-27 15:10 ` Latest Altix I/O code reorganization code Patrick Gefre
2004-08-27 15:10 ` Patrick Gefre
2004-08-27 15:14 ` Patrick Gefre
2004-08-27 15:14 ` Patrick Gefre
2004-08-27 15:21 ` Christoph Hellwig
2004-08-27 15:21 ` Christoph Hellwig
2004-08-27 15:35 ` Patrick Gefre
2004-08-27 15:35 ` Patrick Gefre
2004-08-27 15:44 ` Christoph Hellwig
2004-08-27 15:44 ` Christoph Hellwig
2004-09-03 23:12 ` Latest Altix I/O code rewrite Patrick Gefre
2004-08-27 15:23 ` Latest Altix I/O code reorganization code Pat Gefre
2004-08-27 15:23 ` Pat Gefre
2004-08-27 15:36 ` Christoph Hellwig
2004-08-27 15:36 ` Christoph Hellwig
2004-08-27 15:45 ` Christoph Hellwig
2004-08-27 15:45 ` Christoph Hellwig
2004-08-27 16:32 ` Patrick Gefre
2004-08-27 16:32 ` Patrick Gefre
2004-08-27 15:54 ` Christoph Hellwig
2004-08-27 15:54 ` Christoph Hellwig
2004-08-27 16:06 ` Patrick Gefre
2004-08-27 16:06 ` Patrick Gefre
2004-08-27 16:21 ` Christoph Hellwig
2004-08-27 16:21 ` Christoph Hellwig
2004-09-03 23:40 ` Christoph Hellwig
2004-09-03 23:40 ` Christoph Hellwig
2004-09-07 22:10 ` Patrick Gefre
2004-09-07 22:10 ` Patrick Gefre
2004-09-07 22:16 ` Christoph Hellwig
2004-09-07 22:16 ` Christoph Hellwig
2004-08-27 17:15 ` Christoph Hellwig
2004-08-27 17:15 ` Christoph Hellwig
2004-08-29 6:39 ` Keith Owens
2004-08-29 6:39 ` Keith Owens
2004-08-29 7:16 ` Sam Ravnborg
2004-08-29 7:16 ` Sam Ravnborg
2004-08-29 7:22 ` Keith Owens
2004-08-29 7:22 ` Keith Owens
2004-08-06 13:51 ` Altix I/O code reorganization Keith Owens
2004-08-06 13:51 ` Keith Owens
2004-08-06 13:55 ` Christoph Hellwig
2004-08-06 13:55 ` Christoph Hellwig
2004-08-06 15:47 ` Russ Anderson
2004-08-06 15:47 ` Russ Anderson
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=20040805213657.GA16360@kroah.com \
--to=greg@kroah.com \
--cc=jbarnes@engr.sgi.com \
--cc=linux-ia64@vger.kernel.org \
--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 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.