X86 platform drivers
 help / color / mirror / Atom feed
From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "ilpo.jarvinen@linux.intel.com" <ilpo.jarvinen@linux.intel.com>
Cc: "hdegoede@redhat.com" <hdegoede@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 6.16-rc1
Date: Wed, 14 May 2025 13:38:37 +0000	[thread overview]
Message-ID: <b13c2eb837fb5eeea906befa4a4bae783fbde370.camel@intel.com> (raw)
In-Reply-To: <9a395011-090a-3b8b-ee78-fe33a7d06951@linux.intel.com>

On Wed, 2025-05-14 at 16:02 +0300, Ilpo Järvinen wrote:
> On Fri, 9 May 2025, Pandruvada, Srinivas wrote:
> 
> > Hi Hans and Ilpo,
> > 
> > This pull request is based on
> > https://kernel.googlesource.com/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86
> > review-ilpo-next
> > 
> > This has changes for SST-PP revision 2 support and uncore frequency
> > update for new generations of CPUs.
> > 
> > The following changes since commit
> > 83579675331059689e2869bf752ca9e17fadbd82:
> > 
> >   platform/x86: portwell-ec: Add GPIO and WDT driver for Portwell
> > EC
> > (2025-05-08 17:37:58 +0300)
> 
> Thanks Srinivas,
> 
> I've applied these now.
> 
> In the future, preferrably please try to base PRs on the for-next
> branch 

Sure. I will do next time.

Thanks,
Srinivas

> as review-ilpo-next is quite volatile an I do rewrite commits there
> on 
> relatively low bar. When you base something on review-ilpo-next, you 
> effectively end up tying my hands to keep those commits in 
> review-ilpo-next (or the PR needs to be rebased/respun).
> 


      reply	other threads:[~2025-05-14 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09 21:08 [GIT PULL]: tools/power/x86/intel-speed-select pull request for 6.16-rc1 Pandruvada, Srinivas
2025-05-14 13:02 ` Ilpo Järvinen
2025-05-14 13:38   ` Pandruvada, Srinivas [this message]

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=b13c2eb837fb5eeea906befa4a4bae783fbde370.camel@intel.com \
    --to=srinivas.pandruvada@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    /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