Re: some version_string() magic i'm not aware of?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 9 Sep 2007, Vegard Nossum wrote:

> On 9/8/07, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote:
> > #define version(a) Version_ ## a
> > #define version_string(a) version(a)
> >
> > int version_string(LINUX_VERSION_CODE);
> > ...
> >
> > puzzled because this appears to be the only place in the entire
> > tree that uses the macro version_string().  so is there some
> > reason it even exists, as opposed to just using version() as it's
> > defined there?
>
> The double macro is needed to create a symbol with the name
> Version_<LINUX_VERSION_CODE>. If you simply replace "version_string"
> with "version", you'd get a symbol named
> "Version_LINUX_VERSION_CODE".

ah, quite right -- i *figured* there was a reason for that, i just
didn't see it right away.  thanks.

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================
-
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel Development]     [Kernel Announce]     [Kernel Newbies]     [Linux Networking Development]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Device Mapper]

  Powered by Linux