From: "List User" <lists@chaven.com>
To: "Timur Tabi" <ttabi@interactivesi.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Request: increase in PCI bus limit
Date: Tue, 30 Jan 2001 19:44:23 -0600 [thread overview]
Message-ID: <033c01c08b27$5944a430$160912ac@stcostlnds2zxj> (raw)
In-Reply-To: <FLRPM.A.TsC.j41d6@dinero.interactivesi.com>
He's probably sending it to the list the same reason why most in tech
circles do.
To cut down on the amount of work required. Personally I would love to have
all my custom changes put into a 'standard' distribution that way I wouldn't
need
to keep as many custom notes for x,y,z platforms or what-else. Also for the
fact that it gives something back (generally if I run into a situation there
is a good
chance that someone else will run into it as well, so if I can make _his_
life
easier if he doesn't have the same knowledge it's worth it).
Steve
----- Original Message -----
From: "Timur Tabi" <ttabi@interactivesi.com>
To: <linux-kernel@vger.kernel.org>
Sent: Tuesday, January 30, 2001 18:36
Subject: Re: Request: increase in PCI bus limit
> ** Reply to message from Christopher Neufeld <neufeld@linuxcare.com> on
Tue, 30
> Jan 2001 16:08:32 -0800
>
>
> > Would it be possible to bump it up to 128, or even
> > 256, in later 2.4.* kernel releases? That would allow this customer to
> > work with an unpatched kernel, at the cost of an additional 3.5 kB of
> > variables in the kernel.
>
> I don't think that's going to happen. If we did this for your obscure
system,
> then we'd have to do it for every obscure system, and before you know it,
the
> kernel is 200KB larger.
>
> Besides, why is your client afraid of patched kernels? It sounds like a
very
> odd request from someone with a linuxcare.com email address. I would
think that
> you'd WANT to provide patched kernels so that the customer can keep paying
you
> (until they learn how to use a text editor, at which point they can patch
the
> kernel themselves!!!)
>
>
> --
> Timur Tabi - ttabi@interactivesi.com
> Interactive Silicon - http://www.interactivesi.com
>
> When replying to a mailing-list message, please direct the reply to the
mailing list only. Don't send another copy to me.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-31 1:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 0:08 Christopher Neufeld
2001-01-31 0:36 ` Timur Tabi
2001-01-31 1:44 ` List User [this message]
2001-01-31 9:15 ` James Sutherland
2001-01-31 0:44 ` Udo A. Steinberg
2001-01-31 9:10 ` Helge Hafting
2001-01-31 1:31 Bernd Eckenfels
2001-01-31 1:32 Bernd Eckenfels
2001-01-31 6:55 ` Peter Samuelson
2001-01-31 20:38 ` George
2001-01-31 20:45 ` Scott Laird
2001-01-31 20:52 ` nick
2001-01-31 20:58 ` Dan Hollis
2001-02-10 0:29 ` Dr. Kelsey Hudson
2001-02-24 13:46 ` Ralf Baechle
2001-01-31 10:27 Manfred Spraul
2001-01-31 16:26 Christopher Neufeld
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='033c01c08b27$5944a430$160912ac@stcostlnds2zxj' \
--to=lists@chaven.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ttabi@interactivesi.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
all inboxes | Powered by JetHome®