From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
Alan Piszcz <ap@solarrain.com>
Subject: Re: 2.6.33: Xorg+khubd lockup (D-state) BUG / ioctl EVIOCGNAME failed: Inappropriate ioctl for device / PreInit returned NULL
Date: Mon, 29 Mar 2010 14:44:11 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1003291443330.10153@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1003291253410.3358-100000@iolanthe.rowland.org>
On Mon, 29 Mar 2010, Alan Stern wrote:
> On Mon, 29 Mar 2010, Justin Piszcz wrote:
>
> Yes it does. Maybe there's something wrong with the way your email
> client extracted the patch from the message.
You're correct, sorry about that, when it recurs and I have the usbmon
trace output I will send it along.
>
>> It also fails against 2.6.34-rc2, can you diff -u and show the patch so
>> I can patch manually or include a patch against 2.6.33 or 2.6.34-rc2?
>
> That _was_ a "diff -u"-style patch.
>
> Alan Stern
>
next prev parent reply other threads:[~2010-03-29 18:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 12:29 Justin Piszcz
2010-03-25 12:35 ` Justin Piszcz
2010-03-25 13:40 ` Justin Piszcz
2010-03-25 14:17 ` Alan Stern
2010-03-25 14:47 ` Justin Piszcz
2010-03-25 15:53 ` Alan Stern
2010-03-25 16:45 ` Justin Piszcz
2010-03-25 21:02 ` Alan Stern
2010-03-25 21:14 ` Michael Tokarev
2010-03-29 11:45 ` Justin Piszcz
2010-03-29 15:33 ` Alan Stern
2010-03-29 16:26 ` Justin Piszcz
2010-03-29 16:38 ` Justin Piszcz
2010-03-29 16:58 ` Alan Stern
2010-03-29 18:44 ` Justin Piszcz [this message]
2010-03-30 12:58 ` Justin Piszcz
2010-03-30 17:40 ` Alan Stern
2010-03-30 18:02 ` Justin Piszcz
2010-03-30 23:19 ` Tiago Vignatti
2010-03-31 11:08 ` Justin Piszcz
2010-03-31 18:25 ` Justin Piszcz
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=alpine.DEB.2.00.1003291443330.10153@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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®