From: Domen Puncer <domen@coderock.org>
To: Ed L Cashin <ecashin@coraid.com>
Cc: 7eggert@gmx.de, 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 22:54:25 +0200 [thread overview]
Message-ID: <20050421205425.GA14686@nd47.coderock.org> (raw)
In-Reply-To: <87y8bcjlpq.fsf@coraid.com>
On 21/04/05 09:36 -0400, Ed L Cashin wrote:
> "Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>" <7eggert@gmx.de> writes:
>
> > Ed L Cashin <ecashin@coraid.com> wrote:
> >
...
> >> + /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.
The __setup() stuff is redundancy too, as module parameters already
work as boot parameters (ie. aoe.iflist).
Domen
next prev parent reply other threads:[~2005-04-21 20:54 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
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 [this message]
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=20050421205425.GA14686@nd47.coderock.org \
--to=domen@coderock.org \
--cc=7eggert@gmx.de \
--cc=ecashin@coraid.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox