From: Marc Zyngier <marc.zyngier@arm.com>
To: Pavel Machek <pavel@ucw.cz>,
pali.rohar@gmail.com, sre@debian.org, sre@ring0.de,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org,
aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
patrikbachan@gmail.com
Subject: Re: n900 in 4.1-rc0
Date: Thu, 16 Apr 2015 10:37:52 +0100 [thread overview]
Message-ID: <552F82F0.3070709@arm.com> (raw)
In-Reply-To: <20150416093234.GA17423@amd>
On 16/04/15 10:32, Pavel Machek wrote:
> Hi!
>
> Just tried booting 4.1-rc0 on n900 (commit
> 34c9a0ffc75ad25b6a60f61e27c4a4b1189b8085) and it is broken.
>
> Any ideas?
To such a question, the only answer I have is "Yes".
For a more useful reply, I'm afraid you'll have to ask a better question.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
WARNING: multiple messages have this Message-ID (diff)
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: n900 in 4.1-rc0
Date: Thu, 16 Apr 2015 10:37:52 +0100 [thread overview]
Message-ID: <552F82F0.3070709@arm.com> (raw)
In-Reply-To: <20150416093234.GA17423@amd>
On 16/04/15 10:32, Pavel Machek wrote:
> Hi!
>
> Just tried booting 4.1-rc0 on n900 (commit
> 34c9a0ffc75ad25b6a60f61e27c4a4b1189b8085) and it is broken.
>
> Any ideas?
To such a question, the only answer I have is "Yes".
For a more useful reply, I'm afraid you'll have to ask a better question.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-04-16 9:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 9:32 n900 in 4.1-rc0 Pavel Machek
2015-04-16 9:32 ` Pavel Machek
2015-04-16 9:37 ` Marc Zyngier [this message]
2015-04-16 9:37 ` Marc Zyngier
2015-04-16 16:35 ` Tony Lindgren
2015-04-16 16:35 ` Tony Lindgren
2015-04-26 10:15 ` Pavel Machek
2015-04-26 10:15 ` Pavel Machek
2015-04-16 16:45 ` Tyler Baker
2015-04-16 16:45 ` Tyler Baker
2015-04-26 10:20 ` Pavel Machek
2015-04-26 10:20 ` Pavel Machek
2015-04-27 18:58 ` Tyler Baker
2015-04-27 18:58 ` Tyler Baker
2015-06-29 9:11 ` n900 in 4.2-rc0: repeating oopses Pavel Machek
2015-06-29 10:45 ` Pali Rohár
2015-06-29 10:45 ` Pali Rohár
2015-06-30 9:24 ` Pavel Machek
2015-06-30 9:24 ` Pavel Machek
2015-06-30 9:53 ` Pali Rohár
2015-06-30 9:53 ` Pali Rohár
2015-07-01 6:59 ` Tony Lindgren
2015-07-01 6:59 ` Tony Lindgren
2015-07-01 7:22 ` Pali Rohár
2015-07-01 7:22 ` Pali Rohár
2015-07-01 9:59 ` Pavel Machek
2015-07-01 9:59 ` Pavel Machek
2015-07-01 10:34 ` Tony Lindgren
2015-07-01 10:34 ` Tony Lindgren
2015-07-01 13:09 ` Pavel Machek
2015-07-01 13:09 ` Pavel Machek
2015-07-02 6:16 ` Tony Lindgren
2015-07-02 6:16 ` Tony Lindgren
2015-07-26 22:31 ` Pavel Machek
2015-07-26 22:31 ` Pavel Machek
2015-07-27 7:12 ` Pali Rohár
2015-07-27 7:12 ` Pali Rohár
2015-07-02 20:25 ` Pavel Machek
2015-07-02 20:25 ` Pavel Machek
2015-07-26 9:26 ` Pavel Machek
2015-07-26 9:26 ` Pavel Machek
2015-07-28 6:01 ` Tony Lindgren
2015-07-28 6:01 ` Tony Lindgren
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=552F82F0.3070709@arm.com \
--to=marc.zyngier@arm.com \
--cc=aaro.koskinen@iki.fi \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@debian.org \
--cc=sre@ring0.de \
--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.