From: Jon Hunter <jonathanh@nvidia.com>
To: Dmitry Osipenko <digetx@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: tegra: Enable CPUFREQ userspace governor
Date: Mon, 13 Jul 2020 09:27:28 +0100 [thread overview]
Message-ID: <5f777eab-5584-5e4b-ff81-2a9c6522ddad@nvidia.com> (raw)
In-Reply-To: <857e47b0-e226-72b7-3855-f668c49c0739@gmail.com>
On 12/07/2020 11:48, Dmitry Osipenko wrote:
> 12.07.2020 13:31, Jon Hunter пишет:
>> Enable the CPUFREQ userspace governor in the tegra_defconfig so that
>> we can test CPUFREQ with the userspace governor with this configuration
>> on 32-bit Tegra devices.
>>
>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>> ---
>> The_Yellow_Theme_24-192.wav | 0
>> arch/arm/configs/tegra_defconfig | 1 +
>> 2 files changed, 1 insertion(+)
>
>> create mode 100644 The_Yellow_Theme_24-192.wav
>>
>> diff --git a/The_Yellow_Theme_24-192.wav b/The_Yellow_Theme_24-192.wav
>> new file mode 100644
>
> Hello, Jon! This looks like something unrelated to this patch :)
Ugh indeed. Thanks. I will fix this. Jon
--
nvpublic
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-13 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 10:31 [PATCH] ARM: tegra: Enable CPUFREQ userspace governor Jon Hunter
2020-07-12 10:48 ` Dmitry Osipenko
2020-07-13 8:27 ` Jon Hunter [this message]
2020-07-13 14:41 ` [RESEND PATCH] " Jon Hunter
2020-07-14 8:32 ` Thierry Reding
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=5f777eab-5584-5e4b-ff81-2a9c6522ddad@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=digetx@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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).