From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: Fixes tag needs some work in the pm tree
Date: Thu, 08 Apr 2021 09:52:00 +0200 [thread overview]
Message-ID: <87zgy9b4db.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20210408083836.39c4063a@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> In commit
>
> fa26d0c778b4 ("ACPI: processor: Fix build when CONFIG_ACPI_PROCESSOR=m")
>
> Fixes tag
>
> Fixes: 8cdddd182bd7 ("CPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()")
"A" in "ACPI" seems to be missing
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
This is an extremely unlucky fix :-(
--
Vitaly
next prev parent reply other threads:[~2021-04-08 7:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 22:38 linux-next: Fixes tag needs some work in the pm tree Stephen Rothwell
2021-04-08 7:52 ` Vitaly Kuznetsov [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-06 22:05 Stephen Rothwell
2024-02-25 21:38 Stephen Rothwell
2023-01-24 20:42 Stephen Rothwell
2023-01-11 21:16 Stephen Rothwell
2022-10-16 3:44 Stephen Rothwell
2022-05-19 23:02 Stephen Rothwell
2020-08-19 22:01 Stephen Rothwell
2020-08-20 4:55 ` Viresh Kumar
2020-03-04 20:53 Stephen Rothwell
2019-12-17 20:17 Stephen Rothwell
2019-10-14 20:59 Stephen Rothwell
2019-10-15 10:08 ` Rafael J. Wysocki
2019-09-10 14:33 Stephen Rothwell
2019-09-11 7:27 ` Heikki Krogerus
2019-09-11 17:17 ` Rafael J. Wysocki
2019-09-12 7:40 ` Heikki Krogerus
2019-07-10 11:26 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=87zgy9b4db.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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).