From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: qcom: videocc-glymur: Constify qcom_cc_desc
Date: Tue, 31 Mar 2026 13:34:43 +0200 [thread overview]
Message-ID: <66739d18-2c3d-49d9-b456-2e8c1b81385a@oss.qualcomm.com> (raw)
In-Reply-To: <ecd73358-70ee-4ddc-ab99-aecdf084c172@oss.qualcomm.com>
On 31/03/2026 10:59, Konrad Dybcio wrote:
> You're free to contribute to the internal template that these drivers are
> based on
That's a very reversed logic. I don't use "internal template" because it
is the wrong approach and I am always advocating against it. I am
advocating on basing your work on UPSTREAM work.
Additionally, it's internal, not open-source. I could work on many
internal things, but they don't matter, I don't want to touch them, I
don't care about them. Actually, I imply that no one in open source
community should particularly care about internal stuff.
So no, the users of broken internal stuff need to fix that broken stuff.
Job of the community is not to dwell into internal Qualcomm templates...
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-31 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 8:55 Krzysztof Kozlowski
2026-03-31 8:59 ` Konrad Dybcio
2026-03-31 9:20 ` Taniya Das
2026-03-31 11:34 ` Krzysztof Kozlowski [this message]
2026-03-31 9:15 ` Taniya Das
2026-04-05 19:40 ` Bjorn Andersson
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=66739d18-2c3d-49d9-b456-2e8c1b81385a@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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®