From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: Lee Jones <lee.jones@linaro.org>,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] MAINTAINERS: add Device Tree binding doc for max77686 regulator
Date: Fri, 17 Jul 2015 19:00:18 +0900 [thread overview]
Message-ID: <CAJKOXPdQ9cH2NesrxOheA1bDMd1T0VvOGkFoosfMKWKxXLDdMw@mail.gmail.com> (raw)
In-Reply-To: <1437121078-26409-2-git-send-email-javier@osg.samsung.com>
2015-07-17 17:17 GMT+09:00 Javier Martinez Canillas <javier@osg.samsung.com>:
> The Device Tree binding documentation for the Maxim max77686 regulators
> has been moved from the Multi-Function Device DT binding section to its
> own Documentation/devicetree/bindings/regulator/max77686.txt file.
>
> Use a wilcard so both the mfd and regulator DT bindings are resolved.
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
> ---
>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks for updating this.
Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2015-07-17 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 8:17 [PATCH 0/2] MAINTAINERS: update max77686 entry and add one for max77802 Javier Martinez Canillas
2015-07-17 8:17 ` [PATCH 1/2] MAINTAINERS: add Device Tree binding doc for max77686 regulator Javier Martinez Canillas
2015-07-17 10:00 ` Krzysztof Kozlowski [this message]
2015-07-23 13:48 ` Lee Jones
2015-07-17 8:17 ` [PATCH 2/2] MAINTAINERS: add an entry for the Maxim MAX77802 PMIC drivers Javier Martinez Canillas
[not found] ` <1437121078-26409-3-git-send-email-javier-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2015-07-17 10:05 ` Krzysztof Kozlowski
2015-07-23 14:45 ` 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=CAJKOXPdQ9cH2NesrxOheA1bDMd1T0VvOGkFoosfMKWKxXLDdMw@mail.gmail.com \
--to=k.kozlowski@samsung.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier@osg.samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.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).