From: John Levon <levon@movementarian.org>
To: linux-kernel@vger.kernel.org
Cc: hch@infradead.org, kai-germaschewski@uiowa.edu
Subject: Re: RfC: Don't cd into subdirs during kbuild
Date: Thu, 3 Oct 2002 15:45:59 +0100 [thread overview]
Message-ID: <20021003144559.GC56233@compsoc.man.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0210030922270.24570-100000@chaos.physics.uiowa.edu>
On Thu, Oct 03, 2002 at 09:27:49AM -0500, Kai Germaschewski wrote:
> Since it gives Rules.make the wrong file names in $(obj-[ym]), and relies
> on implementation details inside of Rules.make in combination with the
> vpath statement to make things work despite those wrong names.
This sounds like kbuild's problem not mine. That is, I don't see
anything particularly ugly in using vpath.
> So did you decide to move things from drivers/oprofile/$(ARCH) to
> arch/$(ARCH)/oprofile? It's possible to make it work, but not pretty. As I
> said before, kbuild actually expects to have all parts of a single module
> to be in a single dir. This can be lifted a little bit as done for xfs,
> but spreading parts all over the tree is not very desirable IMO.
Can the kernel people decide amongst themselves what they want, then
I'll just do it ?
Personally, the arch/ drivers/ split seems perfectly natural for
oprofile.
regards
john
--
"Me and my friends are so smart, we invented this new kind of art:
Post-modernist throwing darts"
- the Moldy Peaches
next prev parent reply other threads:[~2002-10-03 14:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 2:59 Kai Germaschewski
2002-10-03 3:32 ` Andreas Dilger
2002-10-03 5:18 ` [kbuild-devel] " Peter Samuelson
2002-10-03 14:54 ` Kai Germaschewski
2002-10-03 8:21 ` Xavier Bestel
2002-10-03 14:56 ` Kai Germaschewski
2002-10-03 15:31 ` Xavier Bestel
2002-10-03 20:41 ` Peter Samuelson
2002-10-03 14:05 ` John Levon
2002-10-03 14:27 ` Kai Germaschewski
2002-10-03 14:45 ` John Levon [this message]
2002-10-03 19:26 ` Sam Ravnborg
2002-10-03 19:33 ` [kbuild-devel] " Sam Ravnborg
2002-10-03 20:01 ` Sam Ravnborg
2002-10-03 20:19 ` Kai Germaschewski
2002-10-03 20:44 ` Sam Ravnborg
2002-10-03 20:20 ` Peter Samuelson
2002-10-03 20:30 ` Sam Ravnborg
2002-10-03 20:38 ` Kai Germaschewski
2002-10-03 20:50 ` Sam Ravnborg
2002-10-04 19:07 ` Sam Ravnborg
2002-10-04 20:17 ` Sam Ravnborg
2002-10-09 0:45 ` [kbuild-devel] " Brendan J Simon
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=20021003144559.GC56233@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=hch@infradead.org \
--cc=kai-germaschewski@uiowa.edu \
--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®