public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: does CONFIG_MODULE_SRCVERSION_ALL depend on MODULE_VERSION?
Date: Sun, 28 Jun 2009 07:56:19 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0906280752060.7674@localhost> (raw)


  from the help text for CONFIG_MODULE_SRCVERSION_ALL:

"Modules which contain a MODULE_VERSION get an extra "srcversion"
field inserted into their modinfo section, which contains a
sum of the source files which made it.  This helps maintainers
see exactly which source was used to build a module (since
others sometimes change the module source without updating
the version).  With this option, such a "srcversion" field
will be created for all modules.  If unsure, say N."

  that first sentence suggests that calculating a module's
"srcversion" value depends on whether you've provided a MODULE_VERSION
value, but that doesn't seem to be the case based on a test i just
made.  and it seems to disagree with the later sentence that this
CONFIG option will generate a srcversion value for "all" modules
regardless.

  clarification?  it seems that first sentence is misleading, unless
i'm misreading it.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

        Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Linked In:                             http://www.linkedin.com/in/rpjday
Twitter:                                       http://twitter.com/rpjday
========================================================================

                 reply	other threads:[~2009-06-28 11:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LFD.2.00.0906280752060.7674@localhost \
    --to=rpjday@crashcourse.ca \
    --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