public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah•com>
To: David Brownell <david-b@pacbell•net>
Cc: Randy Dunlap <randy.dunlap@oracle•com>,
	Stephen Rothwell <sfr@canb•auug.org.au>,
	linux-next@vger•kernel.org, lud <linux-usb@vger•kernel.org>
Subject: Re: linux-next: Tree for August 18 (usb gadget build error)
Date: Mon, 18 Aug 2008 16:00:56 -0700	[thread overview]
Message-ID: <20080818230056.GA26819@kroah.com> (raw)
In-Reply-To: <200808181555.33062.david-b@pacbell.net>

On Mon, Aug 18, 2008 at 03:55:32PM -0700, David Brownell wrote:
> On Monday 18 August 2008, Randy Dunlap wrote:
> > ERROR: "ecm_bind_config" [drivers/usb/gadget/g_cdc.ko] undefined!
> > 
> > config attached.
> 
> I'm guessing that's associate with Greg's patches to
> split the gadget drivers up into lots of little modules.
> 
> I'm really not keen on that, and I guess that means I'll
> have to send the alternate patches (even though I got no
> feedback from my posts on those topics).

Sorry, was off trying to enjoy a weekend :)

I just responded, and it looks like I'm going to drop those patches and
go with David's last patch/idea, hopefully -next tomorrow will be all
fixed up.

I'll post the patch series when I get everything building properly to
linux-usb for review.

thanks,

greg k-h

  reply	other threads:[~2008-08-18 23:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18  7:59 linux-next: Tree for August 18 Stephen Rothwell
2008-08-18 12:28 ` [BUILD-FAILURE] linux-next: Tree for August 18 - randconfig build fails at pnp_get_resource () Kamalesh Babulal
     [not found] ` <20080818175931.52d2b2d6.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-08-18 19:37   ` linux-next: Tree for August 18 (usb gadget build error) Randy Dunlap
2008-08-18 22:55     ` David Brownell
2008-08-18 23:00       ` Greg KH [this message]
2008-08-19  0:19         ` David Brownell

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=20080818230056.GA26819@kroah.com \
    --to=greg@kroah$(echo .)com \
    --cc=david-b@pacbell$(echo .)net \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-usb@vger$(echo .)kernel.org \
    --cc=randy.dunlap@oracle$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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