From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-next <linux-next@vger.kernel.org>,
Rob Herring <robherring2@gmail.com>,
Anton Kolesov <Anton.Kolesov@synopsys.com>,
lkml <linux-kernel@vger.kernel.org>,
greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: ARC fails to boot on linux-next of 20140711
Date: Fri, 25 Jul 2014 16:56:14 +0530 [thread overview]
Message-ID: <53D23ED6.9010502@synopsys.com> (raw)
In-Reply-To: <C2D7FE5348E1B147BCA15975FBA230753C4B67CF@IN01WEMBXA.internal.synopsys.com>
On Friday 25 July 2014 04:32 PM, Vineet Gupta wrote:
> 2014-03-27 a9296cf2d0b6 of: Create of_console_check() for selecting a console
> specified in /chosen
> 2014-03-27 cfa9cacc5dd3 of: Enable console on serial ports specified by
> /chosen/stdout-path
>
> Is there a specific reason for dropping these patches (or perhaps a merge to be
> merged). I cherry-picked both but still doesn't work.
Correction - with these two, ARC boots again.
Thx,
-Vineet
next prev parent reply other threads:[~2014-07-25 11:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 11:02 ARC fails to boot on linux-next of 20140711 Vineet Gupta
2014-07-25 11:26 ` Vineet Gupta [this message]
2014-07-25 14:15 ` Rob Herring
2014-07-26 5:33 ` Grant Likely
2014-07-26 6:53 ` Vineet Gupta
2014-07-26 6:53 ` Vineet Gupta
2014-07-26 15:17 ` Guenter Roeck
2014-07-26 6:52 ` Vineet Gupta
2014-07-26 16:50 ` Grant Likely
2014-07-26 20:10 ` Rob Herring
2014-07-31 3:25 ` Grant Likely
[not found] ` <20140731032527.D2C5AC40A02-WNowdnHR2B42iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2014-07-31 15:12 ` Rob Herring
2014-07-31 15:12 ` Rob Herring
2014-07-28 4:38 ` Vineet Gupta
2014-07-30 23:53 ` 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=53D23ED6.9010502@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Anton.Kolesov@synopsys.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robherring2@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 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.