From: Krzysztof Kozlowski <krzk@kernel.org>
To: Zijun Hu <zijun.hu@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Zijun Hu <zijun_hu@icloud.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: glymur-crd: Enable bluetooth
Date: Fri, 27 Feb 2026 14:17:13 +0100 [thread overview]
Message-ID: <66dd6354-2752-4b8f-8631-cbbfd36e4de1@kernel.org> (raw)
In-Reply-To: <8c18682d-18f4-4fc8-a3bb-5abb6303ff66@oss.qualcomm.com>
On 27/02/2026 12:58, Zijun Hu wrote:
> On 2/27/2026 7:43 PM, Krzysztof Kozlowski wrote:
>>> yes.
>>> the git repo is a private one, so nobody will notice and code review it if this change is not posted to https://lore.kernel.org.
>> No, it is not true. The repo is public.
>>
>
> The 'private' i mean is that the repo is not mentioned in kernel tree.
> so it is not known by public.
Entire Qualcomm Glymur work was coordinated through that repo, so what
do you mean "it is not known"?
>> I am asking why are you duplicating the work, why you are asked even to
>> work on something which was already finished/prepared?
>
> actually, both i and many colleagues does not notice the change obviously.
> so cause duplicated effort.
Then I think your team or colleagues or managers should look there first
or ask points of contact for Glymur upstreaming, so you will not be
doing same work again.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-27 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 5:31 Zijun Hu
2026-02-27 11:20 ` Krzysztof Kozlowski
2026-02-27 11:37 ` Zijun Hu
2026-02-27 11:43 ` Krzysztof Kozlowski
2026-02-27 11:58 ` Zijun Hu
2026-02-27 13:17 ` Krzysztof Kozlowski [this message]
2026-02-27 12:20 ` Dmitry Baryshkov
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=66dd6354-2752-4b8f-8631-cbbfd36e4de1@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=zijun.hu@oss.qualcomm.com \
--cc=zijun_hu@icloud.com \
/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®