mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: health: max30100: drop unnecessary cast
Date: Sun, 12 Apr 2026 15:32:12 +0100	[thread overview]
Message-ID: <20260412153212.62a27aa5@jic23-huawei> (raw)
In-Reply-To: <20260321205646.207ac77f@jic23-huawei>

On Sat, 21 Mar 2026 20:56:46 +0000
Jonathan Cameron <jic23@kernel.org> wrote:

> On Mon, 16 Mar 2026 13:25:00 +0200
> Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> 
> > On Sat, Mar 14, 2026 at 05:33:01PM -0500, David Lechner wrote:  
> > > Drop an unnecessary cast in max30100_led_init().
> > > 
> > > val is defined as unsigned int val[2]; so the cast is not needed, nor
> > > is the address-of operator &.
> > > 
> > > Also fix alignment with ( while we are touching this.    
> >   
> > >  	ret = device_property_read_u32_array(dev, "maxim,led-current-microamp",
> > > -					(unsigned int *) &val, 2);
> > > +					     val, 2);    
> > 
> > You want to have ARRAY_SIZE() as well.
> >   
> Should we make val a u32 val[2]?
> 
> Obviously we all know the unsigned int is that big, but in theory that might
> not always be so...
> 
> This is the only place where it's passed as a pointer rather than value from
> one of the elements I think.
> 
David, this question is outstanding so I've marked it 'changes requested'
in patchwork.

Thanks,

Jonathan

> 
> 


      reply	other threads:[~2026-04-12 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-14 22:33 David Lechner
2026-03-16 11:25 ` Andy Shevchenko
2026-03-21 20:56   ` Jonathan Cameron
2026-04-12 14:32     ` Jonathan Cameron [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=20260412153212.62a27aa5@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 \
    /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

all inboxes | Powered by JetHome®