From: Kalle Valo <kvalo@codeaurora.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH -next 1/2] ath10k: go to path err_unsupported when chip id is not supported
Date: Sat, 12 Jun 2021 10:34:44 +0000 (UTC) [thread overview]
Message-ID: <20210612103444.2E050C433F1@smtp.codeaurora.org> (raw)
In-Reply-To: <20210522105822.1091848-2-yangyingliang@huawei.com>
Yang Yingliang <yangyingliang@huawei.com> wrote:
> When chip id is not supported, it go to path err_unsupported
> to print the error message.
>
> Fixes: f8914a14623a ("ath10k: restore QCA9880-AR1A (v1) detection")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
2 patches applied to ath-next branch of ath.git, thanks.
9e88dd431d23 ath10k: go to path err_unsupported when chip id is not supported
e2783e2f39ba ath10k: add missing error return code in ath10k_pci_probe()
--
https://patchwork.kernel.org/project/linux-wireless/patch/20210522105822.1091848-2-yangyingliang@huawei.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-06-12 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 10:58 [PATCH -next 0/2] fix missing error code on path err_unsupported Yang Yingliang
2021-05-22 10:58 ` [PATCH -next 1/2] ath10k: go to path err_unsupported when chip id is not supported Yang Yingliang
2021-06-12 10:34 ` Kalle Valo [this message]
2021-05-22 10:58 ` [PATCH -next 2/2] ath10k: add missing error return code in ath10k_pci_probe() Yang Yingliang
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=20210612103444.2E050C433F1@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yangyingliang@huawei.com \
/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).