From: Kalle Valo <kvalo@codeaurora.org>
To: Govind Singh <govinds@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
govinds@codeaurora.org
Subject: Re: ath10k: Fix fw path name for WCN3990 target
Date: Thu, 19 Apr 2018 16:22:12 +0000 (UTC) [thread overview]
Message-ID: <20180419162212.BC7B660F6E@smtp.codeaurora.org> (raw)
In-Reply-To: <1523852805-14292-1-git-send-email-govinds@codeaurora.org>
Govind Singh <govinds@codeaurora.org> wrote:
> FW path is mapped incorrectly for the WCN3990
> hw version. Fix fw path with correct hw1.0 name.
>
> Signed-off-by: Govind Singh <govinds@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
6da2b2d46ff9 ath10k: fix fw path name for WCN3990 target
--
https://patchwork.kernel.org/patch/10342185/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2018-04-19 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 4:26 [PATCH] ath10k: Fix fw path name for WCN3990 target Govind Singh
2018-04-16 4:26 ` Govind Singh
2018-04-19 16:22 ` Kalle Valo [this message]
2018-04-19 16:22 ` 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=20180419162212.BC7B660F6E@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=govinds@codeaurora.org \
--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.