From: Kalle Valo <kvalo@codeaurora.org>
To: Federico Cuello <fedux@fedux.com.ar>
Cc: linux-wireless@vger.kernel.org, wgong@codeaurora.org,
ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: Fix ath10k_init_uart when uart_print is false
Date: Wed, 25 Sep 2019 15:02:39 +0300 [thread overview]
Message-ID: <87o8z8inxc.fsf@tynnyri.adurom.net> (raw)
In-Reply-To: <20190925090856.6964-2-fedux@fedux.com.ar> (Federico Cuello's message of "Wed, 25 Sep 2019 11:08:56 +0200")
+ ath10k
Federico Cuello <fedux@fedux.com.ar> writes:
> Patch 4504f0e5b5714d9d26b1a80bf1fc133c95830588 introduced a workaround
> for a firmware UART pin configuration bug, but it caused uart_print to be
> interpreted as true when it was false and uart_pin_workaround also false.
>
> This patch corrects the exit condition when uart_print is false.
>
> Signed-off-by: Federico Cuello <fedux@fedux.com.ar>
I have already applied a fix for this:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=ath-next&id=1340cc631bd00431e2f174525c971f119df9efa1
But it's not CCed for stable, hopefully the stable bots still catch it.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2019-09-25 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 9:08 ath10k: Poor performance with kernel 5.3 fixed Federico Cuello
2019-09-25 9:08 ` [PATCH] ath10k: Fix ath10k_init_uart when uart_print is false Federico Cuello
2019-09-25 12:02 ` Kalle Valo [this message]
2019-09-25 16:24 ` ath10k: Poor performance with kernel 5.3 fixed Brian Norris
2019-09-26 7:56 ` Federico Cuello
2019-09-26 12:54 ` Kalle Valo
2019-09-27 9:25 ` Federico Cuello
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=87o8z8inxc.fsf@tynnyri.adurom.net \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=fedux@fedux.com.ar \
--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 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).