All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wen Gong <wgong@qti.qualcomm.com>
To: Wen Gong <wgong@codeaurora.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH v3 0/2] start recovery process when payload length overflow for sdio
Date: Wed, 8 Jan 2020 03:23:57 +0000	[thread overview]
Message-ID: <CH2PR02MB66484ED5F29338E0E4408758843E0@CH2PR02MB6648.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20191231092806.6247-1-wgong@codeaurora.org>

> -----Original Message-----
> From: ath10k <ath10k-bounces@lists.infradead.org> On Behalf Of Wen Gong
> Sent: Tuesday, December 31, 2019 5:28 PM
> To: ath10k@lists.infradead.org
> Cc: linux-wireless@vger.kernel.org
> Subject: [EXT] [PATCH v3 0/2] start recovery process when payload length
> overflow for sdio
>

V4 sent:
https://patchwork.kernel.org/cover/11322579/
https://patchwork.kernel.org/patch/11322581/
https://patchwork.kernel.org/patch/11322583/

> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Wen Gong <wgong@qti.qualcomm.com>
To: Wen Gong <wgong@codeaurora.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH v3 0/2] start recovery process when payload length overflow for sdio
Date: Wed, 8 Jan 2020 03:23:57 +0000	[thread overview]
Message-ID: <CH2PR02MB66484ED5F29338E0E4408758843E0@CH2PR02MB6648.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20191231092806.6247-1-wgong@codeaurora.org>

> -----Original Message-----
> From: ath10k <ath10k-bounces@lists.infradead.org> On Behalf Of Wen Gong
> Sent: Tuesday, December 31, 2019 5:28 PM
> To: ath10k@lists.infradead.org
> Cc: linux-wireless@vger.kernel.org
> Subject: [EXT] [PATCH v3 0/2] start recovery process when payload length
> overflow for sdio
>

V4 sent:
https://patchwork.kernel.org/cover/11322579/
https://patchwork.kernel.org/patch/11322581/
https://patchwork.kernel.org/patch/11322583/

> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  parent reply	other threads:[~2020-01-08  3:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-31  9:28 [PATCH v3 0/2] start recovery process when payload length overflow for sdio Wen Gong
2019-12-31  9:28 ` Wen Gong
2019-12-31  9:28 ` [PATCH v3 1/2] ath10k: add refcount for ath10k_core_restart Wen Gong
2019-12-31  9:28   ` Wen Gong
2019-12-31  9:28 ` [PATCH v3 2/2] ath10k: start recovery process when payload length exceeds max htc length for sdio Wen Gong
2019-12-31  9:28   ` Wen Gong
2020-01-08  3:23 ` Wen Gong [this message]
2020-01-08  3:23   ` [PATCH v3 0/2] start recovery process when payload length overflow " Wen Gong

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=CH2PR02MB66484ED5F29338E0E4408758843E0@CH2PR02MB6648.namprd02.prod.outlook.com \
    --to=wgong@qti.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wgong@codeaurora.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.