From: William Zhang <william.zhang@broadcom.com>
To: Conor.Dooley@microchip.com, f.fainelli@gmail.com,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com
Cc: anand.gore@broadcom.com, dan.beygelman@broadcom.com,
kursad.oney@broadcom.com, joel.peshkin@broadcom.com,
andre.przywara@arm.com, cai.huoqing@linux.dev,
geert+renesas@glider.be, herbert@gondor.apana.org.au,
mpm@selenic.com, sgoutham@marvell.com, tsbogend@alpha.franken.de,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 3/8] hwrng: bcm2835: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA
Date: Thu, 7 Jul 2022 11:18:41 -0700 [thread overview]
Message-ID: <e24acc99-0dce-5879-2379-6a5e3191e123@broadcom.com> (raw)
In-Reply-To: <9ce5272f-f90d-6b26-a0f8-0159a90e4502@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
On 7/7/22 10:16, Conor.Dooley@microchip.com wrote:
> 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@broadcom.com>
>>>
>>> Acked-by: Florian Fainelli <f.fainelli@gmail.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 :)
Thanks! That is my plan too. Try to figure out the threshold now lol
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4212 bytes --]
next prev parent reply other threads:[~2022-07-07 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220707065800.261269-1-william.zhang@broadcom.com>
2022-07-07 6:57 ` [RESEND PATCH 3/8] hwrng: bcm2835: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA William Zhang
2022-07-07 16:23 ` Florian Fainelli
2022-07-07 17:05 ` William Zhang
2022-07-07 17:16 ` Conor.Dooley
2022-07-07 18:18 ` William Zhang [this message]
2022-07-08 3:49 ` Florian Fainelli
2022-07-11 2:11 ` Florian Fainelli
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=e24acc99-0dce-5879-2379-6a5e3191e123@broadcom.com \
--to=william.zhang@broadcom.com \
--cc=Conor.Dooley@microchip.com \
--cc=anand.gore@broadcom.com \
--cc=andre.przywara@arm.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=cai.huoqing@linux.dev \
--cc=dan.beygelman@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=herbert@gondor.apana.org.au \
--cc=joel.peshkin@broadcom.com \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=sgoutham@marvell.com \
--cc=tsbogend@alpha.franken.de \
/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