From: Samuel Ortiz <sameo@linux.intel.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
Keshava Munegowda <keshava_mgowda@ti.com>
Subject: Re: omap-usb-tll build broken in linux next
Date: Sat, 22 Sep 2012 00:08:17 +0200 [thread overview]
Message-ID: <20120921220817.GZ28670@sortiz-mobl> (raw)
In-Reply-To: <20120920183442.GH28835@atomide.com>
Hi Tony,
On Thu, Sep 20, 2012 at 11:34:42AM -0700, Tony Lindgren wrote:
> Hi Keshava & Felipe,
>
> Looks like we have something broken in linux next:
>
> make[2]: *** No rule to make target `drivers/mfd/omap-usb-tll.o', needed by `drivers/mfd/built-in.o'. Stop.
>
> This is at least with my n8x0 config, see the attached file.
Thanks for the notification. Felipe was right, I forgot a git add...It should
be all fixed now.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-09-21 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 18:34 omap-usb-tll build broken in linux next Tony Lindgren
2012-09-20 19:29 ` Felipe Balbi
2012-09-21 22:08 ` Samuel Ortiz [this message]
2012-09-21 22:29 ` Tony Lindgren
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=20120921220817.GZ28670@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=balbi@ti.com \
--cc=keshava_mgowda@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).