All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
	Mark Rutland <mark.rutland@arm.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
	Sebastian Reichel <sre@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Linux Input <linux-input@vger.kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux LED Subsystem <linux-leds@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v4 5/6] dt-bindings: mfd: max77650: convert the binding document to yaml
Date: Mon, 2 Dec 2019 11:09:40 -0600	[thread overview]
Message-ID: <CAL_Jsq+cpPppgVg_42m55DKOwA5uk7CLV_juDyCCECJMuuZYeg@mail.gmail.com> (raw)
In-Reply-To: <20191112105035.GR3218@dell>

On Tue, Nov 12, 2019 at 4:50 AM Lee Jones <lee.jones@linaro.org> wrote:
>
> On Mon, 11 Nov 2019, Bartosz Golaszewski wrote:
>
> > pon., 11 lis 2019 o 09:08 Lee Jones <lee.jones@linaro.org> napisał(a):
> > >
> > > On Mon, 21 Oct 2019, Bartosz Golaszewski wrote:
> > >
> > > > From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> > > >
> > > > Convert the binding document for MAX77650 core MFD module to YAML.
> > > >
> > > > Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> > > > ---
> > > >  .../devicetree/bindings/mfd/max77650.txt      |  46 ------
> > > >  .../devicetree/bindings/mfd/max77650.yaml     | 149 ++++++++++++++++++
> > > >  2 files changed, 149 insertions(+), 46 deletions(-)
> > > >  delete mode 100644 Documentation/devicetree/bindings/mfd/max77650.txt
> > > >  create mode 100644 Documentation/devicetree/bindings/mfd/max77650.yaml
> > >
> > > Applied, thanks.
> > >
> >
> > Hi Lee,
> >
> > FYI this series is already in next through Rob's DT tree.
>
> Why don't I see an 'applied' email?

There was discussion about it in the cover letter.

With the schema for MFDs, we need to merge all the schema thru one
tree because the main schema references the child node schemas.
Otherwise, 'make dt_binding_check' will start failing (as Linus' tree
is now). Perhaps we should encourage they be a single patche because
1) child devices alone don't make sense and 2) it will be clear not to
apply each separately.

Rob

  reply	other threads:[~2019-12-02 17:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 12:44 [PATCH v4 0/6] dt-bindings: max77650: convert the device-tree bindings to yaml Bartosz Golaszewski
2019-10-21 12:44 ` [PATCH v4 1/6] dt-bindings: input: max77650: convert the binding document " Bartosz Golaszewski
2019-10-21 12:44 ` [PATCH v4 2/6] dt-bindings: regulator: " Bartosz Golaszewski
2019-10-22 10:27   ` Mark Brown
2019-10-25 16:56   ` Rob Herring
2019-10-21 12:44 ` [PATCH v4 3/6] dt-bindings: power: " Bartosz Golaszewski
2019-10-25 16:57   ` Rob Herring
2019-10-21 12:44 ` [PATCH v4 4/6] dt-bindings: leds: " Bartosz Golaszewski
2019-10-25 16:58   ` Rob Herring
2019-11-25 13:06   ` Pavel Machek
2019-10-21 12:44 ` [PATCH v4 5/6] dt-bindings: mfd: " Bartosz Golaszewski
2019-10-25 17:02   ` Rob Herring
2019-11-11  8:08   ` Lee Jones
2019-11-11 19:11     ` Bartosz Golaszewski
2019-11-12 10:50       ` Lee Jones
2019-12-02 17:09         ` Rob Herring [this message]
2019-10-21 12:44 ` [PATCH v4 6/6] MAINTAINERS: update the list of maintained files for max77650 Bartosz Golaszewski
2019-10-26 11:54 ` [PATCH v4 0/6] dt-bindings: max77650: convert the device-tree bindings to yaml Bartosz Golaszewski
2019-10-27 21:03   ` Rob Herring

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=CAL_Jsq+cpPppgVg_42m55DKOwA5uk7CLV_juDyCCECJMuuZYeg@mail.gmail.com \
    --to=robh+dt@kernel.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=brgl@bgdev.pl \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dmurphy@ti.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pavel@ucw.cz \
    --cc=sre@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 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.