From: Kalle Valo <kvalo@codeaurora.org>
To: "sparks71\@gmx.de" <sparks71@gmx.de>
Cc: ojab // <ojab@ojab.ru>, "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
ath10k@lists.infradead.org,
Linux Wireless <linux-wireless@vger.kernel.org>,
netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] ath10k: don't fail if IRAM write fails
Date: Tue, 21 Sep 2021 10:29:34 +0300 [thread overview]
Message-ID: <87wnnav129.fsf@codeaurora.org> (raw)
In-Reply-To: <538825a2-82f0-6102-01da-6e0385e53cf5@gmx.de> (sparks's message of "Sat, 18 Sep 2021 12:12:23 +0200")
"sparks71@gmx.de" <sparks71@gmx.de> writes:
> Have you seen the new patch?
>
> https://www.mail-archive.com/ath10k@lists.infradead.org/msg13784.html
>
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=master-pending&id=973de582639a1e45276e4e3e2f3c2d82a04ad0a6
>
>
> could probably have been communicated better
Yeah, apparently there are two different fixes now. I'll review both of
them and try to choose which one to take.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2021-09-21 7:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 19:35 [PATCH V2] ath10k: don't fail if IRAM write fails ojab
2021-07-22 19:42 ` ojab //
2021-08-02 2:23 ` Axel Rasmussen
2021-08-12 20:21 ` Axel Rasmussen
2021-08-14 11:33 ` sparks71
2021-08-25 16:15 ` ojab //
2021-09-08 23:42 ` ojab //
2021-09-17 19:30 ` ojab //
2021-09-18 10:12 ` sparks71
2021-09-18 11:21 ` ojab //
2021-09-21 7:29 ` Kalle Valo [this message]
2021-09-21 7:50 ` sparks71
2021-10-20 7:54 ` 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=87wnnav129.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ojab@ojab.ru \
--cc=sparks71@gmx.de \
/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).