netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull-request: wireless-next-2023-10-16
Date: Tue, 17 Oct 2023 17:13:24 -0700	[thread overview]
Message-ID: <20231017171324.6c7c2986@kernel.org> (raw)
In-Reply-To: <20231016143822.880D8C433C8@smtp.kernel.org>

On Mon, 16 Oct 2023 14:38:22 +0000 (UTC) Kalle Valo wrote:
> wireless-next patches for v6.7
> 
> The second pull request for v6.7, with only driver changes this time.
> We have now support for mt7925 PCIe and USB variants, few new features
> and of course some fixes.
> 
> Major changes:
> 
> mt76
> 
> * mt7925 support
> 
> ath12k
> 
> * read board data variant name from SMBIOS
> 
> wfx
> 
> * Remain-On-Channel (ROC) support

And due to our slowness it's almost Wednesday, anyway.. sorry about
that!

  reply	other threads:[~2023-10-18  0:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16 14:38 pull-request: wireless-next-2023-10-16 Kalle Valo
2023-10-18  0:13 ` Jakub Kicinski [this message]
2023-10-18  0:30 ` patchwork-bot+netdevbpf

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=20231017171324.6c7c2986@kernel.org \
    --to=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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 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).