From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Youssef Quaisse <yquaisse@gmail.com>
Cc: bingbu.cao@intel.com, tian.shu.qiu@intel.com, mchehab@kernel.org,
gregkh@linuxfoundation.org, skhan@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
linux-media@vger.kernel.org
Subject: Re: [PATCH] Fix three warnings when running `make htmldocs`
Date: Wed, 14 Feb 2024 11:05:16 +0000 [thread overview]
Message-ID: <ZcyebKY86sAJDhr4@kekkonen.localdomain> (raw)
In-Reply-To: <20240210221451.27769-1-yquaisse@gmail.com>
Hi Youssef,
On Sat, Feb 10, 2024 at 10:14:38PM +0000, Youssef Quaisse wrote:
> Running `make htmldocs` generates warnings for file
> drivers/staging/media/ipu3/include/uapi/intel-ipu3.h.
>
> Fix was to remove the "excess" definitions.
>
> Warnings in question:
>
> ```
> ./drivers/staging/media/ipu3/include/uapi/intel-ipu3.h:2522: warning: Excess struct member 'reserved1' description in 'ipu3_uapi_acc_param'
> ./drivers/staging/media/ipu3/include/uapi/intel-ipu3.h:2522: warning: Excess struct member 'reserved2' description in 'ipu3_uapi_acc_param'
> ./drivers/staging/media/ipu3/include/uapi/intel-ipu3.h:2778: warning: Excess struct member '__acc_osys' description in 'ipu3_uapi_flags'
> ```
>
> Signed-off-by: Youssef Quaisse <yquaisse@gmail.com>
Thanks for the patch. These have been already addressed by commit
dcef3ed5b0d79f89018e31d55cf09f2c2f81392b .
> ---
> drivers/staging/media/ipu3/include/uapi/intel-ipu3.h | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/staging/media/ipu3/include/uapi/intel-ipu3.h b/drivers/staging/media/ipu3/include/uapi/intel-ipu3.h
> index caa358e0bae4..4aa2797f5e3c 100644
> --- a/drivers/staging/media/ipu3/include/uapi/intel-ipu3.h
> +++ b/drivers/staging/media/ipu3/include/uapi/intel-ipu3.h
> @@ -2485,11 +2485,9 @@ struct ipu3_uapi_anr_config {
> * &ipu3_uapi_yuvp1_y_ee_nr_config
> * @yds: y down scaler config. See &ipu3_uapi_yuvp1_yds_config
> * @chnr: chroma noise reduction config. See &ipu3_uapi_yuvp1_chnr_config
> - * @reserved1: reserved
> * @yds2: y channel down scaler config. See &ipu3_uapi_yuvp1_yds_config
> * @tcc: total color correction config as defined in struct
> * &ipu3_uapi_yuvp2_tcc_static_config
> - * @reserved2: reserved
> * @anr: advanced noise reduction config.See &ipu3_uapi_anr_config
> * @awb_fr: AWB filter response config. See ipu3_uapi_awb_fr_config
> * @ae: auto exposure config As specified by &ipu3_uapi_ae_config
> @@ -2724,7 +2722,6 @@ struct ipu3_uapi_obgrid_param {
> * @acc_ae: 0 = no update, 1 = update.
> * @acc_af: 0 = no update, 1 = update.
> * @acc_awb: 0 = no update, 1 = update.
> - * @__acc_osys: 0 = no update, 1 = update.
> * @reserved3: Not used.
> * @lin_vmem_params: 0 = no update, 1 = update.
> * @tnr3_vmem_params: 0 = no update, 1 = update.
--
Kind regards,
Sakari Ailus
prev parent reply other threads:[~2024-02-14 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 22:14 [PATCH] Fix three warnings when running `make htmldocs` Youssef Quaisse
2024-02-14 11:05 ` Sakari Ailus [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=ZcyebKY86sAJDhr4@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tian.shu.qiu@intel.com \
--cc=yquaisse@gmail.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