mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Guilak <guilak@linux.vnet.ibm.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	daniel@danielguilak.com
Subject: Re: [PATCH] init/version.c: Define version_string only if CONFIG_KALLSYMS is not defined.
Date: Mon, 14 Jul 2008 15:29:46 -0700	[thread overview]
Message-ID: <1216074586.6497.37.camel@dguilak-desk> (raw)
In-Reply-To: <20080714150731.e86295b2.randy.dunlap@oracle.com>

On Mon, 2008-07-14 at 15:07 -0700, Randy Dunlap wrote:
> On Mon, 14 Jul 2008 14:20:38 -0700 Daniel Guilak wrote:
> 
> > On Mon, 2008-07-14 at 12:38 -0700, Randy Dunlap wrote:
> > > On Mon, 14 Jul 2008 12:04:46 -0700 Daniel Guilak wrote:
> > > 
> > > > int Version_* is only used with ksymoops, which is only needed (according to
> > > > README and Documentation/Changes) if CONFIG_KALLSYMS is NOT defined.  Therefore
> > > > this patch defines version_string only if CONFIG_KALLSYMS is not defined.
> > > > 
> > > > Signed-off-by: Daniel Guilak <daniel@danielguilak.com>
> > > > ---
> > > >  init/version.c |    2 ++
> > > >  1 files changed, 2 insertions(+), 0 deletions(-)
> > > > 
> > > > Depends on "[PATCH] init/version.c: Silenced sparse warning by declaring the version string."
> > > > 
> > > > diff --git a/init/version.c b/init/version.c
> > > > index 041fd82..52a8b98 100644
> > > > --- a/init/version.c
> > > > +++ b/init/version.c
> > > > @@ -13,11 +13,13 @@
> > > >  #include <linux/utsrelease.h>
> > > >  #include <linux/version.h>
> > > >  
> > > > +#ifndef CONFIG_KALLSYMS
> > > >  #define version(a) Version_ ## a
> > > >  #define version_string(a) version(a)
> > > >  
> > > >  extern int version_string(LINUX_VERSION_CODE);
> > > >  int version_string(LINUX_VERSION_CODE);
> > > > +#endif
> > > >  
> > > >  struct uts_namespace init_uts_ns = {
> > > >  	.kref = {
> > > > -- 
> > > 
> > > Does not apply cleanly to linux-2.6.26, linux-next-20080714, or Linus-git-head.
> > > 
> > 
> > Did you apply "[PATCH] init/version.c: Silenced sparse warning by
> > declaring the version string." beforehand? I just applied it on the most
> > recent tree and I didn't have any issues.
> 
> Clearly I didn't apply that patch.  I missed anything saying that this was
> patch 2/2 in a dependent series.

Sorry about that, I should have been a bit more clear with it. Next
time I'll make sure to state that in the subject line. I stated the
dependency right before the diff message.

> > > and why do we ned both extern int version_string()
> > > and int version_string() ?
> > Because sparse was complaining that it wasn't prototyped or static.
> > There isn't a header file to put it in since it only exists to be a
> > kernel.
> 
> so the extern makes it be published in the symbol table, whereas a static
> would keep it private.  Is that correct?
> 
> and the second line (int version_string(LINUX_VERSION_CODE)) actually
> defines it.

Yes, that's exactly the idea behind it.

--Daniel


      reply	other threads:[~2008-07-14 22:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 21:21 [PATCH] init/version.c: Silenced sparse warning by declaring the version string Daniel Guilak
2008-07-09  1:10 ` Josh Triplett
2008-07-11 19:18 ` Andrew Morton
2008-07-14 19:02   ` Daniel Guilak
2008-07-14 19:04 ` [PATCH] init/version.c: Define version_string only if CONFIG_KALLSYMS is not defined Daniel Guilak
2008-07-14 19:38   ` Randy Dunlap
2008-07-14 21:20     ` Daniel Guilak
2008-07-14 21:25       ` Daniel Guilak
2008-07-14 22:07       ` Randy Dunlap
2008-07-14 22:29         ` Daniel Guilak [this message]

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=1216074586.6497.37.camel@dguilak-desk \
    --to=guilak@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=daniel@danielguilak.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=torvalds@linux-foundation.org \
    --cc=trivial@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

all inboxes | Powered by JetHome®