From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: <ath10k@lists.infradead.org>,
Ben Greear <greearb@candelatech.com>,
<linux-wireless@vger.kernel.org>
Subject: Re: [v2,3/5] ath10k: Add WARN_ON if we over-write peer-map pointer.
Date: Fri, 8 Jul 2016 08:48:40 +0200 [thread overview]
Message-ID: <de2f7017a0ef446d994f1e8f6b2ed9fd@euamsexm01a.eu.qualcomm.com> (raw)
In-Reply-To: <1459545132-11295-3-git-send-email-greearb@candelatech.com>
Ben Greear <greearb@candelatech.com> wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> Not sure this can happen, but seems like a reasonable sanity
> check.
>
> Signed-off-by: Ben Greear <greearb@candelatech.com>
Thanks, 2 patches applied to ath-next branch of ath.git:
c5ace87a886d ath10k: Add WARN_ON if we over-write peer-map pointer.
d0eeafad1189 ath10k: Clean up peer when sta goes away.
--
Sent by pwcli
https://patchwork.kernel.org/patch/8727861/
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [v2,3/5] ath10k: Add WARN_ON if we over-write peer-map pointer.
Date: Fri, 8 Jul 2016 08:48:40 +0200 [thread overview]
Message-ID: <de2f7017a0ef446d994f1e8f6b2ed9fd@euamsexm01a.eu.qualcomm.com> (raw)
In-Reply-To: <1459545132-11295-3-git-send-email-greearb@candelatech.com>
Ben Greear <greearb@candelatech.com> wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> Not sure this can happen, but seems like a reasonable sanity
> check.
>
> Signed-off-by: Ben Greear <greearb@candelatech.com>
Thanks, 2 patches applied to ath-next branch of ath.git:
c5ace87a886d ath10k: Add WARN_ON if we over-write peer-map pointer.
d0eeafad1189 ath10k: Clean up peer when sta goes away.
--
Sent by pwcli
https://patchwork.kernel.org/patch/8727861/
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-07-08 6:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 21:12 [PATCH v2 1/5] ath10k: Ensure txrx-compl-task is stopped when cleaning htt-tx greearb
2016-04-01 21:12 ` greearb
2016-04-01 21:12 ` [PATCH v2 2/5] ath10k: Ensure peer_map references are cleaned up greearb
2016-04-01 21:12 ` greearb
2016-04-01 21:12 ` [PATCH v2 3/5] ath10k: Add WARN_ON if we over-write peer-map pointer greearb
2016-04-01 21:12 ` greearb
2016-05-10 7:12 ` Mohammed Shafi Shajakhan
2016-05-10 7:12 ` Mohammed Shafi Shajakhan
2016-05-10 14:41 ` Ben Greear
2016-05-10 14:41 ` Ben Greear
2016-05-10 16:38 ` Mohammed Shafi Shajakhan
2016-05-10 16:38 ` Mohammed Shafi Shajakhan
2016-07-08 6:48 ` Kalle Valo [this message]
2016-07-08 6:48 ` [v2,3/5] " Kalle Valo
2016-04-01 21:12 ` [PATCH v2 4/5] ath10k: Clean up peer when sta goes away greearb
2016-04-01 21:12 ` greearb
2016-04-01 21:12 ` [PATCH v2 5/5] ath10k: Fix deadlock when peer cannot be created greearb
2016-04-01 21:12 ` greearb
2016-05-09 17:19 ` Ben Greear
2016-05-09 17:19 ` Ben Greear
2016-05-09 17:54 ` Manoharan, Rajkumar
2016-05-09 17:54 ` Manoharan, Rajkumar
2016-05-09 17:58 ` Ben Greear
2016-05-09 17:58 ` Ben Greear
2016-05-13 14:07 ` Valo, Kalle
2016-05-13 14:07 ` Valo, Kalle
2016-06-06 17:24 ` [v2,5/5] " Kalle Valo
2016-06-06 17:24 ` Kalle Valo
2016-05-10 6:48 ` [PATCH v2 1/5] ath10k: Ensure txrx-compl-task is stopped when cleaning htt-tx Mohammed Shafi Shajakhan
2016-05-10 6:48 ` Mohammed Shafi Shajakhan
2016-05-10 14:39 ` Ben Greear
2016-05-10 14:39 ` Ben Greear
2016-05-10 16:36 ` Mohammed Shafi Shajakhan
2016-05-10 16:36 ` Mohammed Shafi Shajakhan
2016-07-08 6:43 ` [v2, " Kalle Valo
2016-07-08 6: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=de2f7017a0ef446d994f1e8f6b2ed9fd@euamsexm01a.eu.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.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.