From: Mark Brown <broonie@kernel.org>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Ferre, Nicolas" <Nicolas.FERRE@atmel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
"Yang, Wenyou" <Wenyou.Yang@atmel.com>,
Peter Korsgaard <jacmet@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Kumar Gala <galak@codeaurora.org>,
Lee Jones <lee.jones@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 1/2] regulator: act8945a: add regulator driver for ACT8945A
Date: Fri, 29 Jan 2016 13:03:37 +0100 [thread overview]
Message-ID: <20160129120337.GS4130@sirena.org.uk> (raw)
In-Reply-To: <CABxcv=kNKmgRytxB5ppawrAvC-GDRhV4T_UUGvpHgKp9+BsUmQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 165 bytes --]
On Fri, Jan 29, 2016 at 08:50:19AM -0300, Javier Martinez Canillas wrote:
> Then he should remove the .of_compatible from the MFD cell definition.
Yes, obviously.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2016-01-29 12:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 2:57 [PATCH v4 0/2] regulator: act8945a: add regulator driver for the sub-device of ACT8945A MFD Wenyou Yang
2016-01-27 2:57 ` [PATCH v4 1/2] regulator: act8945a: add regulator driver for ACT8945A Wenyou Yang
[not found] ` <1453863463-30515-2-git-send-email-wenyou.yang-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2016-01-29 0:16 ` Mark Brown
2016-01-29 1:20 ` Yang, Wenyou
2016-01-29 11:35 ` Mark Brown
[not found] ` <20160129113518.GQ4130-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-01-29 11:50 ` Javier Martinez Canillas
2016-01-29 12:03 ` Mark Brown [this message]
[not found] ` <CABxcv=kNKmgRytxB5ppawrAvC-GDRhV4T_UUGvpHgKp9+BsUmQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-01 5:54 ` Yang, Wenyou
2016-02-01 13:15 ` Javier Martinez Canillas
[not found] ` <CABxcv=nJsWEv9KW-5iPpUnyN8ZVpx6CV07gBRaLNWqd644YOqQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-02 2:26 ` Yang, Wenyou
2016-02-03 2:33 ` Yang, Wenyou
2016-02-03 17:47 ` Mark Brown
2016-02-04 13:28 ` Yang, Wenyou
2016-02-02 17:42 ` Peter Korsgaard
[not found] ` <87wpqn3t72.fsf-D6SC8u56vOOJDPpyT6T3/w@public.gmane.org>
2016-02-03 2:29 ` Yang, Wenyou
2016-02-03 2:45 ` Krzysztof Kozlowski
2016-01-27 2:57 ` [PATCH v4 2/2] regulator: add documentation for ACT8945A's regulator DT bindings Wenyou Yang
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=20160129120337.GS4130@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Nicolas.FERRE@atmel.com \
--cc=Wenyou.Yang@atmel.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jacmet@gmail.com \
--cc=javier@dowhile0.org \
--cc=k.kozlowski@samsung.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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).