From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Jes Sorensen <jes@linuxcare.com>
Cc: Rogier Wolff <R.E.Wolff@bitwizard.nl>,
Mitchell Blank Jr <mitch@sfgoth.com>,
Patrick van de Lageweg <patrick@bitwizard.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rogier Wolff <wolff@bitwizard.nl>
Subject: Re: [NEW DRIVER] firestream
Date: Wed, 22 Nov 2000 18:41:23 -0500 [thread overview]
Message-ID: <3A1C59A3.52AA42B3@mandrakesoft.com> (raw)
In-Reply-To: <200011222305.AAA30264@cave.bitwizard.nl> <d366lflgvl.fsf@lxplus015.cern.ch>
Jes Sorensen wrote:
> I think the most important issue is when doing header files to make
> sure they go with the driver code and not in include/linux unless
> there really is a reason to expose them to user space. No reason to
> export register definitions for Ethernet cards down there.
Agreed, that there are some headers that IMHO need to be moved out of
include/linux because they aren't used in userspace, and they aren't
public interfaces, nor shared across directories.
--
Jeff Garzik |
Building 1024 | The chief enemy of creativity is "good" sense
MandrakeSoft | -- Picasso
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-23 0:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 9:32 [NEW DRIVER] firestream Patrick van de Lageweg
2000-11-22 17:23 ` Mitchell Blank Jr
2000-11-22 23:05 ` Rogier Wolff
2000-11-22 23:35 ` Jes Sorensen
2000-11-22 23:41 ` Jeff Garzik [this message]
2000-11-23 11:15 ` Rogier Wolff
2000-11-23 11:44 ` Peter Samuelson
2000-11-23 11:52 ` Rogier Wolff
2000-11-23 11:28 ` Werner Almesberger
2000-11-23 5:40 ` Peter Samuelson
2000-11-23 8:22 ` Rogier Wolff
2000-11-23 8:40 ` Peter Samuelson
2000-11-23 10:32 ` Vojtech Pavlik
2000-11-23 22:19 ` Bartlomiej Zolnierkiewicz
2000-11-23 23:43 ` Rogier Wolff
-- strict thread matches above, loose matches on Subject: below --
2000-11-29 8:45 Patrick van de Lageweg
2000-12-06 8:45 Patrick van de Lageweg
2000-12-12 15:44 Patrick van de Lageweg
2000-12-15 12:07 Patrick van de Lageweg
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=3A1C59A3.52AA42B3@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=R.E.Wolff@bitwizard.nl \
--cc=jes@linuxcare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitch@sfgoth.com \
--cc=patrick@bitwizard.nl \
--cc=wolff@bitwizard.nl \
/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