From: Alejandro Colomar <alx@kernel.org>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>, Greg KH <greg@kroah.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
linux-wireless@vger.kernel.org,
"Rajkumar Manoharan" <rmanohar@qti.qualcomm.com>,
"John W. Linville" <linville@tuxdriver.com>,
"Greg KH" <greg@kroah.com>
Subject: Re: [PATCH v1] wifi: ath9k: Fix typo
Date: Wed, 25 Feb 2026 00:23:48 +0100 [thread overview]
Message-ID: <aZ4xt0TIscdxhseW@devuan> (raw)
In-Reply-To: <828b4d9b-268f-4f7c-ab7c-51aa49c0bde2@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 2609 bytes --]
Hi Jeff, Greg,
On 2026-02-24T15:09:05-0800, Jeff Johnson wrote:
> >> I don't know where I keep the patch, so I'd have to apply it from the
> >> email to resend. Could you amend it yourself?
> >
> > sure, I'll amend the patch in my pending branch
Thanks!
> I've also updated the Fixes tag to meet the expected format...
> Fixes: c4dc0d040e35 ("ath9k: Fetch appropriate operating channel context")
Greg, I CCed you in the man-pages thread where I discussed adding the
commit date to the Fixes tags. I was interested in your opinion, and
also think this could be useful in the kernel.
<https://lore.kernel.org/linux-man/3a656e90329f26d743d0904f56ae847951c852c7.1770150003.git.alx@kernel.org/>
Do you have any opinion about this? Should I send a mail to some kernel
mailing list to propose its use in the kernel?
The format I used is documented in the Linux man-pages here:
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTING.d/patches/trailer#n16>
Fixes
Add 'Fixes:' tags as necessary. 'Fixes:' trailer fields should
have the following format.
Fixes: 12-char-hash ([author-date,] commit-date; "subject")
where the author date is optional, and only included if it's
somehow important. The commit date is often more important, as
it's sorted, and thus can be used to find (with a binary search)
a commit whose hash and subject may have collisions. For
example:
Fixes: bb509e6fcbae (2020-10-16; "kernel_lockdown.7: New page documenting the Kernel Lockdown feature")
See <CONTRIBUTING.d/git> for how to configure the alias.ref and
alias.ref2 git aliases. The commit references can be produced
with them.
$ git ref bb509e6fc
bb509e6fcbae (2020-10-16; "kernel_lockdown.7: New page documenting the Kernel Lockdown feature")
and here:
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTING.d/git#n46>
alias.ref, alias.ref2
To produce git commit references, the following git aliases are
useful.
$ git config --global alias.ref \
"show -s --format=tformat:'%C(auto)%h (%cs%x3B \"%s\")%C(reset)'"
$ git config --global alias.ref2 \
"show -s --format=tformat:'%C(auto)%h (%as, %cs%x3B \"%s\")%C(reset)'"
core.abbrev
Use 12 characters in abbreviated hashes.
$ git config --global core.abbrev 12
The Fixes tag I used in this particular patch was
Fixes: c4dc0d040e35 (2014-06-19; "ath9k: Fetch appropriate operating channel context")
Have a lovely night!
Alex
>
> >
> > /jeff
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-02-24 23:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 22:25 [PATCH v1] wifi: ath9k: Fix typo Alejandro Colomar
2026-02-23 15:17 ` Toke Høiland-Jørgensen
2026-02-24 18:45 ` Jeff Johnson
2026-02-24 21:27 ` Alejandro Colomar
2026-02-24 21:34 ` Jeff Johnson
2026-02-24 22:55 ` Alejandro Colomar
2026-02-24 23:07 ` Jeff Johnson
2026-02-24 23:09 ` Jeff Johnson
2026-02-24 23:23 ` Alejandro Colomar [this message]
2026-02-25 0:04 ` Jeff Johnson
2026-02-25 0:10 ` Alejandro Colomar
2026-02-24 21:37 ` Greg KH
2026-02-24 22:52 ` Alejandro Colomar
2026-02-26 21:29 ` 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=aZ4xt0TIscdxhseW@devuan \
--to=alx@kernel.org \
--cc=greg@kroah.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rmanohar@qti.qualcomm.com \
--cc=toke@toke.dk \
/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