From: "Yokoyama, Caz" <caz.yokoyama@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Souza, Jose" <jose.souza@intel.com>
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915: Add struct to hold IP version
Date: Mon, 1 Nov 2021 14:29:33 +0000 [thread overview]
Message-ID: <a68a1f5360065e9abf11235c9f3ecafa454156fb.camel@intel.com> (raw)
In-Reply-To: <e4a994711cf0bb0d580269eda56ab0bcdad98f87.camel@intel.com>
Reviewed-by: Caz Yokoyama <caz.yokoyama@intel.com>
-caz
On Thu, 2021-10-28 at 21:08 +0000, Souza, Jose wrote:
> Reviewed-by: Caz Yokoyama <caz.yokoyama@intel.com>
next prev parent reply other threads:[~2021-11-01 14:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 0:23 [Intel-gfx] [PATCH 1/3] drm/i915: Add struct to hold IP version José Roberto de Souza
2021-10-20 0:23 ` [Intel-gfx] [PATCH 2/3] drm/i915: Track media IP stepping separated from GT José Roberto de Souza
2021-11-02 7:30 ` Lucas De Marchi
2021-10-20 0:23 ` [Intel-gfx] [PATCH 3/3] drm/i915: Rename GT_STEP to GRAPHICS_STEP José Roberto de Souza
2021-10-20 15:06 ` Yokoyama, Caz
2021-11-02 7:27 ` Lucas De Marchi
2021-10-20 0:37 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915: Add struct to hold IP version Patchwork
2021-10-20 1:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-10-20 5:10 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-02 20:04 ` Souza, Jose
2021-10-20 9:47 ` [Intel-gfx] [PATCH 1/3] " Jani Nikula
2021-10-20 19:29 ` Souza, Jose
2021-10-21 13:11 ` Jani Nikula
2021-10-22 20:15 ` Lucas De Marchi
2021-10-25 9:04 ` Jani Nikula
2021-11-02 5:33 ` Souza, Jose
2021-10-20 15:00 ` Yokoyama, Caz
2021-10-20 19:19 ` Souza, Jose
2021-10-22 21:26 ` Yokoyama, Caz
2021-10-28 21:08 ` Souza, Jose
2021-11-01 14:29 ` Yokoyama, Caz [this message]
2021-11-02 7:32 ` Lucas De Marchi
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=a68a1f5360065e9abf11235c9f3ecafa454156fb.camel@intel.com \
--to=caz.yokoyama@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@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