public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sgi.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: xfs: Makefile-linux-2.6 => Makefile?
Date: Mon, 09 Jan 2006 15:23:39 -0600	[thread overview]
Message-ID: <43C2D45B.2050704@sgi.com> (raw)
In-Reply-To: <20060109212005.GC14477@mars.ravnborg.org>

Sam Ravnborg wrote:
> On Mon, Jan 09, 2006 at 03:03:57PM -0600, Eric Sandeen wrote:
>  
> 
>>Out of curiosity, what's the reason to drop VERSION & PATCHLEVEL... seems 
>>handy if you have a common body of code that needs to build for various 
>>kernels, with various Makefiles to suit.  As above. :)
> 
> The kernel is supposed to hold the code for the kernel - not a lot of
> backward compatibiliy cruft.

Understood, and it makes sense to yank that compat cruft from kernel.org codebases.

But it seems useful for projects outside the kernel which would like to know 
which kernel they are building against, as far as the build system goes.  I've 
seen a few drivers out there that try to keep building for both 2.4 & 2.6.

I guess for 2.4 & 2.6, the same can be accomplished by using Makefile and 
Kbuild for 2.4 and 2.6....

Maybe you can export it only if KBUILD_EXTMOD is set :)

Thanks,
-Eric

  reply	other threads:[~2006-01-09 21:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 16:42 xfs: Makefile-linux-2.6 => Makefile? Sam Ravnborg
2006-01-09 16:46 ` Christoph Hellwig
2006-01-09 17:19   ` Sam Ravnborg
2006-01-09 21:01   ` Sam Ravnborg
2006-01-09 21:05     ` Christoph Hellwig
2006-01-09 21:18       ` Sam Ravnborg
2006-01-09 21:03   ` Eric Sandeen
2006-01-09 21:20     ` Sam Ravnborg
2006-01-09 21:23       ` Eric Sandeen [this message]
2006-01-09 21:45         ` Sam Ravnborg
2006-01-10  7:45     ` Andrew Morton
2006-01-10 15:14       ` Eric Sandeen
2006-01-10 16:34       ` Eric Sandeen
2006-01-10 20:02         ` Sam Ravnborg
2006-01-16 23:19         ` Sam Ravnborg
2006-01-17  3:40           ` Eric Sandeen
2006-01-10 20:00       ` Sam Ravnborg

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=43C2D45B.2050704@sgi.com \
    --to=sandeen@sgi.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --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