From: David Woodhouse <dwmw2@infradead.org>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: Greg KH <greg@kroah.com>, Jan Hudec <bulb@ucw.cz>,
linux-fsdevel@vger.kernel.org
Subject: Re: buffer cache
Date: Tue, 16 Sep 2003 06:13:51 +0100 [thread overview]
Message-ID: <1063689231.788.63.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <OFF20A09E8.52CAFEDE-ON87256DA2.007AD80B-88256DA2.007C8EA9@us.ibm.com>
On Mon, 2003-09-15 at 15:41 -0700, Bryan Henderson wrote:
> >> 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.
>
> I think that's a bit of an overstatement.
I accept the idea. I also accept the idea that said module writer can
also write all his own include files _too_, and avoid even having to
have a kernel tree around at all.
I think he'd have to be on crack, but I do accept that he _can_ do that.
But I don't want him asking for support, and I don't want him advocating
this practice to newbies.
Do what you like in the privacy of your own home; I really couldn't give
a monkey's. Just don't talk about it in public :)
--
dwmw2
next prev parent reply other threads:[~2003-09-16 5:13 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
2003-09-15 22:41 ` Bryan Henderson
2003-09-16 5:13 ` David Woodhouse [this message]
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=1063689231.788.63.camel@imladris.demon.co.uk \
--to=dwmw2@infradead.org \
--cc=bulb@ucw.cz \
--cc=greg@kroah.com \
--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