From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: Jihed Chaibi <jihed.chaibi.dev@gmail.com>,
linux-kernel@vger.kernel.org, peter.ujfalusi@gmail.com,
dmitry.torokhov@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
lgirdwood@gmail.com, tiwai@suse.com, conor+dt@kernel.org,
lee@kernel.org, ukleinek@kernel.org, broonie@kernel.org,
gregkh@linuxfoundation.org, linus.walleij@linaro.org,
brgl@bgdev.pl, aaro.koskinen@iki.fi, khilman@baylibre.com,
rogerq@kernel.org, tony@atomide.com, linux-gpio@vger.kernel.org,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-pwm@vger.kernel.org, linux-sound@vger.kernel.org,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
shuah@kernel.org
Subject: Re: [PATCH v3 1/6] dt-bindings: mfd: twl: Add missing sub-nodes for TWL4030 & TWL603x
Date: Wed, 20 Aug 2025 07:57:15 +0200 [thread overview]
Message-ID: <e0bec141-6aef-475f-b997-60fdf8234b82@kernel.org> (raw)
In-Reply-To: <20250819223157.0b271c74@akair>
On 19/08/2025 22:31, Andreas Kemnade wrote:
>>
>>> + type: object
>>> + $ref: /schemas/usb/ti,twlxxxx-usb.yaml#
>>
>> Are you sure your patchset is bsiectable? Apply this patch and test. You
>> will see errors and you must fix these. Even after fixing you have
>> strict dependencies so your cover letter must explain these (or merging
>> constraints)...
>>
> what are the rules here regarding bisectability? non-existing files
dt_binding_check.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-20 5:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 2:15 [PATCH v3 0/6] dt-bindings: Convert TWL4030/6040 family binding to DT schema Jihed Chaibi
2025-08-16 2:15 ` [PATCH v3 1/6] dt-bindings: mfd: twl: Add missing sub-nodes for TWL4030 & TWL603x Jihed Chaibi
2025-08-19 8:13 ` Krzysztof Kozlowski
2025-08-19 14:51 ` Jihed Chaibi
2025-08-19 20:31 ` Andreas Kemnade
2025-08-20 5:57 ` Krzysztof Kozlowski [this message]
2025-08-20 13:15 ` Jihed Chaibi
2025-08-16 2:15 ` [PATCH v3 2/6] mfd: dt-bindings: ti,twl4030-audio: convert to DT schema Jihed Chaibi
2025-08-16 2:15 ` [PATCH v3 3/6] input: dt-bindings: ti,twl4030-keypad: " Jihed Chaibi
2025-08-16 2:15 ` [PATCH v3 4/6] ASoC: dt-bindings: omap-twl4030: " Jihed Chaibi
2025-08-16 2:15 ` [PATCH v3 5/6] usb: dt-bindings: ti,twlxxxx-usb: " Jihed Chaibi
2025-08-16 2:15 ` [PATCH v3 6/6] dt-bindings: gpio: ti,twl4030: Correct the schema $id path Jihed Chaibi
2025-08-19 8:11 ` Krzysztof Kozlowski
2025-08-19 8:14 ` [PATCH v3 0/6] dt-bindings: Convert TWL4030/6040 family binding to DT schema Krzysztof Kozlowski
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=e0bec141-6aef-475f-b997-60fdf8234b82@kernel.org \
--to=krzk@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jihed.chaibi.dev@gmail.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=shuah@kernel.org \
--cc=tiwai@suse.com \
--cc=tony@atomide.com \
--cc=ukleinek@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;
as well as URLs for NNTP newsgroup(s).