From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cleanup KERNEL_VERSION definition and linux/version.h
Date: Sat, 06 Apr 2002 13:41:46 +1000 [thread overview]
Message-ID: <14688.1018064506@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 05 Apr 2002 09:55:27 PST." <20020405175527.GK961@matchmail.com>
On Fri, 5 Apr 2002 09:55:27 -0800,
Mike Fedyk <mfedyk@matchmail.com> wrote:
>> >On Thu, Apr 04, 2002 at 11:36:06AM +1000, Keith Owens wrote:
>> Breaking that chain _might_ cause problems in 2.4 because it does not
>> have a complete dependency chain to pick up changes to the top level
>> Makefile, it only works at the moment due to the extra recompiles. I
>> am not willing to change this in 2.4 until I have got it stable in 2.5.
>
>Hmm. It looks like kbuild 2.5 might be able to be split up into a few
>separate parts. Do you think so too?
There are some bug fixes to existing makefiles and CML1 that can safely
be fed back to 2.4, I will do them next week. Apart from that, the
design philosophies for kbuild 2.4 and 2.5 are completely different,
there is little from kbuild 2.5 that can safely be extracted and back
ported to kbuild 2.4.
>Do you know where I could find some good documentation on Makefiles?
>Especially on dependencies and etc?
info make.
next prev parent reply other threads:[~2002-04-06 3:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 14:49 Hiroyuki Toda
2002-04-03 23:06 ` Keith Owens
2002-04-04 1:12 ` Hiroyuki Toda
2002-04-04 1:36 ` Keith Owens
2002-04-04 4:31 ` Hiroyuki Toda
2002-04-05 2:07 ` Mike Fedyk
2002-04-05 2:42 ` Keith Owens
2002-04-05 17:55 ` Mike Fedyk
2002-04-06 3:41 ` Keith Owens [this message]
2002-04-06 16:23 Dan Kegel
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=14688.1018064506@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®