From: Viresh Kumar <viresh.kumar@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rajendra Nayak <rnayak@codeaurora.org>
Subject: Re: linux-next: Fixes tag needs some work in the pm tree
Date: Thu, 20 Aug 2020 10:25:26 +0530 [thread overview]
Message-ID: <20200820045526.rj2qs6uodje4josp@vireshk-i7> (raw)
In-Reply-To: <20200820080117.6d7bcf00@canb.auug.org.au>
On 20-08-20, 08:01, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> ceac7fc18ac7 ("opp: Enable resources again if they were disabled earlier")
>
> Fixes tag
>
> Fixes: cd7ea582 ("opp: Make dev_pm_opp_set_rate() handle freq = 0 to drop performance votes")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
> Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
> or later) just making sure it is not set (or set to "auto").
It came from the author and I failed to verify it :(
Rafael: Do you want me to resend the pull request with this fixed ? Or
something else ?
--
viresh
next prev parent reply other threads:[~2020-08-20 4:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 22:01 linux-next: Fixes tag needs some work in the pm tree Stephen Rothwell
2020-08-20 4:55 ` Viresh Kumar [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
2021-04-07 22:38 Stephen Rothwell
2021-04-08 7:52 ` Vitaly Kuznetsov
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=20200820045526.rj2qs6uodje4josp@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rnayak@codeaurora.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).