From: Johannes Berg <johannes@sipsolutions.net>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: pull-request: ath-next-20260303
Date: Wed, 04 Mar 2026 12:34:31 +0100 [thread overview]
Message-ID: <6f10a9f5daea102dc2f7780b93b8f8f7e48025fc.camel@sipsolutions.net> (raw)
In-Reply-To: <18112483-1280-4ede-bd59-10cac700404e@oss.qualcomm.com>
Hi,
On Tue, 2026-03-03 at 08:34 -0800, Jeff Johnson wrote:
> > git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git tags/ath-next-20260303
I'm almost surprised this even still works, don't you use https://?
>
> 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.
Sure, that's fine, I often send almost a PR per week, so should be happy
to accept that too :)
johannes
prev parent reply other threads:[~2026-03-04 11: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
2026-03-04 11:34 ` Johannes Berg [this message]
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=6f10a9f5daea102dc2f7780b93b8f8f7e48025fc.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jeff.johnson@oss.qualcomm.com \
--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