From: Johannes Berg <johannes@sipsolutions.net>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
linux-wireless@vger.kernel.org
Cc: ath10k@lists.infradead.org, ath11k@lists.infradead.org,
ath12k@lists.infradead.org, jjohnson@kernel.org
Subject: Re: pull-request: ath-current-20260113
Date: Wed, 14 Jan 2026 10:47:59 +0100 [thread overview]
Message-ID: <33d998cc225a7aeef4731ebc53c28a32b241ca7e.camel@sipsolutions.net> (raw)
In-Reply-To: <98386125-c0bb-495e-b2ba-2765aaed19d8@oss.qualcomm.com> (sfid-20260113_183400_758847_B264F10B)
On Tue, 2026-01-13 at 09:33 -0800, Jeff Johnson wrote:
>
> Note to maintainers:
>
> This tag includes:
> 31707572108d ("wifi: ath12k: Fix wrong P2P device link id issue")
>
> That commit contains the following:
>
> Note to linux-next and netdev maintainers:
I'm a bit on the fence about this, I hadn't thought about it on the
prior -next PR much, but I feel like this is a process thing that
shouldn't get recorded in the tag for posterity?
I do appreciate the inclusion of this (*especially* when I won't notice
the merge conflict myself), but I tend to think it should be in the
email rather than the tag message, since the latter is something I use
for the merge commit message and it gets recorded.
Either way I have to preserve it manually to the next level, so it
doesn't really help all that much, although I guess in the tag there's a
chance I could see it again when preparing my PR.
I'll just edit it out this time I think since it's so long, but you can
complain and convince me otherwise for the next time ;-)
johannes
next prev parent reply other threads:[~2026-01-14 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 17:33 pull-request: ath-current-20260113 Jeff Johnson
2026-01-14 9:47 ` Johannes Berg [this message]
2026-01-14 15:13 ` Jeff Johnson
2026-01-14 17:08 ` Johannes Berg
2026-01-14 17:51 ` Jeff Johnson
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=33d998cc225a7aeef4731ebc53c28a32b241ca7e.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@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