From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] pull request: u-boot-uniphier/master
Date: Sat, 2 Jul 2016 05:47:26 +0900 [thread overview]
Message-ID: <CAK7LNAQAkh5VoM5jeTc_SBjpgrxRfmPETszo+mNbtn7mam0G9Q@mail.gmail.com> (raw)
In-Reply-To: <CAK7LNATFo4rKArdoSvqUFK7pK6x_Z1U_6+5MPHxwKoxVtQ054Q@mail.gmail.com>
2016-07-01 0:08 GMT+09:00 Masahiro Yamada <yamada.masahiro@socionext.com>:
> Hi Tom,
>
> Here are some bug fixes + DT, pinctrl updates.
> It includes a little more than fixes, but it is
> self-contained for Uniphier SoCs and I tested this series on all of my
> boards. So, I hope it should be OK. (And another reason is just
> personal; I will travel from July 10th, at which the MW will open. I
> may have poor access to my PC for a while during the MW. So, I'd like
> to flush out my patches now.)
Sorry, I found a minor fix for a device tree.
Please let me do a second round.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2016-07-01 20:47 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 15:08 [U-Boot] pull request: u-boot-uniphier/master Masahiro Yamada
2016-07-01 20:47 ` Masahiro Yamada [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-21 17:08 Masahiro Yamada
2017-04-25 12:56 ` Tom Rini
2017-03-13 20:57 Masahiro Yamada
2017-03-16 20:39 ` Tom Rini
2017-02-23 2:03 Masahiro Yamada
2017-02-27 1:37 ` Tom Rini
2017-01-29 12:15 Masahiro Yamada
2017-01-29 17:39 ` Tom Rini
2017-01-22 12:55 Masahiro Yamada
2017-01-23 2:21 ` Tom Rini
2017-01-17 16:36 Masahiro Yamada
2017-01-18 2:56 ` Tom Rini
2016-12-11 9:04 Masahiro Yamada
2016-12-12 15:55 ` Tom Rini
2016-10-29 8:29 Masahiro Yamada
2016-10-30 12:11 ` Tom Rini
2016-10-18 16:00 Masahiro Yamada
2016-10-19 1:53 ` Tom Rini
2016-10-10 1:14 Masahiro Yamada
2016-10-13 0:48 ` Tom Rini
2016-09-22 16:03 Masahiro Yamada
2016-09-23 1:58 ` Tom Rini
2016-09-14 14:13 Masahiro Yamada
2016-09-15 8:40 ` Masahiro Yamada
2016-09-15 11:13 ` Tom Rini
2016-08-28 4:29 Masahiro Yamada
2016-08-29 12:02 ` Tom Rini
2016-08-11 13:16 Masahiro Yamada
2016-08-11 22:44 ` Tom Rini
2016-07-23 15:55 Masahiro Yamada
2016-07-24 0:20 ` Tom Rini
2016-06-19 22:27 Masahiro Yamada
2016-06-20 2:13 ` Tom Rini
2016-06-08 23:27 Masahiro Yamada
2016-06-09 18:02 ` Tom Rini
2016-05-25 15:52 Masahiro Yamada
2016-05-26 15:49 ` Tom Rini
2016-04-30 16:18 Masahiro Yamada
2016-05-02 23:31 ` Tom Rini
2016-04-24 1:04 Masahiro Yamada
2016-04-26 0:15 ` Tom Rini
2016-03-31 16:25 Masahiro Yamada
2016-04-01 17:00 ` Tom Rini
2016-03-23 16:56 Masahiro Yamada
2016-03-23 22:12 ` Tom Rini
2016-03-08 16:18 Masahiro Yamada
2016-03-08 19:59 ` Tom Rini
2016-02-28 19:03 Masahiro Yamada
2016-02-29 9:06 ` Masahiro Yamada
2016-02-29 14:10 ` Tom Rini
2016-02-14 8:54 Masahiro Yamada
2016-02-14 18:56 ` Tom Rini
2016-01-19 23:54 Masahiro Yamada
2016-01-20 1:41 ` Tom Rini
2016-01-12 17:05 Masahiro Yamada
2016-01-12 20:10 ` Tom Rini
2015-12-22 15:22 Masahiro Yamada
2015-12-22 15:59 ` Tom Rini
2015-12-23 2:00 ` Masahiro Yamada
2015-12-27 15:10 ` Tom Rini
2015-11-11 14:44 Masahiro Yamada
2015-11-11 14:55 ` Tom Rini
2015-09-23 14:32 [U-Boot] Pull " Masahiro Yamada
2015-09-24 12:17 ` Masahiro Yamada
2015-09-24 13:19 ` Tom Rini
2015-08-30 15:53 [U-Boot] pull " Masahiro Yamada
2015-08-30 16:07 ` Tom Rini
2015-07-23 14:49 Masahiro Yamada
2015-07-23 19:30 ` Tom Rini
2015-07-01 16:16 [U-Boot] Pull " Masahiro Yamada
2015-07-01 21:56 ` Tom Rini
2015-05-30 18:05 [U-Boot] pull " Masahiro Yamada
2015-06-02 12:54 ` Tom Rini
[not found] <CAMhH57TkcrHGxkjF9DcGmCc=PV+JaZV7bmG5T3QGrAEwEHB=BQ@mail.gmail.com>
2015-01-22 16:16 ` [U-Boot] Pull " Masahiro YAMADA
2015-01-23 21:56 ` Tom Rini
2014-11-27 17:33 Masahiro YAMADA
2014-12-01 20:23 ` Tom Rini
2014-11-11 15:46 Masahiro YAMADA
2014-11-11 20:49 ` Tom Rini
2014-10-29 14:00 Masahiro YAMADA
2014-11-04 2:33 ` Tom Rini
2014-10-05 5:32 Masahiro YAMADA
2014-10-07 10:09 ` Albert ARIBAUD
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=CAK7LNAQAkh5VoM5jeTc_SBjpgrxRfmPETszo+mNbtn7mam0G9Q@mail.gmail.com \
--to=yamada.masahiro@socionext.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.