linux-kernel - Re: [PATCH v3 00/20] Split devres APIs to device/devres.h and introduce devm_kmemdup

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: <Z6CRBDpXpPha07mf@smile.fi.intel.com>
Date: Mon, 3 Feb 2025 11:48:52 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Raag Jadav <raag.jadav@...el.com>
Cc: gregkh@...uxfoundation.org, rafael@...nel.org, linus.walleij@...aro.org,
	mika.westerberg@...ux.intel.com, dmitry.torokhov@...il.com,
	lgirdwood@...il.com, broonie@...nel.org, sre@...nel.org,
	jic23@...nel.org, przemyslaw.kitszel@...el.com,
	linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-input@...r.kernel.org, linux-sound@...r.kernel.org,
	linux-pm@...r.kernel.org, linux-iio@...r.kernel.org
Subject: Re: [PATCH v3 00/20] Split devres APIs to device/devres.h and
 introduce devm_kmemdup_array()

On Mon, Feb 03, 2025 at 01:38:42PM +0530, Raag Jadav wrote:
> This series
> 
> 1. Splits device/devres.h for the users that are only interested in devres APIs.
>    Original work by Andy Shevchenko:
>    https://lore.kernel.org/r/20241203195340.855879-1-andriy.shevchenko@linux.intel.com
> 
> 2. Introduces a more robust and cleaner devm_kmemdup_array() helper and uses it
>    across drivers.
> 
> The idea behind embedding both work into a single series is to reduce conflicts
> and dependencies while merging.
> 
> v2: Use size_mul() for multiplication (Dmitry)
>     Update commit message (Dmitry)
> 
> v3: Embed devres.h work by Andy

>     Add more users of devm_kmemdup_array()

I understand the desire to cover as much as possible, but it becomes much
harder to coordinate. My proposal stays the same, i.e. I may take the GPIO/pin
control related (and already ACKed!) changes via Intel pin control tree and
the rest may use that immutable tag as needed.

What we need is an Ack for the first patch from Greg and perhaps I can take
IIO, if Jonathan gives an Ack.

>     Update tags and rebase

-- 
With Best Regards,
Andy Shevchenko