From: Jonathan Corbet <corbet@lwn.net>
To: Mario Limonciello <superm1@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Bhaskar Chowdhury <unixbhaskar@gmail.com>,
ray.huang@amd.com, perry.yuan@amd.com, kprateek.nayak@amd.com,
skhan@linuxfoundation.org, linux-pm@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] Doc: admin-guide: pm: Remove unnecessary backticks and fix a spell
Date: Fri, 14 Aug 2026 12:38:46 -0600 [thread overview]
Message-ID: <87se4geedl.fsf@trenco.lwn.net> (raw)
In-Reply-To: <776ad089-8d4c-4c85-b6b3-a04cae5cb5e4@kernel.org>
Mario Limonciello <superm1@kernel.org> writes:
> On 8/14/26 12:40, Jonathan Corbet wrote:
>> Mario Limonciello <superm1@kernel.org> writes:
>>
>>> On 8/14/26 07:58, Randy Dunlap wrote:
>>>>
>>>>
>>>> On 8/14/26 2:51 AM, Bhaskar Chowdhury wrote:
>>>>> One,
>>>>> Removed the superfluous backticks in the sentence.
>>>>>
>>>>> And second,
>>>>>
>>>>> s/peferred/preferred/
>>>>>
>>>>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>>>>
>>>> Acked-by: Randy Dunlap <rdunlap@infradead.org>
>>>> Thanks.
>>> Acked-by: Mario Limonciello (AMD) <superm1@kernel.org>
>>>
>>> Since this is pure docs should it go through docs tree? If not I'm fine
>>> to take it through amd-pstate next cycle.
>>
>> Up to you. I was leaving it because Rafael tends to pick up PM stuff,
>> but I'm happy to pick it up if you like, just let me know.
>>
>> Thanks,
>>
>> jon
>
> I'd say go ahead and grab this. There's no matching code changes and
> this doesn't change frequently.
OK, done, thanks.
jon
prev parent reply other threads:[~2026-08-14 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 9:51 [PATCH V2] Doc: admin-guide: pm: Remove unnecessary backticks and fix a spell Bhaskar Chowdhury
2026-08-14 12:58 ` Randy Dunlap
2026-08-14 16:31 ` Mario Limonciello
2026-08-14 17:40 ` Jonathan Corbet
2026-08-14 17:46 ` Mario Limonciello
2026-08-14 18:38 ` Jonathan Corbet [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=87se4geedl.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=kprateek.nayak@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=perry.yuan@amd.com \
--cc=ray.huang@amd.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=superm1@kernel.org \
--cc=unixbhaskar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.