From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>,
konrad.dybcio@linaro.org, andersson@kernel.org,
andi.shyti@kernel.org, linux-arm-msm@vger.kernel.org,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org
Cc: quic_vdadhani@quicinc.com
Subject: Re: [PATCH v1 1/4] dt-bindindgs: i2c: qcom,i2c-geni: Document shared flag
Date: Wed, 4 Sep 2024 20:20:28 +0200 [thread overview]
Message-ID: <a4bbb898-bf91-4dcb-b7da-ab032b228aa2@kernel.org> (raw)
In-Reply-To: <cb7613d0-586e-4089-a1b6-2405f4dc4883@quicinc.com>
On 04/09/2024 20:12, Mukesh Kumar Savaliya wrote:
>> Tools like b4 or scripts/get_maintainer.pl provide you proper list of
>> people, so fix your workflow. Tools might also fail if you work on some
>> ancient tree (don't, instead use mainline) or work on fork of kernel
>> (don't, instead use mainline). Just use b4 and everything should be
>> fine, although remember about `b4 prep --auto-to-cc` if you added new
>> patches to the patchset.
>>
>> You missed at least devicetree list (maybe more), so this won't be
>> tested by automated tooling. Performing review on untested code might be
>> a waste of time.
>>
>
> You mean flag addition into DTSI file ? If yes, then the intention was
> to just enable feature support but not into mainline because it should
> happen per board or usecase. Please suggest if i can enable particular
> node with DTSI feature flag.
> Please correct me if my understanding on your ask went wrong.
How is this related?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-04 18:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 9:24 [PATCH v1 0/4] Enable shared SE support over I2C Mukesh Kumar Savaliya
2024-08-29 9:24 ` [PATCH v1 1/4] dt-bindindgs: i2c: qcom,i2c-geni: Document shared flag Mukesh Kumar Savaliya
2024-08-29 9:58 ` Bryan O'Donoghue
2024-08-29 10:01 ` Bryan O'Donoghue
2024-09-04 18:26 ` Mukesh Kumar Savaliya
2024-09-04 18:37 ` Mukesh Kumar Savaliya
2024-08-30 8:11 ` Krzysztof Kozlowski
2024-09-04 18:12 ` Mukesh Kumar Savaliya
2024-09-04 18:20 ` Krzysztof Kozlowski [this message]
2024-09-05 5:43 ` Mukesh Kumar Savaliya
2024-09-05 6:21 ` Krzysztof Kozlowski
2024-09-05 11:17 ` Mukesh Kumar Savaliya
2024-08-29 9:24 ` [PATCH v1 2/4] dma: gpi: Add Lock and Unlock TRE support to access SE exclusively Mukesh Kumar Savaliya
2024-08-29 10:05 ` Bryan O'Donoghue
2024-09-04 18:23 ` Mukesh Kumar Savaliya
2024-08-29 9:24 ` [PATCH v1 3/4] soc: qcom: geni-se: Export function geni_se_clks_off() Mukesh Kumar Savaliya
2024-08-29 10:19 ` Bryan O'Donoghue
2024-09-04 18:12 ` Mukesh Kumar Savaliya
2024-08-29 9:24 ` [PATCH v1 4/4] i2c: i2c-qcom-geni: Enable i2c controller sharing between two subsystems Mukesh Kumar Savaliya
2024-08-29 9:56 ` [PATCH v1 0/4] Enable shared SE support over I2C Bryan O'Donoghue
2024-09-04 18:21 ` Mukesh Kumar Savaliya
2024-08-29 10:10 ` Bryan O'Donoghue
2024-09-04 18:08 ` Mukesh Kumar Savaliya
2024-08-29 17:01 ` Vinod Koul
2024-08-30 7:47 ` neil.armstrong
2024-09-04 18:07 ` Mukesh Kumar Savaliya
2024-09-05 7:09 ` neil.armstrong
2024-09-05 9:28 ` Mukesh Kumar Savaliya
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=a4bbb898-bf91-4dcb-b7da-ab032b228aa2@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_vdadhani@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.