From: Ed L Cashin <ecashin@coraid.com>
To: Greg KH <greg@kroah.com>
Cc: PPC_LINUX <linuxppc-embedded@ozlabs.org>,
akpm@zip.com.au, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.11.7] ATA Over Ethernet Root, Mark 2
Date: Mon, 16 May 2005 13:03:22 -0400 [thread overview]
Message-ID: <87wtpz5cit.fsf@coraid.com> (raw)
In-Reply-To: <20050516162011.GA8716@kroah.com> (Greg KH's message of "Mon, 16 May 2005 09:20:11 -0700")
Greg KH <greg@kroah.com> writes:
> On Mon, May 16, 2005 at 09:14:02AM -0400, McMullan, Jason wrote:
...
[gregkh writes]
>> > Also, please CC the aoe maintainer, that's documented in
>> > Documentation/SubmittingPatches :)
>>
>> I did to support@coraid.com, in a separate message.
>
> That's not the email address listed in MAINTAINERS, is it?
I did get it, though. I didn't realize that the reason for the patch
is for use on systems that have so little RAM that they can't have an
initrd.
It seems like the system will hang forever with no diagnostics if the
root device isn't found. Perhaps an error message would be helpul?
I do wonder whether the problem this patch solves might be a special
case that doesn't merit the extra complexity of a Kconfig knob. It is
certainly a useful patch for some users, but I don't know how many.
--
Ed L Cashin <ecashin@coraid.com>
WARNING: multiple messages have this Message-ID (diff)
From: Ed L Cashin <ecashin@coraid.com>
To: Greg KH <greg@kroah.com>
Cc: "McMullan, Jason" <jason.mcmullan@timesys.com>,
akpm@zip.com.au, Linux Kernel <linux-kernel@vger.kernel.org>,
PPC_LINUX <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH 2.6.11.7] ATA Over Ethernet Root, Mark 2
Date: Mon, 16 May 2005 13:03:22 -0400 [thread overview]
Message-ID: <87wtpz5cit.fsf@coraid.com> (raw)
In-Reply-To: <20050516162011.GA8716@kroah.com> (Greg KH's message of "Mon, 16 May 2005 09:20:11 -0700")
Greg KH <greg@kroah.com> writes:
> On Mon, May 16, 2005 at 09:14:02AM -0400, McMullan, Jason wrote:
...
[gregkh writes]
>> > Also, please CC the aoe maintainer, that's documented in
>> > Documentation/SubmittingPatches :)
>>
>> I did to support@coraid.com, in a separate message.
>
> That's not the email address listed in MAINTAINERS, is it?
I did get it, though. I didn't realize that the reason for the patch
is for use on systems that have so little RAM that they can't have an
initrd.
It seems like the system will hang forever with no diagnostics if the
root device isn't found. Perhaps an error message would be helpul?
I do wonder whether the problem this patch solves might be a special
case that doesn't merit the extra complexity of a Kconfig knob. It is
certainly a useful patch for some users, but I don't know how many.
--
Ed L Cashin <ecashin@coraid.com>
next prev parent reply other threads:[~2005-05-16 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 19:17 [PATCH 2.6.11.7] ATA Over Ethernet Root, Mark 2 McMullan, Jason
2005-05-14 7:28 ` Greg KH
2005-05-16 13:20 ` McMullan, Jason
2005-05-16 13:20 ` McMullan, Jason
2005-05-16 16:20 ` Greg KH
2005-05-16 16:20 ` Greg KH
2005-05-16 17:03 ` Ed L Cashin [this message]
2005-05-16 17:03 ` Ed L Cashin
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=87wtpz5cit.fsf@coraid.com \
--to=ecashin@coraid.com \
--cc=akpm@zip.com.au \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-embedded@ozlabs.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 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.