From: Andy Whitcroft <apw@canonical.com>
To: Greg KH <gregkh@suse.de>
Cc: Dan Carpenter <error27@gmail.com>,
Rahul Ruikar <rahul.ruikar@gmail.com>,
David Brownell <dbrownell@users.sourceforge.net>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] usb: gadget: goku_udc: add registered flag bit
Date: Tue, 9 Nov 2010 15:27:55 -0500 [thread overview]
Message-ID: <20101109202755.GC1984@penfold> (raw)
In-Reply-To: <20101103182314.GA8010@suse.de>
On Wed, Nov 03, 2010 at 11:23:14AM -0700, Greg KH wrote:
> On Wed, Nov 03, 2010 at 06:02:38PM +0000, Andy Whitcroft wrote:
> > The commit below cleaned up error handling, in part by introducing a
> > registered flag bit. This however was not added to the device
> > structure leding to build failures:
> >
> > commit 319feaabb6c7ccd90da6e3207563c265da7d21ae
> > Author: Dan Carpenter <error27@gmail.com>
> > Date: Tue Oct 5 18:55:34 2010 +0200
> >
> > usb: gadget: goku_udc: Fix error path
> >
> > Add the missing registered flag bit.
>
>
> Dan, is this patch below the correct fix? Or should we be looking at
> some other flag?
>
> [Andy, please always cc: the original patch author when reporting
> problems, to not do so is a bit rude and causes others (i.e. me) extra
> work.]
Appologies. I thought I used get_maintainers which I thought pulled in
the recent committers. More care next time.
-apw
prev parent reply other threads:[~2010-11-09 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 18:02 [PATCH 1/1] usb: gadget: goku_udc: add registered flag bit Andy Whitcroft
2010-11-03 18:23 ` Greg KH
2010-11-03 19:12 ` Dan Carpenter
2010-11-03 19:18 ` Greg KH
2010-11-09 20:27 ` Andy Whitcroft [this message]
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=20101109202755.GC1984@penfold \
--to=apw@canonical.com \
--cc=dbrownell@users.sourceforge.net \
--cc=error27@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rahul.ruikar@gmail.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.