linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: saravanan sekar <sravanhome@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Maxime Ripard <mripard@kernel.org>,
	devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8] dt-bindings: regulator: add document bindings for mpq7920
Date: Thu, 23 Jan 2020 14:50:24 -0600	[thread overview]
Message-ID: <CAL_JsqJ6B76nyQ8W8LPaM7czesqN54LE=nqd_Vaz++tQ65r2PQ@mail.gmail.com> (raw)
In-Reply-To: <3489a505-9992-037d-5007-6e5f5726a4e7@gmail.com>

On Thu, Jan 23, 2020 at 1:14 AM saravanan sekar <sravanhome@gmail.com> wrote:
>
>
> On 22/01/20 11:16 pm, Rob Herring wrote:
>
> On Wed, Jan 22, 2020 at 11:40 AM Saravanan Sekar <sravanhome@gmail.com> wrote:
>
> Add device tree binding information for mpq7920 regulator driver.
> Example bindings for mpq7920 are added.
>
> Signed-off-by: Saravanan Sekar <sravanhome@gmail.com>
> ---
>
> Notes:
>     Changes on v8 :
>       - fixed error reported by dt_binding_check
>
> Still broken. :(
>
> Sorry I cannot reproduce any error, yaml is parsed and mps,mpq7920.example.dts is generated
>   CHKDT   Documentation/devicetree/bindings/regulator/mps,mpq7920.yaml
> Please help me giving more detail

What about building the example? The build log is attached to the
patch in DT patchwork.

Rob

      parent reply	other threads:[~2020-01-23 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 17:40 [PATCH v8] dt-bindings: regulator: add document bindings for mpq7920 Saravanan Sekar
2020-01-22 22:16 ` Rob Herring
2020-01-23 18:48   ` saravanan sekar
     [not found]   ` <3489a505-9992-037d-5007-6e5f5726a4e7@gmail.com>
2020-01-23 20:50     ` Rob Herring [this message]

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_JsqJ6B76nyQ8W8LPaM7czesqN54LE=nqd_Vaz++tQ65r2PQ@mail.gmail.com' \
    --to=robh+dt@kernel.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mripard@kernel.org \
    --cc=sravanhome@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).