From: Fred Chou <fred.chou.nd@gmail.com>
To: Oleksij Rempel <linux@rempel-privat.de>,
ath9k-devel@qca.qualcomm.com, kvalo@codeaurora.org
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ath9k_htc: check seq number instead of cmd id for timeout
Date: Mon, 16 Mar 2015 12:41:16 +0800 [thread overview]
Message-ID: <55065EEC.9050601@gmail.com> (raw)
In-Reply-To: <55052B31.4020803@rempel-privat.de>
On 15/03/2015 14:48, Oleksij Rempel wrote:
> thank you for your patch. Looks good for me. Did you tested it?
Yes. Working all right for two days.
next prev parent reply other threads:[~2015-03-16 4:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 8:32 [PATCH] ath9k_htc: check seq number instead of cmd id for timeout Fred Chou
2015-03-15 6:48 ` Oleksij Rempel
2015-03-16 4:41 ` Fred Chou [this message]
2015-04-06 6:33 ` Fred Chou
[not found] ` <552228AB.8060000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-04-06 10:01 ` Oleksij Rempel
2015-04-07 17:08 ` 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=55065EEC.9050601@gmail.com \
--to=fred.chou.nd@gmail.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).