mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Colin Leroy <colin@colino.net>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: don't spit out too much errors with suspended devices
Date: Thu, 28 Oct 2004 08:37:16 +0200	[thread overview]
Message-ID: <20041028083716.5ab62064.colin@colino.net> (raw)
In-Reply-To: <200410271613.56201.david-b@pacbell.net>

On 27 Oct 2004 at 16h10, David Brownell wrote:

Hi, 

> The "message.c" part is fine, but the usbfs/devio change
> only tests one of several paths for device access.  (My
> first whack at this only covered a different one!)  Can
> you verify this one instead?

I'll do; I'll get back to you next week probably, because
I'll be busy this week-end, and I'm avoiding 2.6.10-rc1 until
ppc fixes go in: Citing Benjamin Herrenschmidt:

> Well, I'd suggest not running that kernel until paul's signal fix gets
> in, there is a FP register corruption in there... There are other issues
> with 2.6.10 currently, so it's not really a good kernel to play with for
> now.

-- 
Colin

  reply	other threads:[~2004-10-28  6:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26 15:28 2.6.10-rc1 OHCI usb error messages Colin Leroy
2004-10-26 16:05 ` [linux-usb-devel] " David Brownell
2004-10-27  7:19   ` [PATCH] usb: don't spit out too much errors with suspended devices Colin Leroy
2004-10-27 23:13     ` David Brownell
2004-10-28  6:37       ` Colin Leroy [this message]
2004-10-27  9:07   ` [linux-usb-devel] 2.6.10-rc1 OHCI usb error messages Colin Leroy
2004-10-27 22:59     ` David Brownell
2004-10-28  9:07       ` Colin Leroy
2004-10-28 14:10         ` David Brownell
2004-10-28 14:46       ` Alan Stern
2004-10-28 16:51         ` David Brownell

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=20041028083716.5ab62064.colin@colino.net \
    --to=colin@colino.net \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-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®