linux-kernel - Re: [PATCH v3 00/13] iio: pressure: mprls0025pa: driver code cleanup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aWfNwLRi4ftU5LLC@smile.fi.intel.com>
Date: Wed, 14 Jan 2026 19:09:20 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Petre Rodan <petre.rodan@...dimension.ro>
Cc: Jonathan Cameron <jic23@...nel.org>,
	David Lechner <dlechner@...libre.com>,
	Nuno Sá <nuno.sa@...log.com>,
	Andy Shevchenko <andy@...nel.org>,
	Andreas Klinger <ak@...klinger.de>, linux-iio@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Jonathan Cameron <Jonathan.Cameron@...wei.com>,
	Marcelo Schmitt <marcelo.schmitt1@...il.com>
Subject: Re: [PATCH v3 00/13] iio: pressure: mprls0025pa: driver code cleanup

On Wed, Jan 14, 2026 at 06:55:29PM +0200, Petre Rodan wrote:
> This series contains a collection of patches to the MPR sensor based
> on feedback I received for other drivers.
> 
> major changes:
>  - trigger flag fix (define edge direction only in the device tree)
>  - fix SPI timing violation
>  - fix scan_type struct
>  - fix pressure calculation
>     (does not affect users that define a sensor via the pressure-triplet)
>  - stricter check for the status byte + better error return levels
>  - drop the use of devm_kzalloc()
>  - stick to the datasheet parameters while performing the measurement
>     sequence
> 
> minor changes:
>  - includes added and removed
>  - rename generic 'buffer' variable to 'rx_buf'
> 
> Tested on two sensors - MPRLS0015PA0000SA and MPRLS0001BA00001A

This version looks good to me,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@...el.com>

The change I mentioned can be sent as a followup.

-- 
With Best Regards,
Andy Shevchenko