From: Hans de Goede <hdegoede@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Mark Gross <mark.gross@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the drivers-x86-fixes tree
Date: Mon, 18 Jan 2021 21:55:29 +0100 [thread overview]
Message-ID: <86f9149d-d824-99f4-2d73-620aef2fa699@redhat.com> (raw)
In-Reply-To: <20210119063909.3dd6f6a5@canb.auug.org.au>
Hi,
On 1/18/21 8:39 PM, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 19 Jan 2021 06:27:58 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> In commit
>>
>> 99d53ba0d0d9 ("platform/x86: hp-wmi: Don't log a warning on HPWMI_RET_UNKNOWN_COMMAND errors")
>>
>> Fixes tag
>>
>> Fixes: 81c93798ef3e ("platform/x86: hp-wmi: add support for thermal policy
>>
>> has these problem(s):
>>
>> - Subject has leading but no trailing parentheses
>> - Subject has leading but no trailing quotes
>
> This is also commit
>
> b96705325421 ("platform/x86: hp-wmi: Don't log a warning on HPWMI_RET_UNKNOWN_COMMAND errors")
>
> in the drivers-x86 tree.
Sorry about that, I've fixed it in both the drivers-x86-fixes and the regular
drivers-x86 trees.
Strange enough checkpatch does not catch this, while it does catch misformatted
commit references in the non tags part of the commit message. I will mail the
checkpatch maintainer about this.
Regards,
Hans
next prev parent reply other threads:[~2021-01-18 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 19:27 linux-next: Fixes tag needs some work in the drivers-x86-fixes tree Stephen Rothwell
2021-01-18 19:39 ` Stephen Rothwell
2021-01-18 20:55 ` Hans de Goede [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-04 21:50 Stephen Rothwell
2022-04-05 9:27 ` Hans de Goede
2019-04-16 21:17 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=86f9149d-d824-99f4-2d73-620aef2fa699@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mark.gross@intel.com \
--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).