public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Mathieu SEGAUD <mathieu.segaud@regala.cx>
Cc: "rae l" <crquan@gmail.com>,
	open-iscsi@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC on MODULE SUPPORT] hello, Rusty, Should we provide module information even if the kernel module compiled built-in with bzImage?
Date: Thu, 17 Jan 2008 09:15:25 +1100	[thread overview]
Message-ID: <200801170915.26040.rusty@rustcorp.com.au> (raw)
In-Reply-To: <87fxwyhtim.fsf@barad-dur.regala.cx>

On Wednesday 16 January 2008 22:58:09 Mathieu SEGAUD wrote:
> your userspace program is somewhat broken
> the userspace should not expect to find the version number in
> /sys/module, as this is used by the Linux kernel module subsystem. You
> should provide the required information in another way such as a
> /proc/ file (bad) or a /sys file (better, but no module stuff, this
> has no business with it).

Shh!  He was going to implement a feature we want!

To be honest, I think his expectations of consistency are correct: if a 
version number makes sense, surely it makes sense for builtins as well.

Thanks,
Rusty.

  reply	other threads:[~2008-01-16 22:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 10:02 [RFC on MODULE SUPPORT] hello, Rusty, Should we provide module information even if the kernel module compiled built-in with bzImage? rae l
2008-01-16 11:58 ` Mathieu SEGAUD
2008-01-16 22:15   ` Rusty Russell [this message]
2008-01-17  8:29     ` Mathieu SEGAUD
2008-01-16 12:25 ` Rusty Russell
2008-01-16 12:59 ` Sam Ravnborg

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=200801170915.26040.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=crquan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.segaud@regala.cx \
    --cc=open-iscsi@googlegroups.com \
    /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