From: Sam Ravnborg <sam@ravnborg.org>
To: Eric Sandeen <sandeen@sgi.com>
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, 9 Jan 2006 22:45:44 +0100 [thread overview]
Message-ID: <20060109214544.GA17315@mars.ravnborg.org> (raw)
In-Reply-To: <43C2D45B.2050704@sgi.com>
On Mon, Jan 09, 2006 at 03:23:39PM -0600, Eric Sandeen wrote:
> 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....
Good point. External modules slipped my mind when I did this change.
We have today:
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 15
EXTRAVERSION =
EXTRAVERSION will soon become -rc1
No sane driver will check for more than VERISON, PATCHLEVEL, SUBLEVEL.
xfs for once only used VERSION, PATCHLEVEL.
googling a little gave lot's of very ugly examples how it can be done
using grep, perl etc. So there is a legitim need for the variable
anyway.
So I will re-export VERISON, PATCHLEVEL, SUBLEVEL.
Sam
next prev parent reply other threads:[~2006-01-09 21:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 16:42 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
2006-01-09 21:45 ` Sam Ravnborg [this message]
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=20060109214544.GA17315@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=sandeen@sgi.com \
/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®