From: Nishanth Menon <nm@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Kevin Hilman <khilman@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
"tony@atomide.com" <tony@atomide.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>,
linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like)
Date: Tue, 23 Dec 2014 10:05:24 -0600 [thread overview]
Message-ID: <549992C4.7000603@ti.com> (raw)
In-Reply-To: <20141223111045.GN11502@n2100.arm.linux.org.uk>
On 12/23/2014 05:10 AM, Russell King - ARM Linux wrote:
> On Tue, Dec 23, 2014 at 12:00:00PM +0100, Marek Szyprowski wrote:
>> I hope I did it right: https://lkml.org/lkml/2014/12/23/158
>> Please test, because I have no access to Omap hardware.
>
> Patch 1/8 looks like I'd expect it to. Nishanth, please test with your
> failing scenario, thanks.
>
3.19-rc1
1: am437x-sk: BOOT: PASS:
http://slexy.org/raw/s2ARFeCcDp
2: am43xx-epos: BOOT: PASS:
http://slexy.org/raw/s2Kzli0GYS
3: am43xx-gpevm: BOOT: PASS:
http://slexy.org/raw/s2DMkJGmdF
4: pandaboard-es: BOOT: PASS:
http://slexy.org/raw/s204jfptrr
5: pandaboard-vanilla: BOOT: PASS:
http://slexy.org/raw/s2cbd82pMI
6: sdp4430: BOOT: PASS:
http://slexy.org/raw/s21bzlzUNr
TOTAL = 6 boards, Booted Boards = 6, No Boot boards = 0
against the patch series: (all am437x platforms fail)
testing
1: am437x-sk: BOOT: FAIL:
http://slexy.org/raw/s2yhDXyF7o
2: am43xx-epos: BOOT: FAIL:
http://slexy.org/raw/s2m9cSdt55
3: am43xx-gpevm: BOOT: FAIL:
http://slexy.org/raw/s2MqFFBuIl
4: pandaboard-es: BOOT: PASS:
http://slexy.org/raw/s2XwggyB0a
5: pandaboard-vanilla: BOOT: PASS:
http://slexy.org/raw/s25WDvtbob
6: sdp4430: BOOT: PASS:
http://slexy.org/raw/s2gjynR1Co
TOTAL = 6 boards, Booted Boards = 3, No Boot boards = 3
I am trying to understand what is different in AM437x except that it
is a single A9 instead of OMAP4 style dual A9s.
--
Regards,
Nishanth Menon
prev parent reply other threads:[~2014-12-23 16:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 16:10 regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like) Nishanth Menon
2014-12-05 16:13 ` Nishanth Menon
2014-12-05 16:23 ` Russell King - ARM Linux
2014-12-08 11:54 ` Tomasz Figa
2014-12-08 12:22 ` Russell King - ARM Linux
2014-12-08 13:54 ` Nishanth Menon
2014-12-08 15:11 ` Russell King - ARM Linux
2014-12-09 16:57 ` Nishanth Menon
2014-12-10 9:42 ` Marek Szyprowski
2014-12-11 9:29 ` Russell King - ARM Linux
2014-12-11 10:42 ` Marek Szyprowski
2014-12-22 17:04 ` Russell King - ARM Linux
2014-12-22 17:08 ` Tony Lindgren
2014-12-22 17:12 ` Nishanth Menon
2014-12-22 17:28 ` Russell King - ARM Linux
2014-12-23 11:00 ` Marek Szyprowski
2014-12-23 11:10 ` Russell King - ARM Linux
2014-12-23 16:05 ` Nishanth Menon [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=549992C4.7000603@ti.com \
--to=nm@ti.com \
--cc=arnd@arndb.de \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=tomasz.figa@gmail.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 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).