public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
	linux-kernel@vger.kernel.org,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: tsl2772: fix all kernel-doc warnings
Date: Sat, 28 Feb 2026 13:12:08 +0000	[thread overview]
Message-ID: <20260228131208.27fd3131@jic23-huawei> (raw)
In-Reply-To: <fc1eddb4-b01f-49a4-808c-9a58b2b63ad8@infradead.org>

On Thu, 26 Feb 2026 14:25:12 -0800
Randy Dunlap <rdunlap@infradead.org> wrote:

> Hi Andy,
> 
> On 2/26/26 12:29 PM, Andy Shevchenko wrote:
> > On Thu, Feb 26, 2026 at 11:14:05AM -0800, Randy Dunlap wrote:  
> >> On 2/26/26 12:04 AM, Andy Shevchenko wrote:  
> >>> On Wed, Feb 25, 2026 at 09:12:57PM -0800, Randy Dunlap wrote:  
> >>>> Use the correct kernel-doc notation for struct members to eliminate
> >>>> kernel-doc warnings:
> >>>>
> >>>> Warning: include/linux/platform_data/tsl2772.h:88 struct member
> >>>>  'prox_diode' not described in 'tsl2772_settings'
> >>>> Warning: include/linux/platform_data/tsl2772.h:88 struct member
> >>>>  'prox_power' not described in 'tsl2772_settings'  
> >>>
> >>> Hmm... I do not see any of the user of this header file.
> >>> Have you checked if these values are even used?
> >>> Perhaps we can simply kill all this?  
> 
> AFAICT all macros and structs and struct members from that header file are used
> in tsl2772.c.
> 
> >> They are used in drivers/iio/light/tsl2772.c.  
> > 
> > It's the same driver. So it's *not* a user of the platform data.
> > 
> > Under 'kill' I meant the following:
> > - inline the content of the file to the c-file  
> 
> Would that be "violating" this commit?

I think the proposal is to remove platform data support entirely from
this driver on basis we have no upstream users.

There are defaults in driver for the stuff that can still come from
platform data.  Note there is generic property support for a bunch
of other stuff (i assume for DT).

So I'd be fine with a patch that removes this header and the use
of platform data in the driver. Easiest path to that is as Andy described
in putting the defs in the c file, plus only using the driver defaults
(so no more 'real' platform data).

Jonathan

> commit 436d42c61c3e
> Author: Arnd Bergmann <arnd@arndb.de>
> Date:   Fri Aug 24 15:22:12 2012 +0200
> 
>     ARM: samsung: move platform_data definitions
>     
>     Platform data for device drivers should be defined in
>     include/linux/platform_data/*.h, not in the architecture
>     and platform specific directories.
> 
> > - recheck the c-file for the unused fields and drop them for good  
> 
> All used AFAICT.
> 
> > Alternatively converting c-file to use device properties instead
> > of platform data.  
> 
> That's your area, I guess.
> 
> > We have done many times in the past such transformations in other
> > drivers.
> >   
> >>> But if Jonathan wants to take this as a quick fix to make less
> >>> warnings appear effective immediately I'm fine with the change
> >>> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>  
> >   
> thanks.


  reply	other threads:[~2026-02-28 13:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26  5:12 [PATCH] iio: tsl2772: fix all kernel-doc warnings Randy Dunlap
2026-02-26  8:04 ` Andy Shevchenko
2026-02-26 19:14   ` Randy Dunlap
2026-02-26 20:29     ` Andy Shevchenko
2026-02-26 22:25       ` Randy Dunlap
2026-02-28 13:12         ` Jonathan Cameron [this message]
2026-02-28 13:13   ` Jonathan Cameron

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=20260228131208.27fd3131@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox