From: Johannes Berg <johannes@sipsolutions.net>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH net-next] wifi: Fix typos
Date: Thu, 24 Jul 2025 09:03:01 +0200 [thread overview]
Message-ID: <881bf7877b72ad05098f50262e546d3cfd87fb55.camel@sipsolutions.net> (raw)
In-Reply-To: <1d5f27a4-5407-4cf2-bd52-1ee75a4050ef@oss.qualcomm.com>
On Wed, 2025-07-23 at 18:41 -0700, Jeff Johnson wrote:
>
> Even better would be to split out the patches that have dedicated subordinate
> maintainer trees (such as ath.git for the ath5k and ath10k changes) unless
> Johannes wants to take this entire set.
I'll just take it, no point splitting it.
johannes
prev parent reply other threads:[~2025-07-24 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 20:17 Bjorn Helgaas
2025-07-24 1:41 ` Jeff Johnson
2025-07-24 7:03 ` 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=881bf7877b72ad05098f50262e546d3cfd87fb55.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®