From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
<heikki.krogerus@linux.intel.com>, <andi.shyti@linux.intel.com>
Subject: Re: [PATCH v1] drm/xe/cri: Enable I2C controller
Date: Thu, 4 Dec 2025 15:22:31 -0500 [thread overview]
Message-ID: <aTHth3B0MOEpnay4@intel.com> (raw)
In-Reply-To: <aTFzpOHWRm1Dvmr5@black.igk.intel.com>
On Thu, Dec 04, 2025 at 12:42:28PM +0100, Raag Jadav wrote:
> On Mon, Dec 01, 2025 at 03:27:07PM -0500, Rodrigo Vivi wrote:
> > On Fri, Nov 28, 2025 at 02:14:14PM +0530, Raag Jadav wrote:
> > > Enable I2C controller for Crescent Island and while at it, rely on
> > > has_i2c flag instead of manual platform checks.
> > >
> > > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> >
> > Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> Anything else I can do here?
Have you inspected the CI failures?
>
> Raag
next prev parent reply other threads:[~2025-12-04 20:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 8:44 [PATCH v1] drm/xe/cri: Enable I2C controller Raag Jadav
2025-11-28 8:52 ` ✓ CI.KUnit: success for " Patchwork
2025-12-01 20:27 ` [PATCH v1] " Rodrigo Vivi
2025-12-04 11:42 ` Raag Jadav
2025-12-04 20:22 ` Rodrigo Vivi [this message]
2025-12-05 5:41 ` Raag Jadav
2025-12-12 3:42 ` Raag Jadav
2025-12-12 16:52 ` Matt Roper
2025-12-01 20:27 ` ✓ CI.KUnit: success for drm/xe/cri: Enable I2C controller (rev2) Patchwork
2025-12-01 21:33 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-12-02 0:05 ` ✗ Xe.CI.Full: " Patchwork
2025-12-04 13:25 ` [PATCH v1] drm/xe/cri: Enable I2C controller Heikki Krogerus
2025-12-05 4:28 ` ✓ CI.KUnit: success for drm/xe/cri: Enable I2C controller (rev3) Patchwork
2025-12-05 5:12 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-05 5:47 ` ✓ Xe.CI.Full: " Patchwork
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=aTHth3B0MOEpnay4@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=raag.jadav@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.