linux-kernel - Re: [PATCH v3] bcma: Use managed APIs

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: <1cb5c9e8-9894-43e6-ba3b-755a7d1dd56b@oss.qualcomm.com>
Date: Sat, 19 Jul 2025 10:21:59 -0700
From: Jeff Johnson <jeff.johnson@....qualcomm.com>
To: Salah Triki <salah.triki@...il.com>,
        Johannes Berg <johannes@...solutions.net>,
        Rafał Miłecki
 <zajec5@...il.com>,
        linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] bcma: Use managed APIs

On 7/19/2025 9:19 AM, Salah Triki wrote:
> Replace pci_* with pcim_* and kzalloc() with devm_kzalloc() so that no
> need to worry about freeing resources and disabling the device.
> 
> Signed-off-by: Salah Triki <salah.triki@...il.com>
> Tested-by: Compile only

1) When you post a new version of a patch, please do NOT have it be
In-Reply-To any previous messages. Each version of a patch should start a
separate e-mail thread. The guidance at
<https://www.kernel.org/doc/html/latest/process/submitting-patches.html#explicit-in-reply-to-headers>
seems outdated.

2) Most maintainers will not accept patches which make such a big semantic
change without actually testing the change on hardware.