linux-kernel - Re: [RESEND PATCH 3/8] hwrng: bcm2835: bcmbca: Replace ARCH_BCM_63XX with ARCH

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]

Date:   Thu, 7 Jul 2022 17:16:52 +0000
From:   <Conor.Dooley@...rochip.com>
To:     <william.zhang@...adcom.com>, <f.fainelli@...il.com>,
        <linux-arm-kernel@...ts.infradead.org>,
        <bcm-kernel-feedback-list@...adcom.com>
CC:     <anand.gore@...adcom.com>, <dan.beygelman@...adcom.com>,
        <kursad.oney@...adcom.com>, <joel.peshkin@...adcom.com>,
        <andre.przywara@....com>, <cai.huoqing@...ux.dev>,
        <Conor.Dooley@...rochip.com>, <geert+renesas@...der.be>,
        <herbert@...dor.apana.org.au>, <mpm@...enic.com>,
        <sgoutham@...vell.com>, <tsbogend@...ha.franken.de>,
        <linux-crypto@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [RESEND PATCH 3/8] hwrng: bcm2835: bcmbca: Replace ARCH_BCM_63XX
 with ARCH_BCMBCA

On 07/07/2022 18:05, William Zhang wrote:
> On 7/7/22 09:23, Florian Fainelli wrote:
>> On 7/6/22 23:57, William Zhang wrote:
>>> Prepare for the BCM63138 ARCH_BCM_63XX migration to ARCH_BCMBCA. Make
>>> HW_RANDOM_BCM2835 depending on ARCH_BCMBCA.
>>>
>>> Signed-off-by: William Zhang <william.zhang@...adcom.com>
>>
>> Acked-by: Florian Fainelli <f.fainelli@...il.com>
>>
>> There is no cover letter for this 8 patch series :/ it is not clear to me whether each subsystem maintainer will be in a posotion to merge these patches individually, yet still have all 8 (7 of them actually, see comment to patch 1) land in 5.20.
>>
> The cover letter will gather all the recipients which will be more than 50

tbf, you probably could cut down the CC list if you want, it isnt required
to CC absolutely everyone that gets spat out by get_maintainer.

For example, I am CCed because I was a recent author for the hwrng kconfig
file, so people like me could be safely excluded if you need to cut down on
the number of people that you are CCing.

Not that I have a problem with being CCed, just if it helps you hit a min.
threshold feel free to drop me :)