From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: pull-request: ath-next-20260303
Date: Tue, 3 Mar 2026 08:34:25 -0800 [thread overview]
Message-ID: <18112483-1280-4ede-bd59-10cac700404e@oss.qualcomm.com> (raw)
In-Reply-To: <79e82568-e951-43f4-ac87-2319245a5490@oss.qualcomm.com>
On 3/3/2026 8:27 AM, Jeff Johnson wrote:
> The following changes since commit 8bf22c33e7a172fbc72464f4cc484d23a6b412ba:
>
> Merge tag 'net-7.0-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2026-02-19 10:39:08 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git tags/ath-next-20260303
>
> for you to fetch changes up to cf7cbf97c630c3414302945617b8ac405e2b0dd7:
>
> wifi: ath12k: Remove the unused argument from the Rx data path (2026-03-02 13:02:05 -0800)
>
> ----------------------------------------------------------------
> ath.git patches for v7.1 (PR #1)
>
> For ath12k:
> Add basic hwmon temperature reporting.
> Enable monitor mode on IPQ5332.
>
> Also a few small cleanups and bug fixes across ath drivers.
FYI the reason for the early PR is that I made the mistake of pulling some
patches into ath-next before I realized that Kees & Linux had applied the
treewide kmalloc_obj() feature, so now I need to merge so I can then fast
forward to wireless-next/main to pick that up. I don't want to take any more
ath-next changes until that is in place.
/jeff
next prev parent reply other threads:[~2026-03-03 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 16:27 pull-request: ath-next-20260303 Jeff Johnson
2026-03-03 16:34 ` Jeff Johnson [this message]
2026-03-04 11:34 ` Johannes Berg
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=18112483-1280-4ede-bd59-10cac700404e@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=johannes@sipsolutions.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox