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 17:49:05 +0000 [thread overview]
Message-ID: <54EE0B11.9030100@cogentembedded.com> (raw)
In-Reply-To: <1418771008-5676-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hello.
On 02/24/2015 06:30 PM, Geert Uytterhoeven wrote:
>>> The mmc problems seem to be resolved in v4.0-rc1 and I have queued
>>> this patch up as part of rebasing renesas-devel/next on top of that rc
>>> release.
>> I can't find the patch in your next or devel branches. Am I looking at the
>> wrong tree ?
> 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...
> Gr{oetje,eeting}s,
> Geert
WBR, Sergei
next prev parent reply other threads:[~2015-02-25 17:49 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 [this message]
2015-02-25 18:06 ` Geert Uytterhoeven
2015-02-25 23:23 ` Simon Horman
2015-02-25 23:28 ` Sergei Shtylyov
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=54EE0B11.9030100@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).