From: Kalle Valo <kvalo@kernel.org>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: linux-firmware@kernel.org, linux-wireless@vger.kernel.org,
ath10k@lists.infradead.org, ath11k@lists.infradead.org
Subject: Re: [PULL linux-firmware] ath10k & ath11k firmware 20230215
Date: Mon, 20 Feb 2023 07:56:51 +0200 [thread overview]
Message-ID: <87a618517g.fsf@kernel.org> (raw)
In-Reply-To: <c9ccbfe1-9535-f46c-756e-4eb19c1afbff@gmail.com> (Christian Lamparter's message of "Fri, 17 Feb 2023 19:57:03 +0100")
Christian Lamparter <chunkeey@gmail.com> writes:
> On 2/15/23 10:17, Kalle Valo wrote:
>> Here's a new pull request for ath10k and ath11k. We have new hardware
>> IPQ5018 and various updates for existing hardware. Especially many have
>> requested the firmware update for WCN6855 which seems to fix an
>> important suspend problem.
>>
>> Please let me know if there are any problems.
>
> Could you also please include all the QCA9888+IPQ4019 boardfiles updates
> from last year too?
I will try to go through them later. The problem here is that I don't
have much time for ath10k nowadays.
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: linux-firmware@kernel.org, linux-wireless@vger.kernel.org,
ath10k@lists.infradead.org, ath11k@lists.infradead.org
Subject: Re: [PULL linux-firmware] ath10k & ath11k firmware 20230215
Date: Mon, 20 Feb 2023 07:56:51 +0200 [thread overview]
Message-ID: <87a618517g.fsf@kernel.org> (raw)
In-Reply-To: <c9ccbfe1-9535-f46c-756e-4eb19c1afbff@gmail.com> (Christian Lamparter's message of "Fri, 17 Feb 2023 19:57:03 +0100")
Christian Lamparter <chunkeey@gmail.com> writes:
> On 2/15/23 10:17, Kalle Valo wrote:
>> Here's a new pull request for ath10k and ath11k. We have new hardware
>> IPQ5018 and various updates for existing hardware. Especially many have
>> requested the firmware update for WCN6855 which seems to fix an
>> important suspend problem.
>>
>> Please let me know if there are any problems.
>
> Could you also please include all the QCA9888+IPQ4019 boardfiles updates
> from last year too?
I will try to go through them later. The problem here is that I don't
have much time for ath10k nowadays.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: linux-firmware@kernel.org, linux-wireless@vger.kernel.org,
ath10k@lists.infradead.org, ath11k@lists.infradead.org
Subject: Re: [PULL linux-firmware] ath10k & ath11k firmware 20230215
Date: Mon, 20 Feb 2023 07:56:51 +0200 [thread overview]
Message-ID: <87a618517g.fsf@kernel.org> (raw)
In-Reply-To: <c9ccbfe1-9535-f46c-756e-4eb19c1afbff@gmail.com> (Christian Lamparter's message of "Fri, 17 Feb 2023 19:57:03 +0100")
Christian Lamparter <chunkeey@gmail.com> writes:
> On 2/15/23 10:17, Kalle Valo wrote:
>> Here's a new pull request for ath10k and ath11k. We have new hardware
>> IPQ5018 and various updates for existing hardware. Especially many have
>> requested the firmware update for WCN6855 which seems to fix an
>> important suspend problem.
>>
>> Please let me know if there are any problems.
>
> Could you also please include all the QCA9888+IPQ4019 boardfiles updates
> from last year too?
I will try to go through them later. The problem here is that I don't
have much time for ath10k nowadays.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-02-20 5:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 9:17 [PULL linux-firmware] ath10k & ath11k firmware 20230215 Kalle Valo
2023-02-15 9:17 ` Kalle Valo
2023-02-15 9:17 ` Kalle Valo
2023-02-15 19:27 ` Josh Boyer
2023-02-15 19:27 ` Josh Boyer
2023-02-15 19:27 ` Josh Boyer
2023-02-17 18:57 ` Christian Lamparter
2023-02-17 18:57 ` Christian Lamparter
2023-02-17 18:57 ` Christian Lamparter
2023-02-20 5:56 ` Kalle Valo [this message]
2023-02-20 5:56 ` Kalle Valo
2023-02-20 5:56 ` Kalle Valo
2023-03-14 12:59 ` Christian Lamparter
2023-03-14 12:59 ` Christian Lamparter
2023-03-15 6:28 ` Kalle Valo
2023-03-15 6:28 ` Kalle Valo
2023-03-17 22:25 ` Christian Lamparter
2023-03-17 22:25 ` Christian Lamparter
2023-03-21 23:39 ` Dmitry Baryshkov
2023-03-21 23:39 ` Dmitry Baryshkov
2023-03-21 23:39 ` Dmitry Baryshkov
2023-03-22 5:54 ` Kalle Valo
2023-03-22 5:54 ` Kalle Valo
2023-03-22 5:54 ` Kalle Valo
2023-03-23 9:35 ` Dmitry Baryshkov
2023-03-23 9:35 ` Dmitry Baryshkov
2023-03-23 9:35 ` Dmitry Baryshkov
2023-03-23 10:19 ` Kalle Valo
2023-03-23 10:19 ` Kalle Valo
2023-03-23 10:19 ` 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=87a618517g.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--cc=chunkeey@gmail.com \
--cc=linux-firmware@kernel.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.