Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	rodrigo.vivi@intel.com, intel-xe@lists.freedesktop.org,
	anshuman.gupta@intel.com, badal.nilawar@intel.com,
	riana.tauro@intel.com
Subject: Re: [PATCH v1] drm/xe/pm: Wire up suspend/resume for I2C controller
Date: Fri, 6 Jun 2025 18:29:28 +0300	[thread overview]
Message-ID: <aEMJWGj-iwaFSzJx@black.fi.intel.com> (raw)
In-Reply-To: <sjqgy6d2lvsxvtmeu56r3rcwgkco22n3s6ct4vh2qbmpk5566r@caoxdrcf3nof>

On Fri, Jun 06, 2025 at 08:50:11AM -0500, Lucas De Marchi wrote:
> On Tue, Jun 03, 2025 at 08:41:46PM +0300, Raag Jadav wrote:
> > On Mon, Jun 02, 2025 at 04:48:33PM +0300, Heikki Krogerus wrote:
> > > On Mon, Jun 02, 2025 at 12:38:18PM +0530, Raag Jadav wrote:
> > > > Wire up suspend/resume handles for I2C controller to match its power
> > > > state with SGUnit.
> > > >
> > > > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> > > > ---
> > > >
> > > > This depends on I2C series by Heikki on [1].
> > > > [1] https://lore.kernel.org/intel-xe/20250530141744.3605983-1-heikki.krogerus@linux.intel.com/
> > > 
> > > If it's okay to everybody, I'll include this to my series when I
> > > resend after the merge window is closed.
> > 
> > Let's give it a few days in case of any comments. If not, perhaps you can
> > include it.
> 
> It has to be included there as there's no way we can run CI otherwise.
> For proper CI run you can also send the dependent patch series as a
> squashed "FOR CI" first patch.

Sure. Now that it is reviewed, would be safe to include.

Raag

  reply	other threads:[~2025-06-06 15:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02  7:08 [PATCH v1] drm/xe/pm: Wire up suspend/resume for I2C controller Raag Jadav
2025-06-02  7:14 ` ✗ CI.Patch_applied: failure for " Patchwork
2025-06-02 13:48 ` [PATCH v1] " Heikki Krogerus
2025-06-03 17:41   ` Raag Jadav
2025-06-06 13:50     ` Lucas De Marchi
2025-06-06 15:29       ` Raag Jadav [this message]
2025-06-06 11:48 ` [v1] " Poosa, Karthik

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=aEMJWGj-iwaFSzJx@black.fi.intel.com \
    --to=raag.jadav@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox