From: Dmitry Osipenko <digetx@gmail.com>
To: Jason Wang <wangborong@cdjrlc.com>, daniel.lezcano@linaro.org
Cc: rafael@kernel.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, linux-pm@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpuidle: tegra: fix typo in a comment
Date: Tue, 14 Dec 2021 09:28:27 +0300 [thread overview]
Message-ID: <1249c2ae-a7f0-3313-5fb1-06840a4f703b@gmail.com> (raw)
In-Reply-To: <be88a80f-251f-638d-bf29-a0423db53e06@gmail.com>
14.12.2021 09:02, Dmitry Osipenko пишет:
> 12.12.2021 06:31, Jason Wang пишет:
>> The double `that' in the comment in line 275 is repeated. Remove one
>> of them from the comment.
>>
>> Signed-off-by: Jason Wang <wangborong@cdjrlc.com>
>> ---
>> drivers/cpuidle/cpuidle-tegra.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/cpuidle/cpuidle-tegra.c b/drivers/cpuidle/cpuidle-tegra.c
>> index 9845629aeb6d..93ed4b8e164a 100644
>> --- a/drivers/cpuidle/cpuidle-tegra.c
>> +++ b/drivers/cpuidle/cpuidle-tegra.c
>> @@ -272,7 +272,7 @@ static int tegra114_enter_s2idle(struct cpuidle_device *dev,
>> * LP2 | C7 (CPU core power gating)
>> * LP2 | CC6 (CPU cluster power gating)
>> *
>> - * Note that that the older CPUIDLE driver versions didn't explicitly
>> + * Note that the older CPUIDLE driver versions didn't explicitly
>> * differentiate the LP2 states because these states either used the same
>> * code path or because CC6 wasn't supported.
>> */
>>
>
> This might be a candidate for <trivial@kernel.org>.
>
> https://www.kernel.org/doc/html/latest/process/submitting-patches.html#select-the-recipients-for-your-patch
>
Although, probably not, because documentation should mean only
Documentation/.
prev parent reply other threads:[~2021-12-14 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 3:31 [PATCH] cpuidle: tegra: fix typo in a comment Jason Wang
2021-12-14 6:02 ` Dmitry Osipenko
2021-12-14 6:28 ` Dmitry Osipenko [this message]
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=1249c2ae-a7f0-3313-5fb1-06840a4f703b@gmail.com \
--to=digetx@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=wangborong@cdjrlc.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