linux-kernel - Re: [PATCH v2] arm64: defconfig: Enable PRUSS as module

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] [day] [month] [year] [list]

Date:   Fri, 4 Aug 2023 15:15:43 +0530
From:   "Anwar, Md Danish" <a0501179@...com>
To:     Arnd Bergmann <arnd@...db.de>,
        Konrad Dybcio <konrad.dybcio@...aro.org>,
        MD Danish Anwar <danishanwar@...com>,
        Peng Fan <peng.fan@....com>,
        Rafał Miłecki <rafal@...ecki.pl>,
        Nícolas F. R. A. Prado 
        <nfraprado@...labora.com>,
        Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Bjorn Andersson <quic_bjorande@...cinc.com>,
        Will Deacon <will@...nel.org>,
        Catalin Marinas <catalin.marinas@....com>, <srk@...com>,
        Nishanth Menon <nm@...com>,
        Vignesh Raghavendra <vigneshr@...com>
CC:     <linux-kernel@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        Linux-OMAP <linux-omap@...r.kernel.org>
Subject: Re: [PATCH v2] arm64: defconfig: Enable PRUSS as module

On 8/4/2023 2:50 PM, Arnd Bergmann wrote:
> On Fri, Aug 4, 2023, at 11:11, Konrad Dybcio wrote:
>> On 4.08.2023 08:18, MD Danish Anwar wrote:
>>> Enables PRUSS as kernel module for TI SoCs.
>>>
>>> Reviewed-by: Christian Gmeiner <christian.gmeiner@...il.com>
>>> Signed-off-by: MD Danish Anwar <danishanwar@...com>
>>> ---
>> As an outsider, I have no idea what this does, and the Kconfig help
>> message doesn't say much more either.
>>
>> Could you please add a short summary about what sort of hardware
>> is driven by this driver?
> 
> Any additional information would also help, but more importantly,
> Danish please use a recipient list that has only the people on 'To:'
> that would actually apply the patch (Nishanth and Vignesh) and
> ask them to merge it, while having everyone else on Cc.
> 

Sure Arnd, I will only keep Nishant and Vignesh in to and move everyone 
else to Cc.

> The problem with addressing a trivial patch to a dozen people
> is that often everyone will think that someone else will take
> care of it. If you address a patch to just one or two maintainers,
> they are more likely to either apply it or tell you if you got
> the wrong person instead of ignoring.
> 
> For defconfig patches adding platform specific lines, there are
> two ways this can be handled:
> 
> a) the K3 maintainers pick it up into a branch and send a
>     pull request to soc@...nel.org with all the defconfig
>     changes, from where I pick that up. This usually works
>     best.
> 
> b) you send it to soc@...nel.org yourself and I wait for
>     an Ack from the K3 maintainers so I know they agree with
>     the contents as well as being bypassed as maintainers on
>     this occasion.
> 
>       Arnd

-- 
Thanks and Regards,
Md Danish Anwar