From: Rob Herring <robh@kernel.org>
To: Lee Jones <lee@kernel.org>
Cc: Stanislav Jakubek <stano.jakubek@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>, Pavel Machek <pavel@ucw.cz>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Sebastian Reichel <sre@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
linux-pm@vger.kernel.org, linux-rtc@vger.kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: mfd: sprd,sc2731: reference sprd,sc2731-efuse bindings
Date: Thu, 7 Nov 2024 09:58:06 -0600 [thread overview]
Message-ID: <20241107155806.GA2774753-robh@kernel.org> (raw)
In-Reply-To: <20241106090509.GL1807686@google.com>
On Wed, Nov 06, 2024 at 09:05:09AM +0000, Lee Jones wrote:
> On Mon, 04 Nov 2024, Stanislav Jakubek wrote:
>
> > Directly reference the sc2731-efuse bindings to simplify the schema.
> > Remove the duplicate example from the efuse bindings.
> >
> > Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
> > ---
> > Changes in V3:
> > - new patch due to a missing dependency in the MFD tree
> >
> > Link to V2: https://lore.kernel.org/lkml/ZyExK01iprBHhGm6@standask-GA-A55M-S2HP/
> > Link to V1: https://lore.kernel.org/lkml/Zr3X1RoQs7ElTnlJ@standask-GA-A55M-S2HP/
> >
> > .../devicetree/bindings/mfd/sprd,sc2731.yaml | 10 +------
> > .../bindings/nvmem/sprd,sc2731-efuse.yaml | 29 -------------------
>
> Srini, you happy for this to go in via MFD?
Can you? AIUI, you don't have nvmem/sprd,sc2731-efuse.yaml in your tree.
So take patch 1 now and this one will have to go next cycle.
Rob
next prev parent reply other threads:[~2024-11-07 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 8:48 [PATCH v3 1/2] dt-bindings: mfd: sprd,sc2731: convert to YAML Stanislav Jakubek
2024-11-04 8:48 ` [PATCH v3 2/2] dt-bindings: mfd: sprd,sc2731: reference sprd,sc2731-efuse bindings Stanislav Jakubek
2024-11-06 9:05 ` Lee Jones
2024-11-07 15:58 ` Rob Herring [this message]
2024-11-11 16:40 ` Lee Jones
2024-11-04 16:24 ` [PATCH v3 1/2] dt-bindings: mfd: sprd,sc2731: convert to YAML Rob Herring (Arm)
2024-11-06 9:04 ` Lee Jones
2024-11-09 15:30 ` Jonathan Cameron
2024-11-10 22:20 ` Alexandre Belloni
2024-11-11 22:03 ` Sebastian Reichel
2024-11-12 14:48 ` (subset) " Lee Jones
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=20241107155806.GA2774753-robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=stano.jakubek@gmail.com \
--cc=zhang.lyra@gmail.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;
as well as URLs for NNTP newsgroup(s).