From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: r8a73a4: Remove legacy code
Date: Wed, 25 Feb 2015 23:28:36 +0000 [thread overview]
Message-ID: <54EE5AA4.30004@cogentembedded.com> (raw)
In-Reply-To: <1418771008-5676-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On 02/26/2015 02:23 AM, Simon Horman wrote:
>>>> I saw it, too. But as renesas-devel-20150224-4.0-rc1 predates the email
>>>> from Simon, I assumed he just hasn't pushed out that version yet.
>>> BTW, does this tag work for anybody? I got the kernel hang with the blank
>>> console after the kernel decompression on the SILK board. After I enabled
>>> CONFIG_DEBUG_LL and early printk(), I saw that the PFC driver fails to load,
>>> all drivers dependent on the PFC driver failing the probes, and then the
>>> early console was disabled before I could see any crash report... I will
>>> provide the kernel log a bit later if anybody is interested...
>> Sure, my tree is based on that, and works on r8a73a4/ape6evm,
>> r8a7740/armadillo, r8a7791/koelsch, and sh73a0/kzm9g.
> FWIW I also tested the above tag on a range of boards.
Sorry about false alarm, it was all due to implementing Laurent's
suggestions in the PFC driver. :-) Looks like we both haven't properly tested
them... :-/
WBR, Sergei
prev parent reply other threads:[~2015-02-25 23:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 23:03 [PATCH] ARM: shmobile: r8a73a4: Remove legacy code Laurent Pinchart
2014-12-17 0:30 ` Simon Horman
2014-12-17 0:39 ` Laurent Pinchart
2015-02-19 17:48 ` Geert Uytterhoeven
2015-02-19 18:02 ` Simon Horman
2015-02-19 18:08 ` Simon Horman
2015-02-23 23:44 ` Simon Horman
2015-02-24 15:23 ` Laurent Pinchart
2015-02-24 15:30 ` Geert Uytterhoeven
2015-02-24 23:50 ` Simon Horman
2015-02-25 17:49 ` Sergei Shtylyov
2015-02-25 18:06 ` Geert Uytterhoeven
2015-02-25 23:23 ` Simon Horman
2015-02-25 23:28 ` Sergei Shtylyov [this message]
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=54EE5AA4.30004@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-sh@vger.kernel.org \
/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.