From: Linus Torvalds <torvalds@linux-foundation.org>
To: Russ Dill <russ.dill@gmail.com>
Cc: Greg KH <greg@kroah.com>, Alan Stern <stern@rowland.harvard.edu>,
Greg KH <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: [GIT PATCH] USB patches for 2.6.33-git
Date: Mon, 14 Dec 2009 20:44:33 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912142043180.14385@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0912142027440.14385@localhost.localdomain>
On Mon, 14 Dec 2009, Linus Torvalds wrote:
>
> Ok, this looks sane. I'll test it on the machine that had trouble.
Tests fine. I'd still like the trivial cleanup, but at least this confirms
that the problem was that the original patch matches the wrong device due
to not matching on the driver field.
Greg, do you want me to do this (revert+fixed patch), or are you going to
send me a pull request with it all sorted out?
Linus
next prev parent reply other threads:[~2009-12-15 4:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 21:26 Greg KH
2009-12-12 6:59 ` [build failure] " Ingo Molnar
2009-12-12 7:00 ` David Miller
2009-12-12 7:15 ` [PATCH] kaweth: Replace runtime power management primitives Ingo Molnar
2009-12-15 0:39 ` [GIT PATCH] USB patches for 2.6.33-git Linus Torvalds
2009-12-15 0:52 ` Greg KH
2009-12-15 1:00 ` Linus Torvalds
2009-12-15 1:47 ` Linus Torvalds
2009-12-15 2:29 ` Linus Torvalds
2009-12-15 3:09 ` Linus Torvalds
2009-12-15 3:17 ` russ.dill
2009-12-15 4:00 ` Russ Dill
2009-12-15 4:28 ` Linus Torvalds
2009-12-15 4:44 ` Linus Torvalds [this message]
2009-12-15 14:31 ` Greg KH
2009-12-15 4:36 ` Linus Torvalds
2009-12-15 4:45 ` Russ Dill
2009-12-15 6:02 ` Linus Torvalds
2009-12-15 6:11 ` Russ Dill
2009-12-15 6:20 ` Linus Torvalds
2010-03-02 23:09 Greg KH
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.LFD.2.00.0912142043180.14385@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=russ.dill@gmail.com \
--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®