From: jiada_wang@mentor.com (jiada)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx: replace imx6q_restart() with mxc_restart()
Date: Sun, 27 Oct 2013 19:41:23 -0700 [thread overview]
Message-ID: <526DCED3.2070704@mentor.com> (raw)
In-Reply-To: <20131021070451.GI17165@S2101-09.ap.freescale.net>
Hi Shawn
On 10/21/2013 12:04 AM, Shawn Guo wrote:
> On Sun, Oct 20, 2013 at 11:13:41PM -0700, jiada wrote:
>> I tried to checkout upstream kernel at commit: f36854c
>> even without your "ARM: imx: replace imx6q_restart() with
>> mxc_restart()" patch
>> I can reproduce system hang issue by "echo b > /proc/sysrq-trigger"
>
> Since the patch hasn't hit upstream tree, you meant you can reproduce
> the issue on linux-next or my for-next branch? What's the reproducing
> rate? I ran a few iterations but did not hit it.
>
> Shawn
>
as per discussion locally, when do you think you will post the fix patch
for the system hang I observed?
I would like to test for your patch, and then pull it to my kernel.
Thanks,
Jiada
next prev parent reply other threads:[~2013-10-28 2:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 9:06 [PATCH] ARM: imx: replace imx6q_restart() with mxc_restart() Shawn Guo
2013-10-08 15:32 ` Nathan Lynch
2013-10-08 15:49 ` Shawn Guo
[not found] ` <857E9EDCA6C0904DB3357321AA9123EB62506837@NA-MBX-01.mgc.mentorg.com>
2013-10-21 3:32 ` jiada
2013-10-21 4:59 ` Shawn Guo
[not found] ` <857E9EDCA6C0904DB3357321AA9123EB62506BEA@NA-MBX-01.mgc.mentorg.com>
2013-10-21 6:13 ` jiada
2013-10-21 7:04 ` Shawn Guo
2013-10-28 2:41 ` jiada [this message]
2013-10-28 2:52 ` Shawn Guo
2013-10-28 7:45 ` Shawn Guo
2013-10-30 3:13 ` jiada
2013-10-30 17:54 ` Russell King - ARM Linux
2013-10-31 5:23 ` Shawn Guo
2013-10-31 5:31 ` jiada
2013-10-28 5:17 ` Olof Johansson
2013-10-28 8:14 ` Shawn Guo
2013-10-28 17:46 ` Olof Johansson
2013-10-29 2:06 ` Shawn Guo
2013-10-29 8:53 ` Lothar Waßmann
2013-10-29 11:37 ` Russell King - ARM Linux
2013-10-29 13:37 ` Shawn Guo
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=526DCED3.2070704@mentor.com \
--to=jiada_wang@mentor.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.