From: Matthew Auld <matthew.auld@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH] drm/doc/rfc: Removing missing reference to xe.rst
Date: Fri, 19 Jan 2024 16:29:50 +0000 [thread overview]
Message-ID: <c06e6e4c-ac73-490f-a607-27ae2e014c6b@intel.com> (raw)
In-Reply-To: <ZaqidHi4EGImQgoF@intel.com>
On 19/01/2024 16:25, Rodrigo Vivi wrote:
> On Tue, Jan 16, 2024 at 05:03:31PM -0500, Rodrigo Vivi wrote:
>> The file has already been deleted as the tasks were completed.
>> However the index reference was missed behind.
>
> Gentle ping on this one.
> I should have mentioned here that this fixes a doc build warning:
>
> Documentation/gpu/rfc/index.rst:35: WARNING: toctree contains reference to nonexisting document 'gpu/rfc/xe'
>
>>
>> Fixes: d11dc7aa98e5 ("drm/doc/rfc: Remove Xe's pre-merge plan")
>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
next prev parent reply other threads:[~2024-01-19 16:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 22:03 [PATCH] drm/doc/rfc: Removing missing reference to xe.rst Rodrigo Vivi
2024-01-16 22:08 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-16 22:08 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-16 22:09 ` ✓ CI.KUnit: success " Patchwork
2024-01-16 22:16 ` ✓ CI.Build: " Patchwork
2024-01-16 22:16 ` ✓ CI.Hooks: " Patchwork
2024-01-16 22:17 ` ✓ CI.checksparse: " Patchwork
2024-01-17 18:45 ` ✓ CI.Patch_applied: " Patchwork
2024-01-17 18:45 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-17 18:46 ` ✓ CI.KUnit: success " Patchwork
2024-01-17 18:53 ` ✓ CI.Build: " Patchwork
2024-01-17 18:53 ` ✓ CI.Hooks: " Patchwork
2024-01-17 18:55 ` ✓ CI.checksparse: " Patchwork
2024-01-17 19:17 ` ✓ CI.BAT: " Patchwork
2024-01-19 16:25 ` [PATCH] " Rodrigo Vivi
2024-01-19 16:29 ` Matthew Auld [this message]
2024-01-19 16:45 ` Rodrigo Vivi
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=c06e6e4c-ac73-490f-a607-27ae2e014c6b@intel.com \
--to=matthew.auld@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@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