From: Raag Jadav <raag.jadav@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org,
"John Harrison" <John.C.Harrison@intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"José Roberto de Souza" <jose.souza@intel.com>
Subject: Re: [PATCH 0/2] drm/xe: devcoredump documentation
Date: Fri, 1 Nov 2024 07:49:57 +0200 [thread overview]
Message-ID: <ZyRsBZ1hl8zg2voX@black.fi.intel.com> (raw)
In-Reply-To: <20241031182916.1441987-1-lucas.demarchi@intel.com>
On Thu, Oct 31, 2024 at 11:29:14AM -0700, Lucas De Marchi wrote:
> Improve our kernel-doc and wire it up to the documentation.
>
> Lucas De Marchi (2):
> drm/xe: Improve devcoredump documentation
> drm/xe: Wire up devcoredump in documentation
For the series,
Reviewed-by: Raag Jadav <raag.jadav@intel.com>
prev parent reply other threads:[~2024-11-01 5:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 18:29 [PATCH 0/2] drm/xe: devcoredump documentation Lucas De Marchi
2024-10-31 18:29 ` [PATCH 1/2] drm/xe: Improve " Lucas De Marchi
2024-11-01 5:47 ` Raag Jadav
2024-11-01 12:44 ` Lucas De Marchi
2024-11-01 15:07 ` Raag Jadav
2024-11-01 18:39 ` John Harrison
2024-11-01 19:19 ` Lucas De Marchi
2024-11-01 19:29 ` Lucas De Marchi
2024-11-01 19:59 ` Rodrigo Vivi
2024-11-01 21:17 ` John Harrison
2024-10-31 18:29 ` [PATCH 2/2] drm/xe: Wire up devcoredump in documentation Lucas De Marchi
2024-11-01 14:41 ` Matthew Brost
2024-10-31 19:48 ` ✓ CI.Patch_applied: success for drm/xe: devcoredump documentation Patchwork
2024-10-31 19:48 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-31 19:49 ` ✓ CI.KUnit: success " Patchwork
2024-10-31 20:01 ` ✓ CI.Build: " Patchwork
2024-10-31 20:03 ` ✓ CI.Hooks: " Patchwork
2024-10-31 20:04 ` ✓ CI.checksparse: " Patchwork
2024-10-31 20:29 ` ✓ CI.BAT: " Patchwork
2024-10-31 23:10 ` ✗ CI.FULL: failure " Patchwork
2024-11-01 5:49 ` Raag Jadav [this message]
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=ZyRsBZ1hl8zg2voX@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=John.C.Harrison@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--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 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.