public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH RFC] put UTS_RELEASE in separate utsversion.h file
Date: Sat, 28 Jan 2006 16:28:34 -0800	[thread overview]
Message-ID: <20060129002834.GA8525@kroah.com> (raw)
In-Reply-To: <20060128215937.GA14442@mars.ravnborg.org>

On Sat, Jan 28, 2006 at 10:59:37PM +0100, Sam Ravnborg wrote:
> During the last few days I have been toying with a allmodconfig tree
> and got irritated by all the extra modules being build over and over
> again.
> The root cause was the definition of UTS_RELEASE in version.h.
> I had enabled automatic appending of git version and it changed each
> time I committed something resulting in a lot of recompiling.
> With the following patch the recompile is kept minimal, the most
> annoying part being all the .mod.c files - but they actually use
> UTS_RELEASE so this is avoidable.
> 
> I have not updated checkversion.pl - Randy can you do that?
> 
> I have not applied the patch yet - wanted some feedback from lkml first.
> Only functional changes is in top-level makefile.
> For all users of UTS_RELEASE I simple included utsversion.h.
> 
> Note: I do not know if any external stuff(*) uses UTS_RELEASE and expect it
> to be in version.h!
> 
> (*) I here think of glibc, gcc, udev etc.

udev does not build against any kernel file, nor care about what kernel
is installed when built.  It also really doesn't check kernel info when
it is running either...

I like this patch, as someone who builds with a lot of modules enabled
:)

thanks,

greg k-h

  reply	other threads:[~2006-01-29  0:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-28 21:59 [PATCH RFC] put UTS_RELEASE in separate utsversion.h file Sam Ravnborg
2006-01-29  0:28 ` Greg KH [this message]
2006-01-30  9:03 ` Jan Engelhardt

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=20060129002834.GA8525@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sam@ravnborg.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