From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: <lucas.demarchi@intel.com>, <intel-xe@lists.freedesktop.org>,
<anshuman.gupta@intel.com>, <badal.nilawar@intel.com>,
<riana.tauro@intel.com>
Subject: Re: [PATCH v1 2/2] drm/xe/doc: Wire up PCIe Gen5 update limitations
Date: Mon, 31 Mar 2025 11:24:10 -0400 [thread overview]
Message-ID: <Z-qzmk67lxSFy-bk@intel.com> (raw)
In-Reply-To: <20250331142336.640226-3-raag.jadav@intel.com>
On Mon, Mar 31, 2025 at 07:53:36PM +0530, Raag Jadav wrote:
> Append PCIe Gen5 update limitations to xe_firmware document.
>
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
> Documentation/gpu/xe/xe_firmware.rst | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/gpu/xe/xe_firmware.rst b/Documentation/gpu/xe/xe_firmware.rst
> index afcb561cd37d..0c3f93e920fe 100644
> --- a/Documentation/gpu/xe/xe_firmware.rst
> +++ b/Documentation/gpu/xe/xe_firmware.rst
> @@ -31,6 +31,12 @@ GuC Power Conservation (PC)
> .. kernel-doc:: drivers/gpu/drm/xe/xe_guc_pc.c
> :doc: GuC Power Conservation (PC)
>
> +PCIe Gen5 Update Limitations
> +============================
> +
> +.. kernel-doc:: drivers/gpu/drm/xe/xe_debugfs.c
> + :doc: PCIe Gen5 Update Limitations
I believe this should be squashed to the first patch.
But anyways,
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> +
> Internal API
> ============
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-03-31 15:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 14:23 [PATCH v1 0/2] DGFX PCIe Gen5 update telemetry and usage Raag Jadav
2025-03-31 14:23 ` [PATCH v1 1/2] drm/xe/debugfs: Expose PCIe Gen5 update telemetry Raag Jadav
2025-03-31 14:52 ` Lucas De Marchi
2025-03-31 15:23 ` Rodrigo Vivi
2025-03-31 15:15 ` Rodrigo Vivi
2025-04-02 18:24 ` Nilawar, Badal
2025-04-03 3:38 ` Raag Jadav
2025-03-31 14:23 ` [PATCH v1 2/2] drm/xe/doc: Wire up PCIe Gen5 update limitations Raag Jadav
2025-03-31 15:24 ` Rodrigo Vivi [this message]
2025-04-02 10:22 ` Raag Jadav
2025-03-31 14:29 ` ✓ CI.Patch_applied: success for DGFX PCIe Gen5 update telemetry and usage Patchwork
2025-03-31 14:30 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-31 14:31 ` ✓ CI.KUnit: success " Patchwork
2025-03-31 14:47 ` ✓ CI.Build: " Patchwork
2025-03-31 14:50 ` ✓ CI.Hooks: " Patchwork
2025-03-31 14:51 ` ✓ CI.checksparse: " Patchwork
2025-03-31 15:37 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-31 16:54 ` ✗ Xe.CI.Full: failure " 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=Z-qzmk67lxSFy-bk@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@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.