From: Greg KH <gregkh@gentoo.org>
To: Terje Kvernes <terjekv@math.uio.no>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Too many kernels?
Date: Fri, 9 Jul 2004 18:28:35 -0700 [thread overview]
Message-ID: <20040710012835.GB7149@kroah.com> (raw)
In-Reply-To: <wxxd634psat.fsf@nommo.uio.no>
On Sat, Jul 10, 2004 at 03:25:14AM +0200, Terje Kvernes wrote:
> but, since I'm curious... Greg, are you maintaining g-d-s these
> days?
Yes I primarily am (with help from others at times.)
> SATA shouldn't be a problem there, should it? :-)
Works for me :)
> Terje - who wants to try the hotswap SATA canisters on his server.
Hm, I don't know if we have hotplug SATA support in the kernel just yet.
thanks,
greg k-h
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-07-10 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 23:22 [gentoo-dev] Too many kernels? Grant Goodyear
2004-07-09 23:32 ` Greg KH
2004-07-09 23:57 ` Mike Frysinger
2004-07-10 11:01 ` Michael Kohl
2004-07-10 1:25 ` Terje Kvernes
2004-07-10 1:28 ` Greg KH [this message]
2004-07-12 20:45 ` Aron Griffis
2004-07-09 23:35 ` Kumba
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=20040710012835.GB7149@kroah.com \
--to=gregkh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=terjekv@math.uio.no \
/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