From: Chanwoo Choi <cw00.choi@samsung.com>
To: Sasha Levin <sashal@kernel.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: chanwoo@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] PM / devfrq: Fix indentaion of devfreq_summary debugfs node
Date: Fri, 24 Jul 2020 17:13:54 +0900 [thread overview]
Message-ID: <41a5d612-ac02-ff22-84ad-9e2138b53b43@samsung.com> (raw)
In-Reply-To: <20200717170847.F18AB207DD@mail.kernel.org>
Hi,
On 7/18/20 2:08 AM, Sasha Levin wrote:
> Hi
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag
> fixing commit: 66d0e797bf09 ("Revert "PM / devfreq: Modify the device name as devfreq(X) for sysfs"").
>
> The bot has tested the following trees: v5.7.8, v5.4.51, v4.19.132, v4.14.188.
>
> v5.7.8: Build OK!
> v5.4.51: Failed to apply! Possible dependencies:
> 490a421bc575d ("PM / devfreq: Add debugfs support with devfreq_summary file")
>
> v4.19.132: Failed to apply! Possible dependencies:
> 490a421bc575d ("PM / devfreq: Add debugfs support with devfreq_summary file")
>
> v4.14.188: Failed to apply! Possible dependencies:
> 490a421bc575d ("PM / devfreq: Add debugfs support with devfreq_summary file")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
>
The fixes commit was merged to v5.6-rc4. As your test result,
it was possible to build above v5.6. It is not problem. Thanks for your testing.
- 66d0e797bf09 ("Revert "PM / devfreq: Modify the device name as devfreq(X) for sysfs"").
--
Best Regards,
Chanwoo Choi
Samsung Electronics
next prev parent reply other threads:[~2020-07-24 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200713071942epcas1p14a9a1d2017e2e5005f7146f5bed09c82@epcas1p1.samsung.com>
2020-07-13 7:31 ` Chanwoo Choi
2020-07-17 17:08 ` Sasha Levin
2020-07-24 8:13 ` Chanwoo Choi [this message]
2020-07-27 2:30 ` Chanwoo Choi
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=41a5d612-ac02-ff22-84ad-9e2138b53b43@samsung.com \
--to=cw00.choi@samsung.com \
--cc=chanwoo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®