From: wgong@codeaurora.org
To: Justin Capella <justincapella@gmail.com>
Cc: linux-wireless@vger.kernel.org, ath10k <ath10k@lists.infradead.org>
Subject: Re: [PATCH v2 1/2] ath10k: add refcount for ath10k_core_restart
Date: Tue, 31 Dec 2019 17:37:37 +0800 [thread overview]
Message-ID: <5f6eb95de0f877b86b90d0c32d458d43@codeaurora.org> (raw)
In-Reply-To: <CAMrEMU-p3+HRZYW6TzXwZSwhxj9oJ9JW1Rg=ZysJ3fr0rm45Ng@mail.gmail.com>
On 2019-12-25 23:14, Justin Capella wrote:
> This does not only effect SDIO.
>
> Why a semaphore / count? Could the conf_mutex be held earlier, or
> perhaps change the state to ATH10K_STATE_RESTARTING first?
> ath10k_reconfig_complete is also called in mac.c when channel is
> changed so
patch v2:
https://patchwork.kernel.org/patch/11313853/
https://patchwork.kernel.org/patch/11313859/
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: wgong@codeaurora.org
To: Justin Capella <justincapella@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ath10k: add refcount for ath10k_core_restart
Date: Tue, 31 Dec 2019 17:37:37 +0800 [thread overview]
Message-ID: <5f6eb95de0f877b86b90d0c32d458d43@codeaurora.org> (raw)
In-Reply-To: <CAMrEMU-p3+HRZYW6TzXwZSwhxj9oJ9JW1Rg=ZysJ3fr0rm45Ng@mail.gmail.com>
On 2019-12-25 23:14, Justin Capella wrote:
> This does not only effect SDIO.
>
> Why a semaphore / count? Could the conf_mutex be held earlier, or
> perhaps change the state to ATH10K_STATE_RESTARTING first?
> ath10k_reconfig_complete is also called in mac.c when channel is
> changed so
patch v2:
https://patchwork.kernel.org/patch/11313853/
https://patchwork.kernel.org/patch/11313859/
next prev parent reply other threads:[~2019-12-31 9:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 12:00 [PATCH v2 0/2] start recovery process when payload length overflow for sdio Wen Gong
2019-12-25 12:00 ` Wen Gong
2019-12-25 12:00 ` [PATCH v2 1/2] ath10k: add refcount for ath10k_core_restart Wen Gong
2019-12-25 12:00 ` Wen Gong
2019-12-25 15:14 ` Justin Capella
2019-12-25 15:14 ` Justin Capella
2019-12-31 9:37 ` wgong [this message]
2019-12-31 9:37 ` wgong
2020-01-02 3:10 ` Justin Capella
2020-01-02 3:10 ` Justin Capella
2020-01-02 4:46 ` wgong
2020-01-02 4:46 ` wgong
2019-12-25 12:00 ` [PATCH v2 2/2] ath10k: start recovery process when payload length exceeds max htc length for sdio Wen Gong
2019-12-25 12:00 ` Wen Gong
2019-12-25 22:56 ` Justin Capella
2019-12-25 22:56 ` Justin Capella
2020-01-02 4:50 ` wgong
2020-01-02 4:50 ` wgong
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=5f6eb95de0f877b86b90d0c32d458d43@codeaurora.org \
--to=wgong@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=justincapella@gmail.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.