dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: "André Almeida" <andrealmeid@igalia.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	airlied@gmail.com, simona@ffwll.ch,
	Krzysztof Karas <krzysztof.karas@intel.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	kernel-dev@igalia.com
Subject: Re: [PATCH v4 1/3] drm/doc: Fix title underline for "Task information"
Date: Fri, 11 Jul 2025 00:59:58 +0300	[thread overview]
Message-ID: <aHA33ispT8V6GUhn@black.fi.intel.com> (raw)
In-Reply-To: <08de556b-e63c-420e-8ab4-c03712be9709@igalia.com>

On Thu, Jul 10, 2025 at 06:27:45PM -0300, André Almeida wrote:
> Em 04/07/2025 16:07, André Almeida escreveu:
> > Fix the following warning:
> > 
> > Documentation/gpu/drm-uapi.rst:450: WARNING: Title underline too short.
> > 
> > Task information
> > --------------- [docutils]
> > 
> 
> This series is now merged at drm-misc-next, thanks!

Shouldn't this be drm-misc-fixes?

Also, this series continues to not land in my inbox. This is why I use raw
emails in my sendmail automation.

Raag

  reply	other threads:[~2025-07-10 22:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-04 19:07 [PATCH v4 1/3] drm/doc: Fix title underline for "Task information" André Almeida
2025-07-04 19:07 ` [PATCH v4 2/3] drm: Add missing struct drm_wedge_task_info kernel doc André Almeida
2025-07-09  5:45   ` Randy Dunlap
2025-07-04 19:07 ` [PATCH v4 3/3] drm/doc: Fix grammar for "Task information" André Almeida
2025-07-09  2:39   ` Bagas Sanjaya
2025-07-09  5:44   ` Randy Dunlap
2025-07-09  2:36 ` [PATCH v4 1/3] drm/doc: Fix title underline " Bagas Sanjaya
2025-07-09  5:45 ` Randy Dunlap
2025-07-10 21:27 ` André Almeida
2025-07-10 21:59   ` Raag Jadav [this message]
2025-07-11 13:52     ` André Almeida

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=aHA33ispT8V6GUhn@black.fi.intel.com \
    --to=raag.jadav@intel.com \
    --cc=airlied@gmail.com \
    --cc=andrealmeid@igalia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-dev@igalia.com \
    --cc=krzysztof.karas@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=simona@ffwll.ch \
    /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;
as well as URLs for NNTP newsgroup(s).