From: Shuah Khan <skhan@linuxfoundation.org>
To: "John B. Wyatt IV" <jwyatt@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-pm@vger.kernel.org, Thomas Renninger <trenn@suse.com>,
Shuah Khan <shuah@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, John Kacur <jkacur@redhat.com>,
Tomas Glozar <tglozar@redhat.com>, Arnaldo Melo <acme@redhat.com>,
"John B. Wyatt IV" <sageofredondo@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 0/2][RFC] Add SWIG Bindings to libcpupower
Date: Wed, 21 Aug 2024 01:08:25 -0600 [thread overview]
Message-ID: <c7259d79-4e66-48c2-922c-f6ab88b3af69@linuxfoundation.org> (raw)
In-Reply-To: <ZsQ6XKQ4pRFYkGoS@rhfedora>
On 8/20/24 00:40, John B. Wyatt IV wrote:
> I wanted to follow up on this since I am close to sending out the v2 of
> this patchset.
>
> 3 points I wanted to raise:
>
> 1) Does everyone understand, is okay with the SWIG license, and wants to
> proceed with me sending in a more complete version of this as a candidate for
> upstreaming?
>
> 2) About maintainership: if I am to be the maintainer of this, how would
> myself and John Kacur be listed? As a CPU POWER MONITORING SUBSYSTEM
> maintainer, a separate category below it called CPU POWER MONITORING SUBSYSTEM
> PYTHON BINDINGS maintainer, or is not needed to be listed at this time?
>
> A quick search for bindings shows what I believe to be all of them for device
> tree. This may establish a new precedent.
>
> If I was to be added, I assume it would be a separate commit in the v2
> submission?
>
> 3) I had to comment out powercap_set_enabled
>
> SWIG reported this symbol not being found despite being in powercap.h. I did a
> quick search and was not able to find it's implementation in powercap.c. The
> get equivalent powercap_get_enabled is in powercap.c. Wanted to check on this
> just in case it is a bug or part of future functionality. I am assuming the
> latter; I would send it v2 with that declaration commented out with a note
> explaining it for users if there is no objection.
Yes please send a complete version for review.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-08-21 7:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 22:11 John B. Wyatt IV
2024-07-24 22:11 ` [PATCH 1/2] Add SWIG bindings files for libcpupower John B. Wyatt IV
2024-07-24 22:11 ` [PATCH 2/2] Include test_raw_pylibcpupower.py John B. Wyatt IV
2024-07-26 17:34 ` [PATCH 0/2][RFC] Add SWIG Bindings to libcpupower Shuah Khan
2024-07-30 20:48 ` Shuah Khan
2024-08-01 21:24 ` John B. Wyatt IV
2024-08-04 8:54 ` Greg Kroah-Hartman
2024-08-06 20:56 ` John B. Wyatt IV
2024-08-20 6:40 ` John B. Wyatt IV
2024-08-21 7:08 ` Shuah Khan [this message]
2024-08-22 3:25 ` Shuah Khan
2024-08-27 17:58 ` John B. Wyatt IV
2024-08-09 20:25 ` Arnaldo Carvalho de Melo
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=c7259d79-4e66-48c2-922c-f6ab88b3af69@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=acme@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkacur@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sageofredondo@gmail.com \
--cc=shuah@kernel.org \
--cc=tglozar@redhat.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®