Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Nikita Travkin <nikita@trvn.ru>
To: Rob Herring <robh@kernel.org>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Lee Jones <lee@kernel.org>,
	linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: mfd: qcom,spmi-pmic: Add pm8916 vm-bms and lbc
Date: Tue, 24 Oct 2023 10:08:56 +0500	[thread overview]
Message-ID: <53474576e3c860a1bb93f811cfe3964a@trvn.ru> (raw)
In-Reply-To: <169808265626.861066.13083505051202182067.robh@kernel.org>

Rob Herring писал(а) 23.10.2023 22:40:
> On Mon, 23 Oct 2023 11:20:32 +0500, Nikita Travkin wrote:
>> PM8916 (and probably some other similar pmics) have hardware blocks for
>> battery monitoring and charging. Add patterns for respecive nodes so the
>> devicetree for those blocks can be validated properly.
>>
>> Signed-off-by: Nikita Travkin <nikita@trvn.ru>
>> ---
>>  Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml | 6 ++++++
>>  1 file changed, 6 insertions(+)
>>
> 
> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> on your patch (DT_CHECKER_FLAGS is new in v5.13):
> 
> yamllint warnings/errors:
> 
> dtschema/dtc warnings/errors:
> /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml:
> Error in referenced schema matching $id: http://devicetree.org/schemas/power/supply/qcom,pm8916-bms-vm.yaml
> 
> doc reference errors (make refcheckdocs):
> 
> See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20231023-pm8916-dtsi-bms-lbc-v2-1-343e3dbf423e@trvn.ru
> 
> The base for the series is generally the latest rc1. A different dependency
> should be noted in *this* patch.
> 

Somehow I missed the memo and thought it tracks -next...

This patch depends on 7f590e3831 and 5cee843d56 in linux-next.git
They were applied in [1].

I'm wondering if the bot just bails out when the "depend" is present
or there is some more sophisticated logic to suggest the base to it?

Sorry for the inconvenience
Nikita

[1] https://lore.kernel.org/r/20230915-pm8916-bms-lbc-v3-0-f30881e951a0@trvn.ru/

  reply	other threads:[~2023-10-24  5:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23  6:20 [PATCH v2 0/3] pm8916: Add BMS and charger Nikita Travkin
2023-10-23  6:20 ` [PATCH v2 1/3] dt-bindings: mfd: qcom,spmi-pmic: Add pm8916 vm-bms and lbc Nikita Travkin
2023-10-23 17:40   ` Rob Herring
2023-10-24  5:08     ` Nikita Travkin [this message]
2023-10-25 12:21       ` Lee Jones
2023-10-25 12:57         ` Nikita Travkin
2023-10-27  7:14           ` Krzysztof Kozlowski
2023-10-25 15:44   ` (subset) " Lee Jones
2023-10-27  7:20     ` Krzysztof Kozlowski
2023-10-31  7:54       ` Lee Jones
2023-11-14  5:24         ` Nikita Travkin
2023-11-14 15:22           ` Krzysztof Kozlowski
2023-10-23  6:20 ` [PATCH v2 2/3] arm64: dts: qcom: pm8916: Add BMS and charger Nikita Travkin
2023-10-24  8:34   ` Konrad Dybcio
2023-10-24  9:29     ` Nikita Travkin
2023-10-26 18:54       ` Konrad Dybcio
2023-10-26 19:17         ` Stephan Gerhold
2023-10-26 20:03           ` Konrad Dybcio
2023-10-27  5:44             ` Nikita Travkin
2023-10-31 11:20               ` Konrad Dybcio
2023-10-23  6:20 ` [PATCH v2 3/3] arm64: dts: qcom: msm8916-longcheer-l8150: Add battery " Nikita Travkin
2023-10-24  8:33   ` Konrad Dybcio
2023-10-24  9:33     ` Nikita Travkin

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=53474576e3c860a1bb93f811cfe3964a@trvn.ru \
    --to=nikita@trvn.ru \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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