From: Dmitry Torokhov <dtor@vmware.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] Show version information for built-in modules in sysfs
Date: Wed, 15 Dec 2010 15:53:12 -0800 [thread overview]
Message-ID: <20101215235312.GA15328@dtor-ws.eng.vmware.com> (raw)
In-Reply-To: <AANLkTindv4GUp3E8Vzkzm_JzGxxOP+TdaAsVhxrEVOw6@mail.gmail.com>
On Wed, Dec 15, 2010 at 03:25:27PM -0800, Alexey Dobriyan wrote:
> On Thu, Dec 16, 2010 at 12:14 AM, Dmitry Torokhov <dtor@vmware.com> wrote:
> > On Wed, Dec 15, 2010 at 02:06:03PM -0800, Alexey Dobriyan wrote:
> >> On Thu, Dec 16, 2010 at 12:00 AM, Dmitry Torokhov <dtor@vmware.com> wrote:
> >> > Currently only drivers that are built as modules have their versions
> >> > shown in /sys/module/<module_name>/version, but this information might
> >>
> >> Can you create just /sys/module/x?
> >> Module version info is quite useless by itself.
> >
> > It is as useful as in the case where driver is built as a module. I am
> > just trying to unify the behavior a bit.
> >
> > Code-wise it is almost as cheap to add /sys/module/x/version as adding
> > just the directory.
>
> OK.
>
> Still, people are using /sys/module/x presence as indicator of modular
> built (unsurprisingly).
>
> http://codesearch.google.com/codesearch/p?hl=en#wZuuyuB8jKQ/src/third_party/autotest/files/client/profilers/powertop/src/bluetooth.c&q=/sys/modules&sa=N&cd=3&ct=rc&l=105
Yeah, I hate to disappoint them but it will break as soon as someone
adds a module_param() to one of the objects... That's even without my
changes.
--
Dmitry
next prev parent reply other threads:[~2010-12-15 23:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 22:00 [PATCH] Show version information for built-in modules in sysfs Dmitry Torokhov
2010-12-15 22:06 ` Alexey Dobriyan
2010-12-15 22:14 ` Dmitry Torokhov
2010-12-15 23:25 ` Alexey Dobriyan
2010-12-15 23:53 ` Dmitry Torokhov [this message]
2010-12-16 0:30 ` Dmitry Torokhov
2010-12-16 12:58 ` Alexey Dobriyan
2010-12-22 1:45 ` Rusty Russell
2010-12-22 1:02 ` Rusty Russell
2010-12-22 1:17 ` Dmitry Torokhov
2010-12-22 1:48 ` Rusty Russell
2010-12-23 0:38 ` Dmitry Torokhov
2010-12-23 2:27 ` Rusty Russell
2011-01-11 19:03 ` Dmitry Torokhov
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=20101215235312.GA15328@dtor-ws.eng.vmware.com \
--to=dtor@vmware.com \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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