From: Kalle Valo <kvalo@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Nagarajan Maran <quic_nmaran@quicinc.com>,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v5.18] ath11k: fix driver initialization failure with WoW unsupported hw
Date: Fri, 01 Apr 2022 14:28:18 +0300 [thread overview]
Message-ID: <87ee2hujot.fsf@kernel.org> (raw)
In-Reply-To: <2f25bb87e665488b30f6fdaa5877ad8b5b19da0a.camel@sipsolutions.net> (Johannes Berg's message of "Thu, 31 Mar 2022 13:59:04 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> On Thu, 2022-03-31 at 13:44 +0300, Kalle Valo wrote:
>> >
>> > Fixes: ba9177fcef21 ("Add basic WoW functionalities")
>>
>> Fixes tag is wrong, it should be:
>>
>> Fixes: ba9177fcef21 ("ath11k: Add basic WoW functionalities")
>>
>
> $ git config --global --add alias.fixes 'show -q --format=fixes'
> $ git config --global --add pretty.fixes 'Fixes: %h ("%s")'
> $ git config --global --add core.abbrev 12
> $ git fixes ba9177fcef21
> Fixes: ba9177fcef21 ("ath11k: Add basic WoW functionalities")
>
> :)
Hehe, really nice! I added this to the wiki:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#fixes_line_is_incorrect
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-04-01 11:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 7:31 [PATCH v5.18] ath11k: fix driver initialization failure with WoW unsupported hw Nagarajan Maran
2022-03-31 10:44 ` Kalle Valo
2022-03-31 10:56 ` Nagarajan Maran (QUIC)
2022-03-31 11:59 ` Johannes Berg
2022-03-31 16:37 ` Nagarajan Maran (QUIC)
2022-04-01 5:46 ` Kalle Valo
2022-04-01 14:03 ` Nagarajan Maran (QUIC)
2022-04-01 11:28 ` Kalle Valo [this message]
2022-04-01 11:51 ` Kalle Valo
2022-04-01 14:05 ` Nagarajan Maran (QUIC)
2022-04-05 8:12 ` Kalle Valo
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=87ee2hujot.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_nmaran@quicinc.com \
/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;
as well as URLs for NNTP newsgroup(s).