From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PULL] Please pull u-boot-rockchip/master
Date: Fri, 1 Dec 2017 16:47:56 -0500 [thread overview]
Message-ID: <20171201214756.GU3587@bill-the-cat> (raw)
In-Reply-To: <6B6A56B0-EAAD-4137-B8A2-371F511AD81C@theobroma-systems.com>
On Fri, Dec 01, 2017 at 07:00:36PM +0100, Dr. Philipp Tomsich wrote:
> Tom,
>
> Another set of changes on u-boot-rockchip is ready for your tree.
> This includes support for the RK3128, documentation updates and convenience changes for some of our boards.
>
> Thanks,
> Philipp.
>
>
> The following changes since commit 9804d88630cdb22f5f0ace05ac05942928410fd9:
>
> Merge branch 'rmobile-mx' of git://git.denx.de/u-boot-sh (2017-11-30 10:39:04 -0500)
>
> are available in the git repository at:
>
> git://git.denx.de/u-boot-rockchip.git master
>
> for you to fetch changes up to 5f104178bf713615dc404fdfcf0fb53d89c66a07:
>
> rockchip: dts: rk3399-puma: add /config/sysreset-gpio property (2017-11-30 22:59:54 +0100)
>
NAK:
+(evb-rk3128) writel(((clr) | (set)) << 16 | (set), addr)
+(evb-rk3128) ^
+(evb-rk3128) ../drivers/clk/rockchip/clk_rk3128.c:234:2: note: in expansion of macro ?rk_clrsetreg?
+(evb-rk3128) rk_clrsetreg(&cru->cru_clksel_con[2],
+(evb-rk3128) ^~~~~~~~~~~~
+(evb-rk3128) ../drivers/clk/rockchip/clk_rk3128.c:445:3: note: in expansion of macro ?rk_clrsetreg?
+(evb-rk3128) rk_clrsetreg(&cru->cru_clksel_con[27],
+(evb-rk3128) ^~~~~~~~~~~~
w+(evb-rk3128) ../drivers/clk/rockchip/clk_rk3128.c: In function ?rkclk_init?:
w+(evb-rk3128) include/asm/arch/hardware.h:17:28: warning: result of ?122624 << 16? requires 34 bits to represent, but ?int? only has 32 bits [-Wshift-overflow=]
w+(evb-rk3128) ../drivers/clk/rockchip/clk_rk3128.c: In function ?rk3128_vop_set_clk?:
w+(evb-rk3128) include/asm/arch/hardware.h:17:28: warning: result of ?1048321 << 16? requires 37 bits to represent, but ?int? only has 32 bits [-Wshift-overflow=]
Please fix, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171201/692b0707/attachment.sig>
next prev parent reply other threads:[~2017-12-01 21:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 18:00 [U-Boot] [PULL] Please pull u-boot-rockchip/master Dr. Philipp Tomsich
2017-12-01 21:47 ` Tom Rini [this message]
2017-12-01 23:32 ` Dr. Philipp Tomsich
2017-12-02 2:59 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2018-07-21 0:00 Dr. Philipp Tomsich
2018-07-21 12:38 ` Tom Rini
2018-05-14 15:32 Dr. Philipp Tomsich
2018-05-14 15:33 ` Dr. Philipp Tomsich
2018-05-15 1:18 ` Tom Rini
2018-02-25 10:43 Dr. Philipp Tomsich
2018-02-26 3:28 ` Tom Rini
2018-02-26 5:05 ` Jonathan Gray
2018-01-03 17:07 Dr. Philipp Tomsich
2018-01-03 17:08 ` Dr. Philipp Tomsich
2018-01-04 1:10 ` Tom Rini
2018-01-01 13:50 Dr. Philipp Tomsich
2018-01-02 0:46 ` Tom Rini
2017-12-18 23:25 Dr. Philipp Tomsich
2017-12-19 1:56 ` Tom Rini
2017-11-26 20:42 Dr. Philipp Tomsich
2017-11-27 12:20 ` Tom Rini
2017-09-29 18:14 Dr. Philipp Tomsich
2017-09-29 22:22 ` Tom Rini
2017-09-08 10:15 Dr. Philipp Tomsich
2017-09-08 14:00 ` Tom Rini
2017-09-05 9:25 Dr. Philipp Tomsich
2017-09-06 0:35 ` Tom Rini
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=20171201214756.GU3587@bill-the-cat \
--to=trini@konsulko.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