Messages in this thread | | | Date | Thu, 7 Jul 2022 20:49:27 -0700 | Subject | Re: [RESEND PATCH 3/8] hwrng: bcm2835: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA | From | Florian Fainelli <> |
| |
On 7/7/2022 11:18 AM, William Zhang wrote: > > > 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
Try adding --norolestats to your get_maintainer.pl invocation. -- Florian
| |