From: Felipe Balbi <balbi@ti.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Dave Gerlach <d-gerlach@ti.com>, Paul Walmsley <paul@pwsan.com>,
Tony Lindgren <tony@atomide.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Regression with AM43xx devices
Date: Tue, 2 Jun 2015 14:23:32 -0500 [thread overview]
Message-ID: <20150602192332.GG9623@saruman.tx.rr.com> (raw)
In-Reply-To: <20150602191752.GE9623@saruman.tx.rr.com>
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
On Tue, Jun 02, 2015 at 02:17:52PM -0500, Felipe Balbi wrote:
> Hi Dave,
>
> You commit fabbe6df130a46d5b5e7484b2273d69c4be3012a (ARM: OMAP: AM43xx
> hwmod: Add data for am43xx emif hwmod) listed below added a new WARNING
> during boot to all AM43xx-based boards. Full boot logs can be found at
> [1], but it seems like we should, at least for the merge window, revert
> said commit unless a fix could come it the next couple days or so.o
>
> ps: note that boot log is for AM43xx IDK, but the same thing has been
> reproduced on AM437x SK.
>
> [1] http://hastebin.com/kasenikevo
Seems like someone forgot to pick [1] up. I've added my Tested-by as a
reply to that thread.
[1] http://marc.info/?l=linux-omap&m=143093317331247&w=2
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression with AM43xx devices
Date: Tue, 2 Jun 2015 14:23:32 -0500 [thread overview]
Message-ID: <20150602192332.GG9623@saruman.tx.rr.com> (raw)
In-Reply-To: <20150602191752.GE9623@saruman.tx.rr.com>
On Tue, Jun 02, 2015 at 02:17:52PM -0500, Felipe Balbi wrote:
> Hi Dave,
>
> You commit fabbe6df130a46d5b5e7484b2273d69c4be3012a (ARM: OMAP: AM43xx
> hwmod: Add data for am43xx emif hwmod) listed below added a new WARNING
> during boot to all AM43xx-based boards. Full boot logs can be found at
> [1], but it seems like we should, at least for the merge window, revert
> said commit unless a fix could come it the next couple days or so.o
>
> ps: note that boot log is for AM43xx IDK, but the same thing has been
> reproduced on AM437x SK.
>
> [1] http://hastebin.com/kasenikevo
Seems like someone forgot to pick [1] up. I've added my Tested-by as a
reply to that thread.
[1] http://marc.info/?l=linux-omap&m=143093317331247&w=2
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150602/a5c3dd2a/attachment-0001.sig>
next prev parent reply other threads:[~2015-06-02 19:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 19:17 Regression with AM43xx devices Felipe Balbi
2015-06-02 19:17 ` Felipe Balbi
2015-06-02 19:23 ` Felipe Balbi [this message]
2015-06-02 19:23 ` Felipe Balbi
2015-06-02 19:25 ` Dave Gerlach
2015-06-02 19:25 ` Dave Gerlach
2015-06-02 19:28 ` Paul Walmsley
2015-06-02 19:28 ` Paul Walmsley
2015-06-03 15:17 ` Dave Gerlach
2015-06-03 15:17 ` Dave Gerlach
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=20150602192332.GG9623@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=d-gerlach@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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.