From: Greg KH <greg@kroah.com>
To: Luis Miguel Garc?a Mancebo <ktech@wanadoo.es>
Cc: LKML <linux-kernel@vger.kernel.org>,
akpm@osdl.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: USB troubles in rc2
Date: Mon, 2 Aug 2004 17:26:34 -0700 [thread overview]
Message-ID: <20040803002634.GB26323@kroah.com> (raw)
In-Reply-To: <200408022100.54850.ktech@wanadoo.es>
On Mon, Aug 02, 2004 at 09:00:54PM +0200, Luis Miguel Garc?a Mancebo wrote:
> Hello,
>
> I have a nforce2 motherboard. I have to report that recent changes in usb
> code make my board don't work at all.
>
> In 2.6.7-mm7, I just reverted the bk-usb.patch and the things started to
> work, but now it's on mainstream, so I cannot make it work.
>
> Do you want for me to do some tests?
Yes please. What exactly "does not work"?
Also, let's cc: the linux-usb-devel mailing list to try to help out
here...
thanks,
greg k-h
next prev parent reply other threads:[~2004-08-03 0:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 19:00 USB troubles in rc2 Luis Miguel García Mancebo
2004-08-03 0:26 ` Greg KH [this message]
2004-08-03 2:08 ` Michael Guterl
2004-08-03 6:49 ` Trever L. Adams
2004-08-03 8:46 ` Luis Miguel García Mancebo
2004-08-03 13:57 ` Greg KH
2004-08-03 23:04 ` Luis Miguel García Mancebo
2004-08-04 20:32 ` Michael Guterl
2004-08-05 1:20 ` [linux-usb-devel] " David Brownell
2004-08-05 3:57 ` Michael Guterl
2004-08-05 15:34 ` David Brownell
2004-08-05 17:05 ` Michael Guterl
2004-08-07 17:51 ` David Brownell
2004-08-07 22:01 ` Wes Janzen
2004-08-08 3:19 ` Michael Guterl
2004-08-08 4:20 ` Alan Stern
2004-08-08 13:29 ` Michael Guterl
2004-08-10 17:16 ` Michael Guterl
2004-08-10 18:54 ` Alan Stern
2004-08-10 19:41 ` Michael Guterl
2004-08-05 18:08 ` Kevin O'Shea
2004-08-05 18:50 ` Michael Guterl
2004-08-06 14:23 ` Alan Stern
2004-08-05 3:59 ` Michael Guterl
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=20040803002634.GB26323@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=ktech@wanadoo.es \
--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