From: Alan Cox <alan@redhat.com>
To: James Mcloughlin <jimbob@osoffice.co.uk>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: kernel patch set - please read
Date: Tue, 14 Mar 2006 07:42:22 -0500 [thread overview]
Message-ID: <20060314124222.GA7514@devserv.devel.redhat.com> (raw)
In-Reply-To: <1140.81.178.12.23.1142280938.squirrel@www.osoffice.co.uk>
On Mon, Mar 13, 2006 at 08:15:38PM -0000, James Mcloughlin wrote:
> People realise that these old boxes are still good for hosting, as you
> dont need a super 3ghz server for a few small web sites...
>
> I wonder if you would consider adding cobalt hardware support to the 2.6
> kernel tree?
Its up to someone who has the hardware to merge any additional hardware support
that is needed and maintain it. If you are building your own trees to do this
and having to add other GPL drivers then you might be ideally placed to do that.
Alan
prev parent reply other threads:[~2006-03-14 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 20:15 kernel patch set - please read James Mcloughlin
2006-03-13 21:00 ` Jesper Juhl
2006-03-14 12:42 ` Alan Cox [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=20060314124222.GA7514@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=jimbob@osoffice.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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