All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: ray.huang@amd.com, gautham.shenoy@amd.com, perry.yuan@amd.com,
	jserv@ccns.ncku.edu.tw, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/power/x86/amd_pstate_tracer: Fix python gnuplot package names
Date: Wed, 24 Sep 2025 00:21:01 +0800	[thread overview]
Message-ID: <aNLI7VBQc+NFrmo8@visitorckw-System-Product-Name> (raw)
In-Reply-To: <75046094-d3b7-49da-af8e-3747ae9ed272@amd.com>

Hi Mario,

On Mon, Aug 25, 2025 at 04:25:58PM -0500, Mario Limonciello wrote:
> On 8/24/2025 3:09 PM, Kuan-Wei Chiu wrote:
> > The prerequisites section listed non-existent packages
> > "phython-gnuplot" and "phython3-gnuplot", which may mislead users and
> > cause installation failures.
> > 
> > Update the names to the correct distribution package names
> > "python-gnuplot" and "python3-gnuplot", helping users avoid confusion
> > and saving time for those following the instructions.
> > 
> > Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
> 
> Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>

Thanks for your review!

Since the merge window is likely opening in less than a week and this
patch has already been submitted and reviewed for about a month, I
noticed it still hasn't shown up in linux-next.

May I ask how we plan to route this patch?

Regards,
Kuan-Wei

  reply	other threads:[~2025-09-23 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-24 20:09 [PATCH] tools/power/x86/amd_pstate_tracer: Fix python gnuplot package names Kuan-Wei Chiu
2025-08-25 21:25 ` Mario Limonciello
2025-09-23 16:21   ` Kuan-Wei Chiu [this message]
2025-09-23 18:44     ` Mario Limonciello

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=aNLI7VBQc+NFrmo8@visitorckw-System-Product-Name \
    --to=visitorckw@gmail.com \
    --cc=gautham.shenoy@amd.com \
    --cc=jserv@ccns.ncku.edu.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=perry.yuan@amd.com \
    --cc=ray.huang@amd.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.