From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Heikki Krogerus <ext-heikki.krogerus@nokia.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the final tree (usb tree related)
Date: Mon, 3 May 2010 11:02:57 -0700 [thread overview]
Message-ID: <20100503180257.GA5901@kroah.com> (raw)
In-Reply-To: <20100503173501.GA11567@kroah.com>
On Mon, May 03, 2010 at 10:35:01AM -0700, Greg KH wrote:
> On Mon, May 03, 2010 at 10:13:48AM -0700, Greg KH wrote:
> > On Mon, May 03, 2010 at 02:57:15PM +1000, Stephen Rothwell wrote:
> > > Hi Guys,
> > >
> > > On Fri, 30 Apr 2010 09:22:24 +0300 Heikki Krogerus <ext-heikki.krogerus@nokia.com> wrote:
> > > >
> > > > On Fri, Apr 30, 2010 at 08:05:55AM +0200, ext Stephen Rothwell wrote:
> > > > >
> > > > > After merging the final tree, today's linux-next build (powerpc
> > > > > allyesconfig) failed like this:
> > > > >
> > > > > drivers/usb/otg/twl4030-usb.c: In function 'twl4030_usb_set_bits':
> > > > > drivers/usb/otg/twl4030-usb.c:238: error: implicit declaration of function 'ULPI_SET'
> > > > > drivers/usb/otg/twl4030-usb.c: In function 'twl4030_usb_clear_bits':
> > > > > drivers/usb/otg/twl4030-usb.c:244: error: implicit declaration of function 'ULPI_CLR'
> > > > > drivers/usb/otg/twl4030-usb.c: In function 'twl4030_usb_set_mode':
> > > > > drivers/usb/otg/twl4030-usb.c:303: error: 'ULPI_IFC_CTRL' undeclared (first use in this function)
> > > > > drivers/usb/otg/twl4030-usb.c:304: error: 'ULPI_IFC_CTRL_CARKITMODE' undeclared (first use in this function)
> > > > > drivers/usb/otg/twl4030-usb.c:306: error: 'ULPI_FUNC_CTRL' undeclared (first use in this function)
> > > > > drivers/usb/otg/twl4030-usb.c:307: error: 'ULPI_FUNC_CTRL_XCVRSEL_MASK' undeclared (first use in this function)
> > > > > drivers/usb/otg/twl4030-usb.c:308: error: 'ULPI_FUNC_CTRL_OPMODE_MASK' undeclared (first use in this function)
> > > > >
> > > > > Caused by commit 57983872ff14cba23d6404a40c89e52063c94854 ("usb: otg:
> > > > > twl4030: use the global ULPI register definitions"). I have reverted
> > > > > that commit for today.
> > > >
> > > > Already informed Greg that he needs the patch for the global ulpi
> > > > registers before this one.
> > >
> > > Still got this one today.
> >
> > Yes, I need the patch from Heikki... {hint...}
>
> Oh nevermind, I see them now, stupid me. I'll go queue them up.
This should now be resolved.
thanks,
greg k-h
next prev parent reply other threads:[~2010-05-03 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 6:05 linux-next: build failure after merge of the final tree (usb tree related) Stephen Rothwell
2010-04-30 6:22 ` Heikki Krogerus
2010-05-03 4:57 ` Stephen Rothwell
2010-05-03 17:13 ` Greg KH
2010-05-03 17:35 ` Greg KH
2010-05-03 18:02 ` Greg KH [this message]
2010-05-03 22:40 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2010-06-17 4:53 Stephen Rothwell
2010-06-17 17:25 ` Greg KH
2010-06-17 22:34 ` Stephen Rothwell
2012-10-23 4:13 Stephen Rothwell
2012-10-23 4:22 ` Greg KH
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=20100503180257.GA5901@kroah.com \
--to=greg@kroah.com \
--cc=ext-heikki.krogerus@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).