From: Ed L Cashin <ecashin@coraid.com>
To: 7eggert@gmx.de
Cc: linux-kernel@vger.kernel.org, Greg K-H <greg@kroah.com>
Subject: Re: [PATCH 2.6.12-rc2] aoe [1/6]: improve allowed interfaces configuration
Date: Thu, 21 Apr 2005 09:36:17 -0400 [thread overview]
Message-ID: <87y8bcjlpq.fsf@coraid.com> (raw)
In-Reply-To: <E1DOVtj-0003bF-6c@be1.7eggert.dyndns.org> (Bodo Eggert's message of "Thu, 21 Apr 2005 09:14:46 +0200")
"Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>" <7eggert@gmx.de> writes:
> Ed L Cashin <ecashin@coraid.com> wrote:
>
>> +++ b/Documentation/aoe/aoe.txt 2005-04-20 11:42:20.000000000 -0400
>
>> + When the aoe driver is a module, use
>
> Is there any reason for this inconsistent behaviour?
Yes, the /sys/module/aoe area is only present when the aoe driver is a
module. It would be nicer if there were a sysfs area where I could
put this file regardless of whether the driver is a module or built
into the kernel.
I could probably create one, but I got the file in
/sys/module/aoe/parameters for free when I used module_param_string.
>> + /sys/module/aoe/parameters/aoe_iflist instead of
> ^^^
>
> Why does the module name need to be part of the attribute?
> That's redundant. That's redundant.
Yes. That's true. Redundancy isn't always bad, though, and using the
"aoe_" prefix lets the kernel parameter for the built-in aoe driver be
the same as the parameter for the modular driver.
--
Ed L Cashin <ecashin@coraid.com>
next prev parent reply other threads:[~2005-04-21 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3VqSf-2z7-15@gated-at.bofh.it>
2005-04-21 7:14 ` [PATCH 2.6.12-rc2] aoe [1/6]: improve allowed interfaces configuration Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
2005-04-21 13:36 ` Ed L Cashin [this message]
2005-04-21 14:56 ` Greg KH
2005-04-21 15:30 ` Ed L Cashin
2005-04-21 16:01 ` Greg KH
2005-04-21 16:11 ` /sys/module (was Re: [PATCH 2.6.12-rc2] aoe [1/6]: improve allowed interfaces configuration) Ed L Cashin
2005-04-21 16:32 ` [PATCH 2.6.12-rc2] aoe [1/6]: improve allowed interfaces configuration Randy.Dunlap
2005-04-21 20:54 ` Domen Puncer
2005-04-20 17:02 Ed L Cashin
2005-04-20 17:16 ` Randy.Dunlap
2005-04-20 17:27 ` 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=87y8bcjlpq.fsf@coraid.com \
--to=ecashin@coraid.com \
--cc=7eggert@gmx.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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.