From: "Anwar, Md Danish" <a0501179@ti.com>
To: "Arnd Bergmann" <arnd@arndb.de>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
"MD Danish Anwar" <danishanwar@ti.com>,
"Peng Fan" <peng.fan@nxp.com>, "Rafał Miłecki" <rafal@milecki.pl>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Bjorn Andersson" <quic_bjorande@quicinc.com>,
"Will Deacon" <will@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
srk@ti.com, "Nishanth Menon" <nm@ti.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v2] arm64: defconfig: Enable PRUSS as module
Date: Fri, 4 Aug 2023 15:15:43 +0530 [thread overview]
Message-ID: <a5578fc7-04f9-9d9c-ebf1-3d788075bbcd@ti.com> (raw)
In-Reply-To: <ae2ad056-96de-41b7-8df4-1d9c0f5c469b@app.fastmail.com>
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@gmail.com>
>>> Signed-off-by: MD Danish Anwar <danishanwar@ti.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@kernel.org with all the defconfig
> changes, from where I pick that up. This usually works
> best.
>
> b) you send it to soc@kernel.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
prev parent reply other threads:[~2023-08-04 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 6:18 MD Danish Anwar
2023-08-04 9:11 ` Konrad Dybcio
2023-08-04 9:20 ` Arnd Bergmann
2023-08-04 9:45 ` Anwar, Md Danish [this message]
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=a5578fc7-04f9-9d9c-ebf1-3d788075bbcd@ti.com \
--to=a0501179@ti.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=danishanwar@ti.com \
--cc=geert+renesas@glider.be \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=nm@ti.com \
--cc=peng.fan@nxp.com \
--cc=quic_bjorande@quicinc.com \
--cc=rafal@milecki.pl \
--cc=srk@ti.com \
--cc=vigneshr@ti.com \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®