From: Kalle Valo <kvalo@codeaurora.org>
To: Andrea Greco <a.greco@4sigma.it>
Cc: johannes.berg@intel.com, Andrea Greco <a.greco@4sigma.it>,
QCA ath9k Development <ath9k-devel@qca.qualcomm.com>,
"David S. Miller" <davem@davemloft.net>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ath9K: debugfs: Fix SPUR-DOWN field
Date: Tue, 26 Feb 2019 13:08:44 +0000 (UTC) [thread overview]
Message-ID: <20190226130844.99F3E60F3C@smtp.codeaurora.org> (raw)
In-Reply-To: <20190221231257.6221-1-andrea.greco.gapmilano@gmail.com>
Andrea Greco <a.greco@4sigma.it> wrote:
> SPUR DOWN field returns spurup instead of spurdown.
>
> Signed-off-by: Andrea Greco <a.greco@4sigma.it>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
d0480d4326e2 ath9k: debugfs: Fix SPUR-DOWN field
--
https://patchwork.kernel.org/patch/10824837/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2019-02-26 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 23:12 [PATCH 2/2] ath9K: debugfs: Fix SPUR-DOWN field Andrea Greco
2019-02-26 13:08 ` Kalle Valo [this message]
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=20190226130844.99F3E60F3C@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=a.greco@4sigma.it \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=davem@davemloft.net \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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).