From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
apenwarr@gmail.com
Subject: Re: [PATCH 0/2] ath10k: 2014-05-07 fixes
Date: Wed, 07 May 2014 06:36:37 -0700 [thread overview]
Message-ID: <536A36E5.6040100@candelatech.com> (raw)
In-Reply-To: <1399466006-5556-1-git-send-email-michal.kazior@tieto.com>
On 05/07/2014 05:33 AM, Michal Kazior wrote:
> Hi,
>
> These 2 patches address kernel panics reported by
> Avery recently. One of them was most likely
> reported by Ben some time ago already.
>
> I've never seen these panics myself. It'd be great
> if you guys could give it a try and (assuming
> you're capable of reproducing) see if it actually
> helps.
I'll add these to my tree today and we'll run them through
our test harness.
I have not been able to repeat any crashes like this recently...but
I'll let you know if I see anything strange after applying
the patches.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
apenwarr@gmail.com
Subject: Re: [PATCH 0/2] ath10k: 2014-05-07 fixes
Date: Wed, 07 May 2014 06:36:37 -0700 [thread overview]
Message-ID: <536A36E5.6040100@candelatech.com> (raw)
In-Reply-To: <1399466006-5556-1-git-send-email-michal.kazior@tieto.com>
On 05/07/2014 05:33 AM, Michal Kazior wrote:
> Hi,
>
> These 2 patches address kernel panics reported by
> Avery recently. One of them was most likely
> reported by Ben some time ago already.
>
> I've never seen these panics myself. It'd be great
> if you guys could give it a try and (assuming
> you're capable of reproducing) see if it actually
> helps.
I'll add these to my tree today and we'll run them through
our test harness.
I have not been able to repeat any crashes like this recently...but
I'll let you know if I see anything strange after applying
the patches.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-05-07 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 12:33 [PATCH 0/2] ath10k: 2014-05-07 fixes Michal Kazior
2014-05-07 12:33 ` Michal Kazior
2014-05-07 12:33 ` [PATCH 1/2] ath10k: fix htt rx ring clean up Michal Kazior
2014-05-07 12:33 ` Michal Kazior
2014-05-07 12:33 ` [PATCH 2/2] ath10k: fix handling of wierd MSDU chaining cases Michal Kazior
2014-05-07 12:33 ` Michal Kazior
2014-05-07 13:36 ` Ben Greear [this message]
2014-05-07 13:36 ` [PATCH 0/2] ath10k: 2014-05-07 fixes Ben Greear
2014-05-14 13:43 ` Kalle Valo
2014-05-14 13:43 ` Kalle Valo
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=536A36E5.6040100@candelatech.com \
--to=greearb@candelatech.com \
--cc=apenwarr@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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.