Linux Power Management development
 help / color / mirror / Atom feed
From: Min-Hua Chen <minhuadotchen@gmail.com>
To: skhan@linuxfoundation.org
Cc: jkacur@redhat.com, jwyatt@redhat.com,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	minhuadotchen@gmail.com, shuah@kernel.org, trenn@suse.com
Subject: Re: [RFC PATCH for-next] pm: cpupower: rename raw_pylibcpupower.i
Date: Fri, 13 Sep 2024 06:55:19 +0800	[thread overview]
Message-ID: <20240912225519.119392-1-minhuadotchen@gmail.com> (raw)
In-Reply-To: <b64402ad-4c0d-4f5f-939b-4be1a7855e4a@linuxfoundation.org>

AFAIK,
raw_pylibcpupower.i is not a generated file, it is a interface file
for swig.

The *.i file extension is also used for pre-processor output
(single target build) and all *.i files are removed by 'make mrproper',
including raw_pylibcpupower.i (should not be removed).


thanks,
Min-Hua
>
>
>> I have reviewed and tested and this. I am good with it being a stopgap.
>
>I am okay with the stopgap, but I do want i explore other solutions.
>> 
>> Please send the non-rfc patch.
>> 
>> Thank you for reporting and sending a patch for this Min-Hua.
>> 
>> Reviewed-by: John B. Wyatt IV <jwyatt@redhat.com>
>> Reviewed-by: John B. Wyatt IV <sageofredondo@gmail.com>
>> Tested-by: John B. Wyatt IV <jwyatt@redhat.com>
>> Tested-by: John B. Wyatt IV <sageofredondo@gmail.com>
>> 

  reply	other threads:[~2024-09-12 22:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 12:50 [RFC PATCH for-next] pm: cpupower: rename raw_pylibcpupower.i Min-Hua Chen
2024-09-12 16:31 ` Shuah Khan
2024-09-12 17:36   ` John B. Wyatt IV
2024-09-12 20:03     ` Shuah Khan
2024-09-12 22:55       ` Min-Hua Chen [this message]
2024-09-13 16:35         ` John B. Wyatt IV
2024-09-13 16:45           ` Shuah Khan
2024-09-12 22:49     ` Min-Hua Chen

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=20240912225519.119392-1-minhuadotchen@gmail.com \
    --to=minhuadotchen@gmail.com \
    --cc=jkacur@redhat.com \
    --cc=jwyatt@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=trenn@suse.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