All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@nokia.com>
To: "ext Krishnamoorthy, Balaji T" <balajitk@ti.com>
Cc: "Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: commit fc7b92fca4e546184557f1c53f84ad57c66b7695 broke compilation
Date: Tue, 15 Dec 2009 14:15:39 +0200	[thread overview]
Message-ID: <20091215121539.GI3689@nokia.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E739404372AAF22@dbde02.ent.ti.com>

On Tue, Dec 15, 2009 at 01:05:01PM +0100, ext Krishnamoorthy, Balaji T wrote:
>> -----Original Message-----
>> From: Felipe Balbi [mailto:felipe.balbi@nokia.com]
>> Sent: Tuesday, December 15, 2009 5:28 PM
>> To: Linux OMAP Mailing List
>> Cc: Krishnamoorthy, Balaji T
>> Subject: commit fc7b92fca4e546184557f1c53f84ad57c66b7695 broke compilation
>>
>> Hi,
>>
>> the patch renaming twl4030 to twl broke compilation of several omap
>> boards.
>>
>> Here are all the files including a file that doesn't exist anymore:
>>
>Thanks Felipe,
>I am preparing a patch for this.

please, compile test with all omap3 defconfigs to be sure.

something like:

for i in `ls arch/arm/configs | grep omap | grep -v 'omap-l137'`; do
	make CROSS_COMPILE=arm-linux- ARCH=arm $i defconfig;
	make CROSS_COMPILE=arm-linux- ARCH=arm;
done

this won't get rx51_defconfig or n8x0_deconfig nor n770_defconfig, but 
it's good enough. rx51_defconfig is the only of those three that twl4030 
anyways.

-- 
balbi

      reply	other threads:[~2009-12-15 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 11:58 commit fc7b92fca4e546184557f1c53f84ad57c66b7695 broke compilation Felipe Balbi
2009-12-15 12:05 ` Krishnamoorthy, Balaji T
2009-12-15 12:15   ` Felipe Balbi [this message]

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=20091215121539.GI3689@nokia.com \
    --to=felipe.balbi@nokia.com \
    --cc=balajitk@ti.com \
    --cc=linux-omap@vger.kernel.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.