From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail•com>
Cc: Mauro Carvalho Chehab <mchehab@kernel•org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the v4l-dvb-fixes tree
Date: Fri, 18 Sep 2020 18:03:57 +1000 [thread overview]
Message-ID: <20200918180357.3afadbda@canb.auug.org.au> (raw)
In-Reply-To: <20200918075230.GD3049@jagdpanzerIV.localdomain>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
Hi Sergey,
On Fri, 18 Sep 2020 16:52:30 +0900 Sergey Senozhatsky <sergey.senozhatsky@gmail•com> wrote:
>
> On (20/09/18 17:21), Stephen Rothwell wrote:
> > After merging the v4l-dvb-fixes tree, today's linux-next build (htmldocs)
> > produced this warning:
> >
> > Documentation/userspace-api/media/v4l/buffer.rst:692: WARNING: The "flat-table" directive is empty; content required.
> >
> > .. flat-table::
> > :header-rows: 0
> > :stub-columns: 0
> > :widths: 3 1 4
>
> Thanks. I think there is a patch for this already.
> Will hit linux-next soon.
Excellent, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-18 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 7:21 linux-next: build warning after merge of the v4l-dvb-fixes tree Stephen Rothwell
2020-09-18 7:52 ` Sergey Senozhatsky
2020-09-18 8:03 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-25 22:50 Stephen Rothwell
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=20200918180357.3afadbda@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@kernel$(echo .)org \
--cc=sergey.senozhatsky@gmail$(echo .)com \
/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