From: Sven Eckelmann <sven@narfation.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>, ath11k@lists.infradead.org
Cc: ath10k <ath10k@lists.infradead.org>,
ath11k <ath11k@lists.infradead.org>,
ath12k <ath12k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <quic_kvalo@quicinc.com>,
Robert Marko <robert.marko@sartura.hr>
Subject: Re: New staging repos for ath1*k firmware
Date: Tue, 10 Sep 2024 11:00:52 +0200 [thread overview]
Message-ID: <3772134.MHq7AAxBmi@ripper> (raw)
In-Reply-To: <CA+HBbNFQ+25u_PK2j3vYtiCZwv+shVAVeAHKqQCwhyCopORt4Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
On Thursday, 7 March 2024 09:39:26 CEST Robert Marko wrote:
> Can I please ask for IPQ6018 firmware to be updated to 2.9.0.1 as well?
>
I've asked them via their support platform. They closed the ticket after Jeff
uploaded the 2.7.0.1 firmware (which was given to him by the firmware team).
I will ask again...
(Btw. thanks to Jeff and Kalle for managing the new firmware repositories - I
just hope that you get better input from the firmware teams)
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-09-10 9:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 19:23 New staging repos for ath1*k firmware Jeff Johnson
2024-03-07 8:39 ` Robert Marko
2024-03-07 16:49 ` Kalle Valo
2024-03-09 17:58 ` Sebastian Gottschall
2024-03-13 19:32 ` Jeff Johnson
2024-03-14 7:54 ` Robert Marko
2024-03-14 22:27 ` Felix Kaechele
2024-09-10 9:00 ` Sven Eckelmann [this message]
2024-09-10 9:23 ` Kalle Valo
2024-09-10 11:39 ` Sven Eckelmann
2024-09-10 11:46 ` Robert Marko
2024-09-11 19:18 ` Jeff Johnson
2024-05-17 5:32 ` Kalle Valo
2024-06-03 20:11 ` Kalle Valo
2024-06-03 20:21 ` pgupta
2024-06-03 20:47 ` Jeff Johnson
2025-11-21 13:28 ` Paweł Owoc
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=3772134.MHq7AAxBmi@ripper \
--to=sven@narfation.org \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_kvalo@quicinc.com \
--cc=robert.marko@sartura.hr \
/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