All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
	Athanasios Oikonomou <athoik@gmail.com>,
	linux-media@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] media: frontend.h.rst.exceptions: add more dvb define exceptions
Date: Fri, 19 May 2023 09:03:08 +0100	[thread overview]
Message-ID: <20230519090308.0e53eccd@sal.lan> (raw)
In-Reply-To: <20230518234735.20289-1-rdunlap@infradead.org>

Hi Randy,

Em Thu, 18 May 2023 16:47:35 -0700
Randy Dunlap <rdunlap@infradead.org> escreveu:

> Building documentation reports multiple warnings for undefined DVB
> frontend labels:
> 
> Documentation/output/frontend.h.rst:6: WARNING: undefined label: 'fec-11-45'
> Documentation/output/frontend.h.rst:6: WARNING: undefined label: 'fec-4-15'
> Documentation/output/frontend.h.rst:6: WARNING: undefined label: 'fec-14-45'
> Documentation/output/frontend.h.rst:6: WARNING: undefined label: 'fec-7-15'
> Documentation/output/frontend.h.rst:6: WARNING: undefined label: 'fec-11-45'
> Documentation/output/frontend.h.rst:6: WARNING: undefined label: 'fec-4-15'
> Documentation/output/frontend.h.rst:6: WARNING: undefined label: 'fec-14-45'
> Documentation/output/frontend.h.rst:6: WARNING: undefined label: 'fec-7-15'

Thanks for the patch. FYI, I already merged yesterday a fix identical
to your patch:

	https://git.linuxtv.org/media_stage.git/commit/?id=8bc27fa5d7763d376a992a1638475987ed4807e7

Regards,
Mauro


> 
> so add those symbols to the ignore list to prevent the build warnings.
> 
> Fixes: 1825788e2a96 ("media: dvb: add missing DVB-S2X FEC parameter values")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Link: https://lore.kernel.org/linux-media/202305162245.wtaLIXf3-lkp@intel.com/
> Cc: Athanasios Oikonomou <athoik@gmail.com>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: linux-media@vger.kernel.org
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> ---
>  Documentation/userspace-api/media/frontend.h.rst.exceptions |    4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff -- a/Documentation/userspace-api/media/frontend.h.rst.exceptions b/Documentation/userspace-api/media/frontend.h.rst.exceptions
> --- a/Documentation/userspace-api/media/frontend.h.rst.exceptions
> +++ b/Documentation/userspace-api/media/frontend.h.rst.exceptions
> @@ -142,6 +142,10 @@ ignore symbol FEC_26_45
>  ignore symbol FEC_28_45
>  ignore symbol FEC_32_45
>  ignore symbol FEC_77_90
> +ignore symbol FEC_11_45
> +ignore symbol FEC_4_15
> +ignore symbol FEC_14_45
> +ignore symbol FEC_7_15
>  
>  ignore symbol TRANSMISSION_MODE_AUTO
>  ignore symbol TRANSMISSION_MODE_1K

  reply	other threads:[~2023-05-19  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 23:47 [PATCH] media: frontend.h.rst.exceptions: add more dvb define exceptions Randy Dunlap
2023-05-19  8:03 ` Mauro Carvalho Chehab [this message]
2023-05-19 15:01   ` Randy Dunlap

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=20230519090308.0e53eccd@sal.lan \
    --to=mchehab@kernel.org \
    --cc=athoik@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=rdunlap@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.