From: Cristian Cimpianu <cristi@trego.co.il>
To: backports@vger.kernel.org
Cc: eyal@trego.co.il
Subject: backports for wifi-7 and kernel 6.5
Date: Thu, 23 Nov 2023 16:24:35 +0200 [thread overview]
Message-ID: <31498106.Y1g1iz2YYI@cristie14.c-scale.ro> (raw)
Hi guys,
I've been working on a project using the backports project to build some custom wifi modules for different kernel versions.
Now the customer wants to do a wifi-7 chip keeping the infrastructure the same as much as possible. But wifi-7 has been added into kernel 6.5, while the backports project is still at 5.15. And the customer wants that in like 6 months.
So, in the hope I will understand better what would be the easiest solution, I figured I could ask here.
Is there a plan to add support in the backports project for kernel 6.5 or for the wifi-7 changes to the mac80211 and cfg80211 modules?
best regards,
Cristian.
next reply other threads:[~2023-11-23 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 14:24 Cristian Cimpianu [this message]
2023-11-24 13:34 ` backports for wifi-7 and kernel 6.5 Larry Finger
2023-11-24 17:38 ` Brian Witte
2023-12-04 13:36 ` Cristian Cimpianu
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=31498106.Y1g1iz2YYI@cristie14.c-scale.ro \
--to=cristi@trego.co.il \
--cc=backports@vger.kernel.org \
--cc=eyal@trego.co.il \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).