public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Dan Carpenter <error27@gmail.com>,
	Andy Whitcroft <apw@canonical.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: Wed, 3 Nov 2010 12:18:54 -0700	[thread overview]
Message-ID: <20101103191854.GA9894@suse.de> (raw)
In-Reply-To: <20101103191238.GI14069@bicker>

On Wed, Nov 03, 2010 at 09:12:38PM +0200, Dan Carpenter wrote:
> 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?
> > 
> 
> Yes.  This was my fault.  I forgot to send you that part of the patch.
> 
> Acked-by: Dan Carpenter <error27@gmail.com>

Thanks for the quick response, I'll queue this up.

greg k-h

  reply	other threads:[~2010-11-03 19:22 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 [this message]
2010-11-09 20:27   ` Andy Whitcroft

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=20101103191854.GA9894@suse.de \
    --to=gregkh@suse.de \
    --cc=apw@canonical.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=error27@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox