All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: David Rientjes <rientjes@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch for-3.8-rc8] usb, chipidea: fix link error when USB_EHCI_HCD is a module
Date: Fri, 26 Apr 2013 13:33:45 -0700	[thread overview]
Message-ID: <20130426203345.GA25959@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1304261323060.17754@chino.kir.corp.google.com>

I think you mean "3.9" in your subject: right?

On Fri, Apr 26, 2013 at 01:25:01PM -0700, David Rientjes wrote:
> Fixes link error when USB_EHCI_HCD=m and USB_CHIPIDEA_HOST=y:
> 
> 	drivers/built-in.o: In function `ci_hdrc_host_init':
> 	drivers/usb/chipidea/host.c:104: undefined reference to `ehci_init_driver'
> 
> as a result of commit 09f6ffde2ece ("USB: EHCI: fix build error by making
> ChipIdea host a normal EHCI driver").
> 
> Cc: stable@vger.kernel.org [v3.7+]
> Signed-off-by: David Rientjes <rientjes@google.com>
> ---
>  drivers/usb/chipidea/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

There have been a ton of chipidea changes recently in linux-next.  This
really just looks like you got the configuration wrong, nothing that is
needed at this point in the release cycle, right?

thanks,

greg k-h

  reply	other threads:[~2013-04-26 20:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 20:25 [patch for-3.8-rc8] usb, chipidea: fix link error when USB_EHCI_HCD is a module David Rientjes
2013-04-26 20:33 ` Greg Kroah-Hartman [this message]
2013-04-26 21:50   ` David Rientjes
2013-04-26 22:00     ` Greg Kroah-Hartman
2013-04-26 22:14       ` David Rientjes

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=20130426203345.GA25959@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rientjes@google.com \
    --cc=stern@rowland.harvard.edu \
    --cc=torvalds@linux-foundation.org \
    /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.