From: Sven Eckelmann <sven@narfation.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: Tanjeff Moos <Tanjeff.Moos@westermo.com>,
openwrt-devel@lists.openwrt.org, Felix Fietkau <nbd@nbd.name>,
ath11k@lists.infradead.org,
Jeff Johnson <quic_jjohnson@quicinc.com>
Subject: Re: Question to recent Qualcomm CVEs
Date: Mon, 29 Apr 2024 15:36:47 +0200 [thread overview]
Message-ID: <4889305.GXAFRqVoOG@bentobox> (raw)
In-Reply-To: <87il00qpjp.fsf@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
On Monday, 29 April 2024 15:14:18 CEST Kalle Valo wrote:
> It's quite strange that they updated 2.5.0.1 branch first but my
> understanding that there should be updates for the newer 2.7.0.1 branch
> as well (2.7.0.1 branch is also in linux-firmware).
Yes, I also told them in the support ticket that this is from an older branch
than what is currently shipped in linux-firmware.git. But they told me
that they are working on newer versions (whatever that means) - but they
wanted to handle first the update to ATH.11.4 (2.5.0.x) and then
step-by-step release it for newer firmware branches. It seem like that would be
up to 2.9.0.x - no idea why there is no (public) 2.10.x/2.11.x for the AP
SoCs.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-29 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48174971-4b30-4046-9710-2acb16990e07@westermo.com>
[not found] ` <5e5c35eb-336b-4e92-b506-506e9fbeef7d@nbd.name>
[not found] ` <2668032.usQuhbGJ8B@ripper>
2024-02-26 15:53 ` Question to recent Qualcomm CVEs Kalle Valo
2024-04-29 13:14 ` Kalle Valo
2024-04-29 13:36 ` Sven Eckelmann [this message]
2024-04-29 14:50 ` Robert Marko
2024-04-30 8:47 ` Kalle Valo
2024-04-30 8:56 ` Robert Marko
2024-04-30 13:02 ` Kalle Valo
2024-04-30 13:05 ` Robert Marko
2024-04-30 13:11 ` Christian Marangi (Ansuel)
2024-05-02 7:25 ` Sven Eckelmann
2024-05-03 7:42 ` Sven Eckelmann
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=4889305.GXAFRqVoOG@bentobox \
--to=sven@narfation.org \
--cc=Tanjeff.Moos@westermo.com \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=nbd@nbd.name \
--cc=openwrt-devel@lists.openwrt.org \
--cc=quic_jjohnson@quicinc.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 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.