mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zijun Hu <zijun.hu@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	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 19:58:41 +0800	[thread overview]
Message-ID: <8c18682d-18f4-4fc8-a3bb-5abb6303ff66@oss.qualcomm.com> (raw)
In-Reply-To: <a72b1f27-1bea-4930-a8f5-b0ae22675920@kernel.org>

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.
> 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.

  reply	other threads:[~2026-02-27 11:58 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 [this message]
2026-02-27 13:17         ` Krzysztof Kozlowski
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=8c18682d-18f4-4fc8-a3bb-5abb6303ff66@oss.qualcomm.com \
    --to=zijun.hu@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --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®