From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
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 18:46:23 +0200 [thread overview]
Message-ID: <20160825164623.GI2856@katana> (raw)
In-Reply-To: <CAMuHMdUneaDwC2yMOkcfNQy2f47dTdOoxr=YyZX6VPmZW0kBQg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
> > 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)?
>
> It's part of my topic/renesas-debug branch. Just merge that into latest
> renesas-drivers and see...
I second Magnus in wanting this upstream. The FIXMEs are about the
cache. Maybe submit an initial version without cache report first? Or
are there other issues? It would be really helpful to have this in the
bootlogs by default, I'd say.
Thanks,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-25 17:39 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 ` renesas-drivers-2016-08-23-v4.8-rc3 Magnus Damm
2016-08-25 7:46 ` renesas-drivers-2016-08-23-v4.8-rc3 Geert Uytterhoeven
2016-08-25 16:46 ` Wolfram Sang [this message]
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=20160825164623.GI2856@katana \
--to=wsa@the-dreams.de \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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.