From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Commit d3cfcb3 breaks beagle_x15 build
Date: Fri, 17 Apr 2015 18:05:49 +0530 [thread overview]
Message-ID: <5530FE25.1080607@ti.com> (raw)
In-Reply-To: <20150416105027.7833fe13@lilith>
Hi Albert,
On Thursday 16 April 2015 02:20 PM, Albert ARIBAUD wrote:
> Hello,
>
> Commit d3cfcb3 (ARM: DRA7: Enable clocks for USB OTGSS and USB PHY)
> breaks beagle_x15 build:
>
> Building current source for 1 boards (1 thread, 8 jobs per thread)
> arm: + beagle_x15
> +board/ti/beagle_x15/board.c: In function 'board_usb_init':
> +board/ti/beagle_x15/board.c:393:1: error: 'const struct prcm_regs' has no member named 'cm_l3init_usb_otg_ss_clkctrl'
> +make[2]: *** [board/ti/beagle_x15/board.o] Error 1
> +make[1]: *** [board/ti/beagle_x15] Error 2
> +make: *** [sub-make] Error 2
Thanks for pointing this. Kishon has sent a patch fixing this.
https://patchwork.ozlabs.org/patch/461734/
Thanks and regards,
Lokesh
>
> Cc:ing the committer and author.
>
> Kishon, can you look into this?
>
> Amicalement,
>
prev parent reply other threads:[~2015-04-17 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 8:50 [U-Boot] Commit d3cfcb3 breaks beagle_x15 build Albert ARIBAUD
2015-04-17 12:35 ` Lokesh Vutla [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=5530FE25.1080607@ti.com \
--to=lokeshvutla@ti.com \
--cc=u-boot@lists.denx.de \
/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