linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin GAIGNARD <benjamin.gaignard@st.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"mark.rutland@arm.co" <mark.rutland@arm.co>,
	Alexandre TORGUE <alexandre.torgue@st.com>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	Amelie DELAUNAY <amelie.delaunay@st.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-stm32@st-md-mailman.stormreply.com" 
	<linux-stm32@st-md-mailman.stormreply.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v3] dt-bindings: mfd: Convert stmfx bindings to json-schema
Date: Tue, 16 Jun 2020 13:33:14 +0000	[thread overview]
Message-ID: <f0e8c6fc-a5fc-b621-1c7e-251bafd2f46c@st.com> (raw)
In-Reply-To: <20200514090025.GE271301@dell>



On 5/14/20 11:00 AM, Lee Jones wrote:
> On Thu, 14 May 2020, Benjamin GAIGNARD wrote:
>
>>
>> On 2/26/20 5:21 PM, Rob Herring wrote:
>>> On Thu, 20 Feb 2020 17:22:46 +0100, Benjamin Gaignard wrote:
>>>> Convert stmfx bindings to json-schema
>>>>
>>>> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
>>>> ---
>>>>    .../devicetree/bindings/mfd/st,stmfx.yaml          | 124 +++++++++++++++++++++
>>>>    Documentation/devicetree/bindings/mfd/stmfx.txt    |  28 -----
>>>>    .../devicetree/bindings/pinctrl/pinctrl-stmfx.txt  | 116 -------------------
>>>>    3 files changed, 124 insertions(+), 144 deletions(-)
>>>>    create mode 100644 Documentation/devicetree/bindings/mfd/st,stmfx.yaml
>>>>    delete mode 100644 Documentation/devicetree/bindings/mfd/stmfx.txt
>>>>    delete mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-stmfx.txt
>>>>
>> Hi Lee, Rob,
>>
>> I haven't been able to found this patch in -next branches, can one of
>> you merge it ?
>>
>> Thanks,
>> Benjamin
>>> Reviewed-by: Rob Herring <robh@kernel.org>
> Rob,
>
> We should agree on a process going forward.  Do you take DT document
> changes or should I?  Up until we moved to YAML formatting, I took
> them but responsibly seems to have migrated over to you since then.
>
> I don't mind either way.
Hi,

Any news on this yaml conversion ?

Benjamin
>

  reply	other threads:[~2020-06-16 13:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 16:22 [PATCH v3] dt-bindings: mfd: Convert stmfx bindings to json-schema Benjamin Gaignard
2020-02-26 16:21 ` Rob Herring
2020-05-14  7:39   ` Benjamin GAIGNARD
2020-05-14  9:00     ` Lee Jones
2020-06-16 13:33       ` Benjamin GAIGNARD [this message]
2020-05-20  8:51 ` Lee Jones
2020-06-20 21:32   ` Linus Walleij
2020-06-22 10:30 ` 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=f0e8c6fc-a5fc-b621-1c7e-251bafd2f46c@st.com \
    --to=benjamin.gaignard@st.com \
    --cc=alexandre.torgue@st.com \
    --cc=amelie.delaunay@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mark.rutland@arm.co \
    --cc=robh+dt@kernel.org \
    --cc=robh@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).