From: Greg KH <greg@kroah.com>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: David Woodhouse <dwmw2@infradead.org>, Jan Hudec <bulb@ucw.cz>,
linux-fsdevel@vger.kernel.org
Subject: Re: buffer cache
Date: Mon, 15 Sep 2003 09:35:51 -0700 [thread overview]
Message-ID: <20030915163551.GC1433@kroah.com> (raw)
In-Reply-To: <OF4823E92C.DA959E14-ON87256DA2.005808AE-88256DA2.00598359@us.ibm.com>
On Mon, Sep 15, 2003 at 09:18:38AM -0700, Bryan Henderson wrote:
> >The correct way to build modules out of the kernel tree is to use the
> >kernel makefiles and override SUBDIRS to point at your own directory;
>
> That philosophy seems to fly in the face of the very modularity that makes
> modules great. If you accept the idea that your module source code should
> be arranged the same way as Linux kernel source code and built the same
> way, you might as well just maintain your code as a patch to the Linux
> source tree.
>
> But if you accept the idea that a module writer can write his own make
> file, then he is free to organize the source code in original ways, use a
> language other than C, and share code or structure with non-Linux
> applications (e.g. device drivers for the same device in other OSes).
Um, I think the point is that no one does accept that idea. And if you
try to write your own makefile, then you deserve any problems that you
might have, as the kernel build developers have repeatedly told people
how to do this properly so that things to not break.
greg k-h
next prev parent reply other threads:[~2003-09-15 16:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 8:51 buffer cache vadiraj c s
2003-09-13 10:27 ` Jan Hudec
2003-09-13 13:14 ` Matthew Wilcox
2003-09-13 17:25 ` Bryan Henderson
2003-09-13 17:28 ` Jan Hudec
2003-09-14 9:32 ` David Woodhouse
2003-09-14 10:03 ` Jan Hudec
2003-09-14 10:37 ` David Woodhouse
2003-09-14 11:19 ` Jan Hudec
2003-09-15 16:18 ` Bryan Henderson
2003-09-15 16:35 ` Greg KH [this message]
2003-09-15 22:41 ` Bryan Henderson
2003-09-16 5:13 ` David Woodhouse
2003-09-16 10:18 ` Jamie Lokier
2003-09-16 12:16 ` David Woodhouse
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=20030915163551.GC1433@kroah.com \
--to=greg@kroah.com \
--cc=bulb@ucw.cz \
--cc=dwmw2@infradead.org \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@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