From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: Hui Liu <Hui.Liu@freescale.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
<ath6kl@lists.infradead.org>
Subject: Re: [PATCH] ath6kl: sdio: fix system panic when doing wifi stress test
Date: Sat, 8 Mar 2014 13:57:36 +0200 [thread overview]
Message-ID: <87a9d0oqbz.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20140307093813.GA28728@pengutronix.de> (Steffen Trumtrar's message of "Fri, 7 Mar 2014 10:38:13 +0100")
Hi Steffen,
Steffen Trumtrar <s.trumtrar@pengutronix.de> writes:
>> > Does the patch below help? It would also fix the corruption with
>> > scat_q_depth. Please note that I have only compile tested it. And I might
>> > have also missed something important, so please review it carefully.
>>
>> Yes, Firstly, I have looked at the asm code and the compiler(gcc 4.8.1) works correctly after applying
>> the following patch. Secondly, I have tested the patch with compiler(gcc 4.8.1) on the real HW, and it
>> works fine too. Without the patch, the kernel crash will happen 100%.
>>
>> Thus, for the patch:
>>
>> Acked-by: Jason Liu <r64343@freescale.com>
>> Tested-by: Jason Liu <r64343@freescale.com>
[...]
> What happend with this? If I look in mainline, I don't find it. At
> least the reording of the struct fields looks as if one definitely
> wants to have that.
It seems that I forgot to submit this properly, sorry about that. I did
it now:
http://lists.infradead.org/pipermail/ath6kl/2014-March/000000.html
--
Kalle Valo
next prev parent reply other threads:[~2014-03-08 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 1:53 [PATCH] ath6kl: sdio: fix system panic when doing wifi stress test Jason Liu
2013-11-26 10:40 ` Kalle Valo
2013-11-29 6:02 ` Hui Liu
2014-03-07 9:38 ` Steffen Trumtrar
2014-03-08 11:57 ` Kalle Valo [this message]
2014-03-08 15:37 ` Steffen Trumtrar
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=87a9d0oqbz.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=Hui.Liu@freescale.com \
--cc=ath6kl@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=s.trumtrar@pengutronix.de \
/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