From: "André Almeida" <andrealmeid@igalia.com>
To: Raag Jadav <raag.jadav@intel.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 10:52:14 -0300 [thread overview]
Message-ID: <018a61b2-a5d9-422e-b0a6-890d584d83dd@igalia.com> (raw)
In-Reply-To: <aHA33ispT8V6GUhn@black.fi.intel.com>
Em 10/07/2025 18:59, Raag Jadav escreveu:
> 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?
>
The commits that those patches fixes can't be found on drm-misc-fixes as
it's now, so I thought I should merge it at drm-misc-next.
> Also, this series continues to not land in my inbox. This is why I use raw
> emails in my sendmail automation.
>
> Raag
prev parent reply other threads:[~2025-07-11 13:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 19:07 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
2025-07-11 13:52 ` André Almeida [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=018a61b2-a5d9-422e-b0a6-890d584d83dd@igalia.com \
--to=andrealmeid@igalia.com \
--cc=airlied@gmail.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=raag.jadav@intel.com \
--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
all inboxes | Powered by JetHome®