mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Dave Jones <davej@codemonkey.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: struct inode size reduction.
Date: 10 Mar 2003 14:04:57 +0900	[thread overview]
Message-ID: <buoy93ng6bq.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <20030309235934.GA3962@werewolf.able.es>

"J.A. Magallon" <jamagallon@able.es> writes:
> That was my point, I do not know if some arch still requires 2.95 in 2.6.
> For 2.4, it states 2.95.3 as minimun.

Even if no arch `requires' gcc 2.95 (I don't really know, though until
recently my arch didn't even _have_ a [working] gcc 3.x port!), there
are certainly a buttload of people _using_ it to build the kernel, so
requiring gcc 3.2, would be kind of obnoxious.

-Miles
-- 
Come now, if we were really planning to harm you, would we be waiting here, 
 beside the path, in the very darkest part of the forest?

      reply	other threads:[~2003-03-10  4:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09 13:54 Fwd: " Dave Jones
2003-03-09 17:13 ` Andries Brouwer
2003-03-09 20:33   ` Dave Jones
2003-03-09 19:55     ` Christoph Hellwig
2003-03-09 20:31       ` Andries Brouwer
2003-03-09 22:18         ` Roman Zippel
2003-03-09 23:08           ` Andries Brouwer
2003-03-10  2:23             ` Alexander Viro
2003-03-10 10:58             ` Roman Zippel
2003-03-10 12:05               ` Andries Brouwer
2003-03-10 16:25                 ` Roman Zippel
2003-03-10 17:32                   ` Andries Brouwer
2003-03-10 18:39                     ` Roman Zippel
2003-03-09 22:45 ` J.A. Magallon
2003-03-10  0:11   ` Dave Jones
2003-03-09 23:59     ` J.A. Magallon
2003-03-10  5:04       ` Miles Bader [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=buoy93ng6bq.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=davej@codemonkey.org.uk \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@gnu.org \
    /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

all inboxes | Powered by JetHome®