From: Daniel Schultz <d.schultz@phytec.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Garrett Giordano <ggiordano@phytec.com>,
catalin.marinas@arm.com, will@kernel.org,
quic_bjorande@quicinc.com, geert+renesas@glider.be,
dmitry.baryshkov@linaro.org, shawnguo@kernel.org,
neil.armstrong@linaro.org, alexander.stein@ew.tq-group.com,
biju.das.jz@bp.renesas.com, javier.carrasco@wolfvision.net,
elinor.montmasson@savoirfairelinux.com,
linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, upstream@lists.phytec.de
Subject: Re: [Upstream] [PATCH] arm64: defconfig: Enable BANG BANG Thermal Governor
Date: Mon, 5 May 2025 15:40:59 +0200 [thread overview]
Message-ID: <ac9ba45c-4545-46bf-a908-54133520e34d@phytec.de> (raw)
In-Reply-To: <ab0ab264-4fd2-4826-8a89-eaa55c462183@linaro.org>
On 5/5/25 10:33, Krzysztof Kozlowski wrote:
> On 05/05/2025 10:18, Daniel Schultz wrote:
>> Hey,
>>
>> can someone please take a look at this patch? I can also re-send in case
>> it doesn't apply anymore. Thanks!
>
> Sounds like a product thingy, so I do not see much need to enable it in
> the defconfig.
I'm okay with that. We can handle that downstream but wasn't sure if
this config would be accepted.
>
> BTW, the more people you CC, the bigger chance no one will fell
> responsible. You Cc-eed ~7 persons not related to your subsystem.
Ah, yes that makes sense. Thank you for the hint!
- Daniel
>
>
> Best regards,
> Krzysztof
prev parent reply other threads:[~2025-05-05 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 18:56 [PATCH] arm64: defconfig: Enable BANG BANG Thermal Governor Garrett Giordano
2025-05-05 8:18 ` [Upstream] " Daniel Schultz
2025-05-05 8:33 ` Krzysztof Kozlowski
2025-05-05 13:40 ` Daniel Schultz [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=ac9ba45c-4545-46bf-a908-54133520e34d@phytec.de \
--to=d.schultz@phytec.de \
--cc=alexander.stein@ew.tq-group.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=catalin.marinas@arm.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=elinor.montmasson@savoirfairelinux.com \
--cc=geert+renesas@glider.be \
--cc=ggiordano@phytec.com \
--cc=javier.carrasco@wolfvision.net \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_bjorande@quicinc.com \
--cc=shawnguo@kernel.org \
--cc=upstream@lists.phytec.de \
--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