From: Kalle Valo <kvalo@codeaurora.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Wireless <linux-wireless@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Subject: Re: linux-next: Fixes tag needs some work in the wireless-drivers-next tree
Date: Wed, 19 Aug 2020 09:52:47 +0300 [thread overview]
Message-ID: <87y2mbi0u8.fsf@codeaurora.org> (raw)
In-Reply-To: <20200819083359.67f45112@canb.auug.org.au> (Stephen Rothwell's message of "Wed, 19 Aug 2020 08:33:59 +1000")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> In commit
>
> 3b9fb6791e71 ("wcn36xx: Fix reported 802.11n rx_highest rate wcn3660/wcn3680")
>
> Fixes tag
>
> Fixes: 8e84c2582169 ("wcn36xx: mac80211 driver for Qualcomm WCN3660/WCN3680
>
> has these problem(s):
>
> - Subject has leading but no trailing parentheses
> - Subject has leading but no trailing quotes
>
> Please do not split Fixes tags over more that one line. Also, keep all
> the commit message tags together at the end of the message.
Doh, I have checked carefully the commit ids but of course I missed
checking the trailing. I really need to automate this. Stephen, are your
scripts checking these available somewhere?
But I'll leave this as is, no point of rebasing just because of this.
Thanks for the report.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-08-19 6:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 22:33 linux-next: Fixes tag needs some work in the wireless-drivers-next tree Stephen Rothwell
2020-08-19 6:52 ` Kalle Valo [this message]
2020-08-19 8:13 ` Stephen Rothwell
2020-09-24 16:11 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2020-08-02 22:03 Stephen Rothwell
2020-08-04 13:17 ` Kalle Valo
2020-07-14 10:59 Stephen Rothwell
2020-07-14 17:49 ` Kalle Valo
2020-05-18 13:01 Stephen Rothwell
2020-05-19 8:50 ` Kalle Valo
2020-04-14 22:08 Stephen Rothwell
2020-04-15 0:36 ` Larry Finger
2020-04-15 1:06 ` Stephen Rothwell
2020-04-15 4:45 ` Kalle Valo
2020-01-27 0:42 Stephen Rothwell
2020-01-29 14:05 ` Kalle Valo
2019-07-01 21:33 Stephen Rothwell
2019-07-02 4:26 ` dundi
2019-06-30 21:44 Stephen Rothwell
2019-07-01 10:35 ` Lorenzo Bianconi
2019-05-27 21:48 Stephen Rothwell
2019-05-01 21:50 Stephen Rothwell
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=87y2mbi0u8.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=bryan.odonoghue@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).