Message ID | cbd2f7727419301acc17c4479b81637829db4c9f.camel@intel.com (mailing list archive) |
---|---|
State | Deferred, archived |
Headers | show |
Series | [GIT,PULL] : tools/power/x86/intel-speed-select pull request for 5.18-rc1 | expand |
<added the thermal maintainers to the To: list> On 2/15/22 20:21, Pandruvada, Srinivas wrote: > Hi Hans, > > Please check the pull request for intel-speed-select tool. > > To build the tool, we have dependency on linux-next commit > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thermal?h=next-20220215&id=e4b1eb24ce5a696ef7229f9926ff34d7502f0582 Hmm, that means that if I merge this into pdx86/for-next which is based on 5.17-rc1 then this won't build, which is bad. So I'm going to either need some immutable branch from the thermal maintainers to merge into pdx86/for-next, or we can just merge the intel-speed-select changes through the thermal tree for the 5.18-rc1 merge window. Either way is fine with me. Regards, Hans > > > The following changes since commit > ae707d0eb707b5fc658e870dbd8b21887b0a5240: > > platform/x86: intel_cht_int33fe: Move to intel directory (2022-02-11 > 10:52:56 +0100) > > are available in the Git repository at: > > https://github.com/spandruvada/linux-kernel.git intel-sst > > for you to fetch changes up to > 9aa7f0d5fe526cb9ceeea0787db0dc1c081bc61d: > > tools/power/x86/intel-speed-select: v1.12 release (2022-02-15 > 11:12:55 -0800) > > ---------------------------------------------------------------- > Srinivas Pandruvada (3): > tools/power/x86/intel-speed-select: OOB daemon mode > tools/power/x86/intel-speed-select: HFI support > tools/power/x86/intel-speed-select: v1.12 release > > tools/power/x86/intel-speed-select/Build | 2 +- > tools/power/x86/intel-speed-select/Makefile | 10 +++- > tools/power/x86/intel-speed-select/hfi-events.c | 309 > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > ++++++++++++++++++++++++++++ > tools/power/x86/intel-speed-select/isst-config.c | 54 ++++++++++++++- > --- > tools/power/x86/intel-speed-select/isst-daemon.c | 244 > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > +++++++ > tools/power/x86/intel-speed-select/isst.h | 13 +++++ > 6 files changed, 617 insertions(+), 15 deletions(-) > create mode 100644 tools/power/x86/intel-speed-select/hfi-events.c > create mode 100644 tools/power/x86/intel-speed-select/isst-daemon.c > > Thanks, > Srinivas >
On Thu, Feb 17, 2022 at 5:39 PM Hans de Goede <hdegoede@redhat.com> wrote: > > <added the thermal maintainers to the To: list> > > On 2/15/22 20:21, Pandruvada, Srinivas wrote: > > Hi Hans, > > > > Please check the pull request for intel-speed-select tool. > > > > To build the tool, we have dependency on linux-next commit > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thermal?h=next-20220215&id=e4b1eb24ce5a696ef7229f9926ff34d7502f0582 > > Hmm, that means that if I merge this into pdx86/for-next which > is based on 5.17-rc1 then this won't build, which is bad. > > So I'm going to either need some immutable branch from the > thermal maintainers to merge into pdx86/for-next, > or we can just merge the intel-speed-select changes through > the thermal tree for the 5.18-rc1 merge window. That can be done. > Either way is fine with me. OK
Hi Rafael, On 2/17/22 17:41, Rafael J. Wysocki wrote: > On Thu, Feb 17, 2022 at 5:39 PM Hans de Goede <hdegoede@redhat.com> wrote: >> >> <added the thermal maintainers to the To: list> >> >> On 2/15/22 20:21, Pandruvada, Srinivas wrote: >>> Hi Hans, >>> >>> Please check the pull request for intel-speed-select tool. >>> >>> To build the tool, we have dependency on linux-next commit >>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thermal?h=next-20220215&id=e4b1eb24ce5a696ef7229f9926ff34d7502f0582 >> >> Hmm, that means that if I merge this into pdx86/for-next which >> is based on 5.17-rc1 then this won't build, which is bad. >> >> So I'm going to either need some immutable branch from the >> thermal maintainers to merge into pdx86/for-next, >> or we can just merge the intel-speed-select changes through >> the thermal tree for the 5.18-rc1 merge window. > > That can be done. > >> Either way is fine with me. > > OK Thanks for the quick reply. If you don't have any preference I think it makes sense to merge the intel-speed-select changes through the thermal tree for the 5.18-rc1 merge window, as the changes tot he tool build on kernel work done there. Regards, Hans
On Thu, Feb 17, 2022 at 5:43 PM Hans de Goede <hdegoede@redhat.com> wrote: > > Hi Rafael, > > On 2/17/22 17:41, Rafael J. Wysocki wrote: > > On Thu, Feb 17, 2022 at 5:39 PM Hans de Goede <hdegoede@redhat.com> wrote: > >> > >> <added the thermal maintainers to the To: list> > >> > >> On 2/15/22 20:21, Pandruvada, Srinivas wrote: > >>> Hi Hans, > >>> > >>> Please check the pull request for intel-speed-select tool. > >>> > >>> To build the tool, we have dependency on linux-next commit > >>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thermal?h=next-20220215&id=e4b1eb24ce5a696ef7229f9926ff34d7502f0582 > >> > >> Hmm, that means that if I merge this into pdx86/for-next which > >> is based on 5.17-rc1 then this won't build, which is bad. > >> > >> So I'm going to either need some immutable branch from the > >> thermal maintainers to merge into pdx86/for-next, > >> or we can just merge the intel-speed-select changes through > >> the thermal tree for the 5.18-rc1 merge window. > > > > That can be done. > > > >> Either way is fine with me. > > > > OK > > Thanks for the quick reply. > > If you don't have any preference I think it makes sense to merge > the intel-speed-select changes through the thermal tree for > the 5.18-rc1 merge window, as the changes tot he tool build on > kernel work done there. Right. Srinivas, please rebase this on top of commit c95aa2bab974 (the head of my thermal-hfi branch) and resubmit with a CC to linux-pm. Alternatively, you can just send a patch for me to apply.
On Thu, 2022-02-17 at 19:20 +0100, Rafael J. Wysocki wrote: > On Thu, Feb 17, 2022 at 5:43 PM Hans de Goede <hdegoede@redhat.com> > wrote: > > > > Hi Rafael, > > > > On 2/17/22 17:41, Rafael J. Wysocki wrote: > > > On Thu, Feb 17, 2022 at 5:39 PM Hans de Goede > > > <hdegoede@redhat.com> wrote: > > > > > > > > <added the thermal maintainers to the To: list> > > > > > > > > On 2/15/22 20:21, Pandruvada, Srinivas wrote: > > > > > Hi Hans, > > > > > > > > > > Please check the pull request for intel-speed-select tool. > > > > > > > > > > To build the tool, we have dependency on linux-next commit > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thermal?h=next-20220215&id=e4b1eb24ce5a696ef7229f9926ff34d7502f0582 > > > > > > > > Hmm, that means that if I merge this into pdx86/for-next which > > > > is based on 5.17-rc1 then this won't build, which is bad. > > > > > > > > So I'm going to either need some immutable branch from the > > > > thermal maintainers to merge into pdx86/for-next, > > > > or we can just merge the intel-speed-select changes through > > > > the thermal tree for the 5.18-rc1 merge window. > > > > > > That can be done. > > > > > > > Either way is fine with me. > > > > > > OK > > > > Thanks for the quick reply. > > > > If you don't have any preference I think it makes sense to merge > > the intel-speed-select changes through the thermal tree for > > the 5.18-rc1 merge window, as the changes tot he tool build on > > kernel work done there. > > Right. > > Srinivas, please rebase this on top of commit c95aa2bab974 (the head > of my thermal-hfi branch) and resubmit with a CC to linux-pm. > I see these branches at https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git remotes/rafael-pm/acpi remotes/rafael-pm/bleeding-edge remotes/rafael-pm/devprop remotes/rafael-pm/linux-next remotes/rafael-pm/master remotes/rafael-pm/pm remotes/rafael-pm/pnp remotes/rafael-pm/testing remotes/rafael-pm/thermal There is no thermal-hfi publicly visible. Is this OK to rebase on top of thermal or linux-next? Thanks, Srinivas > Alternatively, you can just send a patch for me to apply.
On Thu, Feb 17, 2022 at 7:36 PM Pandruvada, Srinivas <srinivas.pandruvada@intel.com> wrote: > > On Thu, 2022-02-17 at 19:20 +0100, Rafael J. Wysocki wrote: > > On Thu, Feb 17, 2022 at 5:43 PM Hans de Goede <hdegoede@redhat.com> > > wrote: > > > > > > Hi Rafael, > > > > > > On 2/17/22 17:41, Rafael J. Wysocki wrote: > > > > On Thu, Feb 17, 2022 at 5:39 PM Hans de Goede > > > > <hdegoede@redhat.com> wrote: > > > > > > > > > > <added the thermal maintainers to the To: list> > > > > > > > > > > On 2/15/22 20:21, Pandruvada, Srinivas wrote: > > > > > > Hi Hans, > > > > > > > > > > > > Please check the pull request for intel-speed-select tool. > > > > > > > > > > > > To build the tool, we have dependency on linux-next commit > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thermal?h=next-20220215&id=e4b1eb24ce5a696ef7229f9926ff34d7502f0582 > > > > > > > > > > Hmm, that means that if I merge this into pdx86/for-next which > > > > > is based on 5.17-rc1 then this won't build, which is bad. > > > > > > > > > > So I'm going to either need some immutable branch from the > > > > > thermal maintainers to merge into pdx86/for-next, > > > > > or we can just merge the intel-speed-select changes through > > > > > the thermal tree for the 5.18-rc1 merge window. > > > > > > > > That can be done. > > > > > > > > > Either way is fine with me. > > > > > > > > OK > > > > > > Thanks for the quick reply. > > > > > > If you don't have any preference I think it makes sense to merge > > > the intel-speed-select changes through the thermal tree for > > > the 5.18-rc1 merge window, as the changes tot he tool build on > > > kernel work done there. > > > > Right. > > > > Srinivas, please rebase this on top of commit c95aa2bab974 (the head > > of my thermal-hfi branch) and resubmit with a CC to linux-pm. > > > I see these branches at > https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git > > remotes/rafael-pm/acpi > remotes/rafael-pm/bleeding-edge > remotes/rafael-pm/devprop > remotes/rafael-pm/linux-next > remotes/rafael-pm/master > remotes/rafael-pm/pm > remotes/rafael-pm/pnp > remotes/rafael-pm/testing > remotes/rafael-pm/thermal > > There is no thermal-hfi publicly visible. Is this OK to rebase on top > of thermal or linux-next? thermal-hfi should be visible now.