From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 0/1] Add some missing descriptions
Date: Wed, 6 Dec 2023 15:41:40 +0100 [thread overview]
Message-ID: <20231206154140.605fa0c2@maurocar-mobl2> (raw)
In-Reply-To: <20231206132045.zueuquideqpvzxxt@kamilkon-desk.igk.intel.com>
On Wed, 6 Dec 2023 14:20:45 +0100
Kamil Konieczny <kamil.konieczny@linux.intel.com> wrote:
> Hi Mauro,
> On 2023-12-06 at 11:51:29 +0100, Mauro Carvalho Chehab wrote:
> > From: Mauro Carvalho Chehab <mchehab@kernel.org>
> >
> > Address those build time warnings:
> >
> > Warning: igt@xe_live_ktest@bo Description documentation is missing
> > Warning: igt@xe_live_ktest@dmabuf Description documentation is missing
> > Warning: igt@xe_live_ktest@migrate Description documentation is missing
> > Warning: igt@xe_media_fill@media-fill Description documentation is missing
>
> You actually adressed only this one, do you plan send other fixes?
Sorry, got a wrong head as basis. Resent it, this time with all 3 patches.
Regards,
Mauro
next prev parent reply other threads:[~2023-12-06 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 10:51 [igt-dev] [PATCH i-g-t 0/1] Add some missing descriptions Mauro Carvalho Chehab
2023-12-06 10:51 ` [igt-dev] [PATCH i-g-t 1/1] intel/xe_media_fill.c: address a documentation warning Mauro Carvalho Chehab
2023-12-06 12:51 ` Kamil Konieczny
2023-12-06 13:05 ` Kamil Konieczny
2023-12-06 11:53 ` [igt-dev] ✗ GitLab.Pipeline: warning for Add some missing descriptions Patchwork
2023-12-06 12:33 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-12-06 13:20 ` [igt-dev] [PATCH i-g-t 0/1] " Kamil Konieczny
2023-12-06 14:41 ` Mauro Carvalho Chehab [this message]
2023-12-06 13:33 ` [igt-dev] ✓ CI.xeBAT: success for " Patchwork
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=20231206154140.605fa0c2@maurocar-mobl2 \
--to=mauro.chehab@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.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