All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>,
	"Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	"mgross@linux.intel.com" <mgross@linux.intel.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Zhang Rui <rui.zhang@intel.com>,
	"srinivas.pandruvada@linux.intel.com" 
	<srinivas.pandruvada@linux.intel.com>,
	"prarit@redhat.com" <prarit@redhat.com>,
	"platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>
Subject: Re: [GIT PULL]: tools/power/x86/intel-speed-select pull request for 5.18-rc1
Date: Thu, 17 Feb 2022 19:20:48 +0100	[thread overview]
Message-ID: <CAJZ5v0hmBwziRS7uMjK+CAz-D1CuyCA4dt3n0QPc62Uy1MgUpQ@mail.gmail.com> (raw)
In-Reply-To: <5ce192a8-ced8-0bf1-6825-d65cacfc8b3e@redhat.com>

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.

  reply	other threads:[~2022-02-17 18:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 19:21 [GIT PULL]: tools/power/x86/intel-speed-select pull request for 5.18-rc1 Pandruvada, Srinivas
2022-02-17 16:39 ` Hans de Goede
2022-02-17 16:41   ` Rafael J. Wysocki
2022-02-17 16:43     ` Hans de Goede
2022-02-17 18:20       ` Rafael J. Wysocki [this message]
2022-02-17 18:36         ` Pandruvada, Srinivas
2022-02-17 18:51           ` Rafael J. Wysocki
2022-02-17 19:07 Pandruvada, Srinivas
2022-02-17 19:28 ` Rafael J. Wysocki
2022-02-17 19:31   ` Pandruvada, Srinivas

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=CAJZ5v0hmBwziRS7uMjK+CAz-D1CuyCA4dt3n0QPc62Uy1MgUpQ@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=hdegoede@redhat.com \
    --cc=mgross@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=rui.zhang@intel.com \
    --cc=srinivas.pandruvada@intel.com \
    --cc=srinivas.pandruvada@linux.intel.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.