All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Borislav Petkov <bp@alien8.de>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] include/version.h: Update for kernel 3.7
Date: Mon, 15 Oct 2012 21:43:07 -0500	[thread overview]
Message-ID: <507CC9BB.2020007@lwfinger.net> (raw)
In-Reply-To: <20121015215411.GB28086@liondog.tnic>

On 10/15/2012 04:54 PM, Borislav Petkov wrote:
> On Mon, Oct 15, 2012 at 04:43:27PM -0500, Larry Finger wrote:
>> The value for LINUX_VERSION_CODE was not updated for kernel 3.7-rc1.
>
> That's probably fallout from the whole UAPI thing.
>
>>
>> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
>> ---
>>   version.h |    2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>> ---
>>
>> Index: linux-2.6/include/linux/version.h
>> ===================================================================
>> --- linux-2.6.orig/include/linux/version.h
>> +++ linux-2.6/include/linux/version.h
>> @@ -1,2 +1,2 @@
>
> There are two version.h files on my box:
>
>> -#define LINUX_VERSION_CODE 198144
>
> This is in <include/linux/version.h>
>
>> +#define LINUX_VERSION_CODE 198400
>
> This is in <include/generated/uapi/linux/version.h>
>
> I'd guess that everything should include this new version.h file now
> since the Makefile generates this now and not the one above.
>
> But I could very well be wrong.

It seems to be fixed now.

Thanks,

Larry



  reply	other threads:[~2012-10-16  2:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15 21:43 [PATCH] include/version.h: Update for kernel 3.7 Larry Finger
2012-10-15 21:54 ` Borislav Petkov
2012-10-16  2:43   ` Larry Finger [this message]
2012-10-16  2:53 ` Theodore Ts'o

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=507CC9BB.2020007@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.