From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
USB list <linux-usb@vger.kernel.org>,
David Lopo <dlopo@chipidea.mips.com>
Subject: Re: linux-next: Tree for Jun 18 usb/chipidea)
Date: Tue, 18 Jun 2013 11:52:36 -0700 [thread overview]
Message-ID: <51C0AC74.5050705@infradead.org> (raw)
In-Reply-To: <20130618173030.16d73801ab72b7c611faccea@canb.auug.org.au>
On 06/18/13 00:30, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130617:
>
on i386:
# CONFIG_USB_PHY is not set
drivers/built-in.o: In function `ci_hdrc_probe':
core.c:(.text+0x20446b): undefined reference to `of_usb_get_phy_mode'
chipidea needs to depend on or select some kind of USB_PHY support...?
--
~Randy
next prev parent reply other threads:[~2013-06-18 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 7:30 linux-next: Tree for Jun 18 Stephen Rothwell
2013-06-18 18:52 ` Randy Dunlap [this message]
2013-06-18 20:12 ` linux-next: Tree for Jun 18 usb/chipidea) Felipe Balbi
2013-06-19 1:35 ` Peter Chen
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=51C0AC74.5050705@infradead.org \
--to=rdunlap@infradead.org \
--cc=dlopo@chipidea.mips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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