From: Ed L Cashin <ecashin@coraid.com>
To: Greg KH <greg@kroah.com>
Cc: 7eggert@gmx.de, linux-kernel@vger.kernel.org
Subject: /sys/module (was Re: [PATCH 2.6.12-rc2] aoe [1/6]: improve allowed interfaces configuration)
Date: Thu, 21 Apr 2005 12:11:39 -0400 [thread overview]
Message-ID: <87u0m0f6tg.fsf_-_@coraid.com> (raw)
In-Reply-To: <20050421160104.GA10221@kroah.com> (Greg KH's message of "Thu, 21 Apr 2005 09:01:04 -0700")
Greg KH <greg@kroah.com> writes:
...
> It's not for things other than modules, it's filling a real need that
> you yourself just pointed out. Namely, we need to be able to have
> access to module paramaters in a consistant place, no matter if the
> driver is built into the kernel or not.
>
> Man, you try to be nice to people... :)
It wasn't a complaint --- like I said, I'm pleased! I just wanted to
serve as a datum: one guy was surprised.
I wanted to put the interfaces list configuration into sysfs, but I
didn't really know how or where to put it, so I procrastinated. Then
I created the module parameter and was pleased to see it show up in
sysfs. I had read about module parameters before, but I had forgotten
about that feature, or maybe it's newer than the docs I read.
Thanks for working so hard to make sysfs useful.
--
Ed L Cashin <ecashin@coraid.com>
next prev parent reply other threads:[~2005-04-21 16:22 UTC|newest]
Thread overview: 8+ 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 ` Ed L Cashin [this message]
2005-04-21 16:32 ` Randy.Dunlap
2005-04-21 20:54 ` Domen Puncer
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=87u0m0f6tg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox