From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull ARC changes
Date: Mon, 11 Dec 2017 20:55:33 -0500 [thread overview]
Message-ID: <20171212015533.GC372@bill-the-cat> (raw)
In-Reply-To: <1512981792.6183.5.camel@synopsys.com>
On Mon, Dec 11, 2017 at 08:43:12AM +0000, Alexey Brodkin wrote:
> Hi Tom,
>
> Seems like I'm a little bit late as RC1 was already cut but anyways
> I think most if not all the mentioned below changes could be safely pulled.
>
> That's because 5 of 6 patches are really just very trivial fixes
> (which I think is quite of for post-RC1 stage) and the only more significant
> change is HSDK clk driver. Still that patch was floated on the mailing list
> quite some time ago and shouldn't cause any troubles because it is by default
> is disabled, and essentially it all went through full TravisCI build so
> I don't expect any issues.
>
> Anyways if you prefer I may exclude HSDK clk driver from this pull-request and
> resend it shortly.
>
> The following changes since commit 335f7b1290ce24a729a9689a1db834c743226ca8:
>
> Merge git://git.denx.de/u-boot-mpc85xx (2017-12-08 12:02:01 -0500)
>
> are available in the git repository at:
>
> git://git.denx.de/u-boot-arc.git
>
> for you to fetch changes up to e80dac0ab83ccb1d54e2d91b93d27b54a7f6544f:
>
> ARC: clk: introduce HSDK CGU clock driver (2017-12-11 11:36:23 +0300)
>
Applied to u-boot/master, 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/20171211/7ec91ca5/attachment.sig>
next prev parent reply other threads:[~2017-12-12 1:55 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 8:43 [U-Boot] Please pull ARC changes Alexey Brodkin
2017-12-12 1:55 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-25 5:52 Alexey Brodkin
2019-01-27 3:50 ` Tom Rini
2018-12-03 11:32 Alexey Brodkin
2018-12-03 15:32 ` Tom Rini
2018-11-01 20:41 Alexey Brodkin
2018-11-02 20:30 ` Tom Rini
2018-10-15 10:22 Alexey Brodkin
2018-10-12 12:38 Alexey Brodkin
2018-10-05 14:10 Alexey Brodkin
2018-10-06 1:16 ` Tom Rini
2018-06-21 11:59 Alexey Brodkin
2018-06-21 18:21 ` Tom Rini
2018-06-18 9:29 Alexey Brodkin
2018-06-15 13:14 Alexey Brodkin
2018-06-16 2:34 ` Tom Rini
2018-05-24 13:09 Alexey Brodkin
2018-05-24 23:41 ` Tom Rini
2018-03-23 13:23 Alexey Brodkin
2018-03-23 13:33 ` Tom Rini
2018-03-23 13:38 ` Alexey Brodkin
2018-03-23 13:51 ` Tom Rini
2018-02-15 12:53 Alexey Brodkin
2018-02-15 19:07 ` Tom Rini
2018-01-19 15:08 Alexey Brodkin
2018-01-19 15:08 ` Alexey Brodkin
2018-01-19 21:11 ` Tom Rini
2018-01-19 21:11 ` Tom Rini
2017-12-12 15:52 Alexey Brodkin
2017-12-12 15:52 ` Alexey Brodkin
2017-12-12 15:58 ` Tom Rini
2017-12-12 15:58 ` Tom Rini
2017-11-24 16:39 Alexey Brodkin
2017-11-24 21:33 ` Tom Rini
2017-06-29 16:39 Alexey Brodkin
2017-06-30 1:26 ` Tom Rini
2017-04-11 14:56 Alexey Brodkin
2017-04-11 15:55 ` Tom Rini
2017-03-31 19:12 Alexey Brodkin
2017-04-04 20:00 ` Tom Rini
2017-03-24 11:53 Alexey Brodkin
2017-03-24 17:37 ` Tom Rini
2016-09-16 11:30 Alexey Brodkin
2016-09-19 0:31 ` Tom Rini
2016-08-05 10:09 Alexey Brodkin
2016-08-06 2:09 ` Tom Rini
2016-07-04 8:49 Alexey Brodkin
2016-07-05 2:44 ` Tom Rini
2016-06-13 12:43 Alexey Brodkin
2016-06-19 14:08 ` Tom Rini
2016-04-21 17:11 Alexey Brodkin
2016-04-22 14:26 ` Tom Rini
2016-04-11 17:23 Alexey Brodkin
2016-04-12 2:27 ` Tom Rini
2016-02-20 8:22 Alexey Brodkin
2016-02-20 14:23 ` Tom Rini
2015-12-08 14:33 Alexey Brodkin
2015-12-08 15:00 ` Tom Rini
2015-11-17 21:41 Alexey Brodkin
2015-11-18 0:50 ` 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=20171212015533.GC372@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 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.