public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel•com>
To: "André Almeida" <andrealmeid@igalia•com>
Cc: simona@ffwll•ch, Krzysztof Karas <krzysztof.karas@intel•com>,
	airlied@gmail•com,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	dri-devel@lists•freedesktop.org, linux-kernel@vger•kernel.org,
	Stephen Rothwell <sfr@canb•auug.org.au>,
	kernel-dev@igalia•com
Subject: Re: [PATCH v3 1/3] drm/doc: Fix title underline for "Task information"
Date: Fri, 4 Jul 2025 21:26:14 +0300	[thread overview]
Message-ID: <aGgcxuT7YQx4YC2Q@black.fi.intel.com> (raw)
In-Reply-To: <52c32d1b-e5c4-4f6d-82a3-cf02c0cf4681@igalia.com>

On Fri, Jul 04, 2025 at 01:46:07PM -0300, André Almeida wrote:
> Raag, gently ping for reviewing this series.

Somehow this didn't land in my inbox and I have no idea why.

Raag

> Em 27/06/2025 14:17, André Almeida escreveu:
> > Fix the following warning:
> > 
> > Documentation/gpu/drm-uapi.rst:450: WARNING: Title underline too short.
> > 
> > Task information
> > --------------- [docutils]
> > 
> > Fixes: cd37124b4093 ("drm/doc: Add a section about "Task information" for the wedge API")
> > Reported-by: Stephen Rothwell <sfr@canb•auug.org.au>
> > Signed-off-by: André Almeida <andrealmeid@igalia•com>
> > ---
> > v2: Add Reported-by tag
> > ---
> >   Documentation/gpu/drm-uapi.rst | 4 ++--
> >   1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
> > index 263e5a97c080..10dea6a1f097 100644
> > --- a/Documentation/gpu/drm-uapi.rst
> > +++ b/Documentation/gpu/drm-uapi.rst
> > @@ -447,7 +447,7 @@ hang is usually the most critical one which can result in consequential hangs or
> >   complete wedging.
> >   Task information
> > ----------------
> > +----------------
> >   The information about which application (if any) was involved in the device
> >   wedging is useful for userspace if they want to notify the user about what
> > @@ -728,4 +728,4 @@ Stable uAPI events
> >   From ``drivers/gpu/drm/scheduler/gpu_scheduler_trace.h``
> >   .. kernel-doc::  drivers/gpu/drm/scheduler/gpu_scheduler_trace.h
> > -   :doc: uAPI trace events
> > \ No newline at end of file
> > +   :doc: uAPI trace events
> 

  reply	other threads:[~2025-07-04 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250627171715.438304-1-andrealmeid@igalia.com>
2025-07-04 16:46 ` [PATCH v3 1/3] drm/doc: Fix title underline for "Task information" André Almeida
2025-07-04 18:26   ` Raag Jadav [this message]
2025-07-04 18:41 ` Raag Jadav
2025-07-04 18:49   ` André Almeida
2025-07-04 18:54     ` Raag Jadav
     [not found] ` <20250627171715.438304-2-andrealmeid@igalia.com>
2025-07-04 18:47   ` [PATCH v3 2/3] drm: Add missing struct drm_wedge_task_info kernel doc Raag Jadav
     [not found] ` <20250627171715.438304-3-andrealmeid@igalia.com>
2025-07-04 18:49   ` [PATCH v3 3/3] drm/doc: Fix grammar for "Task information" Raag Jadav

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=aGgcxuT7YQx4YC2Q@black.fi.intel.com \
    --to=raag.jadav@intel$(echo .)com \
    --cc=airlied@gmail$(echo .)com \
    --cc=andrealmeid@igalia$(echo .)com \
    --cc=dri-devel@lists$(echo .)freedesktop.org \
    --cc=kernel-dev@igalia$(echo .)com \
    --cc=krzysztof.karas@intel$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=simona@ffwll$(echo .)ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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