From: Sachin Kamat <spk.linux@gmail.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Laura Abbott <lauraa@codeaurora.org>,
Tushar Behera <trblinux@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Kevin Hilman <khilman@linaro.org>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robherring2@gmail.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [RESEND][PATCHv2 0/3] Fix for buggy u-boot memory banks
Date: Sun, 27 Jul 2014 09:58:44 +0530 [thread overview]
Message-ID: <CAK5sBcFeaHrLLoSYCvrSMBX+eGYWoGPrCH0Uxy3Ao2OAYXoTNA@mail.gmail.com> (raw)
In-Reply-To: <53D3FB9C.9080908@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
On Sunday, July 27, 2014, Andreas Färber <afaerber@suse.de> wrote:
> Hi Laura,
>
> Am 15.07.2014 19:03, schrieb Laura Abbott:
> > This is a resend of the series to fix the uboot bug exposed by the
> removal
> > of meminfo. I haven't gotten any acks though.
> >
> > Please help with review/acks. Grant/Rob, I'd still like this to go
> through
> > the devicetree tree if possible.
>
> Sorry for the delay in testing.
>
> With this v2 applied on top of kgene's for-next branch (plus
> https://patchwork.kernel.org/patch/4297431/ as build fix) I get:
>
> [ 9.699985] Unhandled fault: asynchronous external abort (0x211) at
> 0x00000000
>
>
If this is on Arndale octa board, please try disabling MCPM option.
> Same for v1 that had worked okay before, so it's not your series, but it
> may explain why you haven't heard on v2 from the others yet.
>
> Regards,
> Andreas
>
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org <javascript:;>
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Regards,
Sachin.
[-- Attachment #2: Type: text/html, Size: 2000 bytes --]
next prev parent reply other threads:[~2014-07-27 4:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 17:03 [RESEND][PATCHv2 0/3] Fix for buggy u-boot memory banks Laura Abbott
2014-07-15 17:03 ` [RESEND][PATCHv2 1/3] of: Split early_init_dt_scan into two parts Laura Abbott
[not found] ` <1405443816-29917-1-git-send-email-lauraa-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-07-15 17:03 ` [RESEND][PATCHv2 2/3] of: Add memory limiting function for flattened devicetrees Laura Abbott
2014-07-15 17:03 ` [RESEND][PATCHv2 3/3] arm: Add devicetree fixup machine function Laura Abbott
2014-07-26 19:03 ` [RESEND][PATCHv2 0/3] Fix for buggy u-boot memory banks Andreas Färber
2014-07-27 4:28 ` Sachin Kamat [this message]
2014-07-27 5:39 ` Andreas Färber
2014-07-26 21:20 ` Rob Herring
2014-07-28 18:56 ` Laura Abbott
2014-07-30 3:24 ` Grant Likely
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=CAK5sBcFeaHrLLoSYCvrSMBX+eGYWoGPrCH0Uxy3Ao2OAYXoTNA@mail.gmail.com \
--to=spk.linux@gmail.com \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=khilman@linaro.org \
--cc=lauraa@codeaurora.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=robherring2@gmail.com \
--cc=trblinux@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 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).