From: Greg KH <greg@kroah.com>
To: Ed L Cashin <ecashin@coraid.com>
Cc: 7eggert@gmx.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.12-rc2] aoe [1/6]: improve allowed interfaces configuration
Date: Thu, 21 Apr 2005 09:01:04 -0700 [thread overview]
Message-ID: <20050421160104.GA10221@kroah.com> (raw)
In-Reply-To: <87pswoi1vl.fsf@coraid.com>
On Thu, Apr 21, 2005 at 11:30:06AM -0400, Ed L Cashin wrote:
> Greg KH <greg@kroah.com> writes:
>
> > On Thu, Apr 21, 2005 at 09:36:17AM -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:
> >> >
> >> >> +++ 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.
> >
> > Not true, have you looked in /sys/module lately? :)
> >
> >> 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.
> >
> > That's the place for it. It will be there if the driver is built as a
> > module or into the kernel.
>
> Wow! Well, that's very convenient for driver writers, so I'm pleased,
> and I can update the docs. It surprises me, though, to find out that
> /sys/module is for things other than modules.
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... :)
thanks,
greg k-h
next prev parent reply other threads:[~2005-04-21 16:01 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 [this message]
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=20050421160104.GA10221@kroah.com \
--to=greg@kroah.com \
--cc=7eggert@gmx.de \
--cc=ecashin@coraid.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.