From: "Gregory T. Norris" <haphazard@socket.net>
To: rio500-devel <rio500-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] rio500 devfs support
Date: Mon, 25 Jun 2001 06:43:36 -0500 [thread overview]
Message-ID: <20010625064336.A9650@glitch.snoozer.net> (raw)
In-Reply-To: <20010619175224.A1137@glitch.snoozer.net> <20010624173711.A1764@glitch.snoozer.net> <200106250616.f5P6Gp710044@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200106250616.f5P6Gp710044@vindaloo.ras.ucalgary.ca>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
Ok, back to the original version then. Thanx!
On Mon, Jun 25, 2001 at 12:16:51AM -0600, Richard Gooch wrote:
> No, it's a bad idea to test the error from devfs_register() unless you
> *really* have a good reason. Most people who think they have a good
> reason actually don't, they're just confused :-)
>
> The reason you don't want to test the return value is that way the
> driver works fine with CONFIG_DEVFS=n. Otherwise, you have a driver
> that doesn't work with devfs, or you have to put ugly #ifdef's in the
> code.
>
> Regards,
>
> Richard....
> Permanent: rgooch@atnf.csiro.au
> Current: rgooch@ras.ucalgary.ca
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-06-25 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 22:52 Gregory T. Norris
2001-06-24 22:37 ` Gregory T. Norris
2001-06-25 6:16 ` Richard Gooch
2001-06-25 11:43 ` Gregory T. Norris [this message]
2001-06-25 17:35 ` Greg KH
2001-06-25 22:12 ` Gregory T. Norris
2001-06-26 5:07 ` Greg KH
2001-07-01 20:55 ` Gregory T. Norris
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=20010625064336.A9650@glitch.snoozer.net \
--to=haphazard@socket.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rio500-devel@lists.sourceforge.net \
/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®