All of lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Wolfram Sang <wsa@the-dreams.de>, Simon <horms@verge.net.au>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: renesas-drivers-2016-08-23-v4.8-rc3
Date: Thu, 25 Aug 2016 11:42:25 +0900	[thread overview]
Message-ID: <CANqRtoRCoe6-f3ekkvvTsX5co5kj8ZTzUpgfXL8LAHqp6c7=og@mail.gmail.com> (raw)
In-Reply-To: <874m6buh17.wl%kuninori.morimoto.gx@renesas.com>

Hi Morimoto-san, everyone,

On Wed, Aug 24, 2016 at 9:58 AM, Kuninori Morimoto
<kuninori.morimoto.gx@renesas.com> wrote:
>
> Hi Geert, Simon, Wolfram
>
>> I have pushed renesas-drivers-2016-08-23-v4.8-rc3 to
>> https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git
>>
>> This tree is meant to ease development of platform support and drivers
>> for Renesas ARM SoCs. It is created by merging (a) the for-next branches
>> of various subsystem trees and (b) branches with driver code submitted
>> or planned for submission to maintainers into the development branch of
>> Simon Horman's renesas.git tree.
>>
>> Today's version is based on renesas-devel-20160823-v4.8-rc3.
>
> I noticed that Lager "ES3.0" board can't boot on this and previous -rc2 branch.
> In my and Shimoda-san's check, "ES2.0" seems have no problem.
>
> It start works if I reverted this patch.
>
>         09a28bb8b17e8cab3e9c120b7e37f631cc334a8f
>         ("ARM: dts: lager: use demuxer for IIC3/I2C3")
>

FYI, I have now received the problematic Lager ES3 board from
Morimoto-san and I will install it for remote access.

How can we check which ES version we are running? I recall seeing some
patch from Geert that printed out useful information during boot, any
chance that could make it upstream (if it is not already)?

Cheers,

/ magnus

  parent reply	other threads:[~2016-08-25  4:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 13:35 renesas-drivers-2016-08-23-v4.8-rc3 Geert Uytterhoeven
2016-08-24  0:58 ` renesas-drivers-2016-08-23-v4.8-rc3 Kuninori Morimoto
2016-08-24  6:15   ` renesas-drivers-2016-08-23-v4.8-rc3 Wolfram Sang
2016-08-24  6:20     ` renesas-drivers-2016-08-23-v4.8-rc3 Kuninori Morimoto
2016-08-24  6:28       ` renesas-drivers-2016-08-23-v4.8-rc3 Wolfram Sang
2016-08-25  2:24         ` renesas-drivers-2016-08-23-v4.8-rc3 Kuninori Morimoto
2016-08-25  2:42   ` Magnus Damm [this message]
2016-08-25  7:46     ` renesas-drivers-2016-08-23-v4.8-rc3 Geert Uytterhoeven
2016-08-25 16:46       ` renesas-drivers-2016-08-23-v4.8-rc3 Wolfram Sang
2016-09-06 13:18         ` renesas-drivers-2016-08-23-v4.8-rc3 Geert Uytterhoeven
2016-08-30 11:24   ` renesas-drivers-2016-08-23-v4.8-rc3 Wolfram Sang
2016-08-31  6:20     ` renesas-drivers-2016-08-23-v4.8-rc3 Kuninori Morimoto
2016-08-31  7:44       ` renesas-drivers-2016-08-23-v4.8-rc3 Geert Uytterhoeven
2016-08-31  8:07         ` renesas-drivers-2016-08-23-v4.8-rc3 Wolfram Sang
2016-08-31  8:12           ` renesas-drivers-2016-08-23-v4.8-rc3 Geert Uytterhoeven
2016-09-01  0:53         ` renesas-drivers-2016-08-23-v4.8-rc3 Kuninori Morimoto
2016-09-01  5:50           ` renesas-drivers-2016-08-23-v4.8-rc3 Wolfram Sang
2016-09-01  7:06             ` renesas-drivers-2016-08-23-v4.8-rc3 Kuninori Morimoto
2016-09-01  7:26               ` renesas-drivers-2016-08-23-v4.8-rc3 Geert Uytterhoeven
2016-09-02  1:38                 ` renesas-drivers-2016-08-23-v4.8-rc3 Kuninori Morimoto
2016-09-02  8:10                   ` renesas-drivers-2016-08-23-v4.8-rc3 Geert Uytterhoeven

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='CANqRtoRCoe6-f3ekkvvTsX5co5kj8ZTzUpgfXL8LAHqp6c7=og@mail.gmail.com' \
    --to=magnus.damm@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa@the-dreams.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.