Linux kernel staging patches
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] staging: media: ipu3: Remove some excess struct member documentation
Date: Tue, 19 Dec 2023 07:26:51 +0000	[thread overview]
Message-ID: <ZYFFu6ieLKk5QLKe@kekkonen.localdomain> (raw)
In-Reply-To: <87h6kfjay7.fsf@meer.lwn.net>

Hi Jon,

On Mon, Dec 18, 2023 at 05:24:48PM -0700, Jonathan Corbet wrote:
> Remove kerneldoc entries for struct members that do not exist, fixing these
> warnings:
> 
>   ./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: Jonathan Corbet <corbet@lwn.net>

Thanks for the patch.

I'll take this to my tree. I assume the other two patches are destined
elsewhere.

-- 
Kind regards,

Sakari Ailus

      reply	other threads:[~2023-12-19  7:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  0:24 [PATCH 1/3] staging: media: ipu3: Remove some excess struct member documentation Jonathan Corbet
2023-12-19  7:26 ` 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=ZYFFu6ieLKk5QLKe@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=corbet@lwn.net \
    --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 \
    /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