mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
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 22:07:01 -0700	[thread overview]
Message-ID: <20010625220701.A18827@kroah.com> (raw)
In-Reply-To: <20010619175224.A1137@glitch.snoozer.net> <20010625103521.A17036@kroah.com> <20010625171201.A13305@glitch.snoozer.net>
In-Reply-To: <20010625171201.A13305@glitch.snoozer.net>; from haphazard@socket.net on Mon, Jun 25, 2001 at 05:12:01PM -0500

On Mon, Jun 25, 2001 at 05:12:01PM -0500, Gregory T. Norris wrote:
> I was thinking of doing some similar updates this evening after work. 
> Darn it... now I have to find something else to do!  :-)
> 
> Going by this morning's comments from Richard Gooch, it sounds like the
> 
> 	if (rio->devfs == NULL)
> 		dbg("probe_rio: device node registration failed");

Just don't have it be using a call to "err()" like the printer.c file
does.  Loads of users wondering why they have an error message in their
logs, yet their printers still work.  That's why I made it dbg().

But yes, I agree that it doesn't have to be there at all.

greg k-h

  reply	other threads:[~2001-06-26  5:09 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
2001-06-25 17:35 ` Greg KH
2001-06-25 22:12   ` Gregory T. Norris
2001-06-26  5:07     ` Greg KH [this message]
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=20010625220701.A18827@kroah.com \
    --to=greg@kroah.com \
    --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®