From: Greg KH <gregkh@suse.de>
To: Aras Vaichas <arasv@magellan-technology.com>
Cc: Mihai Don??u <mihai.dontu@gmail.com>,
"Gadiyar, Anand" <gadiyar@ti.com>,
Maxim Osipov <maxim.osipov@gmail.com>,
Sergei Shtylyov <sshtylyov@mvista.com>,
David Brownell <dbrownell@users.sourceforge.net>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: Fix kernel oops with g_ether and Windows
Date: Wed, 12 Oct 2011 18:12:02 -0600 [thread overview]
Message-ID: <20111013001202.GB19446@suse.de> (raw)
In-Reply-To: <CAPs5rNZ07VZ0qK2PVG2u1DLEEnXS_CvVcYGLLE7fzFCcMo696A@mail.gmail.com>
On Thu, Oct 13, 2011 at 10:31:08AM +1100, Aras Vaichas wrote:
> On 8 September 2010 10:34, Greg KH <gregkh@suse.de> wrote:
You are responding to a message from over a year ago?
> > On Wed, Sep 08, 2010 at 02:54:02AM +0300, Mihai Don??u wrote:
> > > On Wednesday 08 September 2010 00:29:15 Greg KH wrote:
> > > > On Tue, Sep 07, 2010 at 04:18:23PM +0530, Gadiyar, Anand wrote:
> > > > > Since Greg has already sent a pull request, I won't touch the file
> > > > > now; maybe a trivial patch later on to fix up the coding style.
> > > >
> > > > That would be fine to have, I'd gladly accept it.
> > >
> > > Would something like the following do? It's against:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6.git
> > >
> > > Corrected the coding style.
> >
> > Looks good, thanks, I'll go queue it up.
>
> Did this patch get applied and the problem resolved?
Probably, I'd suggest you take a look at the kernel sources to verify
this, I can't remember what was applied last week very well, let alone
last year.
> I'm running 2.6.33.7-rt29 and we have a customer in India who
> complains that they can't connect via USB. We don't have the problem
> here, or anywhere else that we know of.
>
> I looked at the logs of the device and it appears to have the same
> Oops error as the one that this patch addresses.
What kernel version are they using? Hopefully something newer than the
date of this original email :)
greg k-h
next prev parent reply other threads:[~2011-10-13 0:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 10:54 [PATCH] USB: Fix kernel oops with g_ether and Windows Maxim Osipov
2010-08-21 13:27 ` Sergei Shtylyov
2010-09-06 14:37 ` Gadiyar, Anand
2010-09-06 20:18 ` Greg KH
2010-09-07 9:55 ` Sergei Shtylyov
2010-09-07 10:12 ` Maxim Osipov
2010-09-07 10:48 ` Gadiyar, Anand
2010-09-07 21:29 ` Greg KH
2010-09-07 23:54 ` Mihai Donțu
2010-09-08 0:34 ` Greg KH
2011-10-12 23:31 ` Aras Vaichas
2011-10-13 0:12 ` Greg KH [this message]
2011-10-13 0:46 ` Aras Vaichas
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=20111013001202.GB19446@suse.de \
--to=gregkh@suse.de \
--cc=arasv@magellan-technology.com \
--cc=dbrownell@users.sourceforge.net \
--cc=gadiyar@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=maxim.osipov@gmail.com \
--cc=mihai.dontu@gmail.com \
--cc=sshtylyov@mvista.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.