From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Lee Jones <lee.jones@linaro.org>
Cc: devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/4] mfd: max77686: Use a generic name for the PMIC node in the example
Date: Fri, 17 Jul 2015 11:19:26 +0200 [thread overview]
Message-ID: <55A8C89E.8010606@osg.samsung.com> (raw)
In-Reply-To: <55A8C6B2.5020109@cogentembedded.com>
Hello Sergei,
On 07/17/2015 11:11 AM, Sergei Shtylyov wrote:
> Hello.
>
> On 7/17/2015 9:29 AM, Javier Martinez Canillas wrote:
>
>> The ePAR standard says that: "the name of a node should be somewhat
>
> ePAPR.
>
Thanks for pointing it out. I guess that Lee can fix the typo when applying?
>> generic, reflecting the function of the device and not its precise
>> programming model."
>
>> So, change the max77686 binding document example to use a generic
>> node name instead of using the chip's name.
>
>> Suggested-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>
> MBR, Sergei
>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2015-07-17 9:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 6:29 [PATCH v2 0/4] mfd: Improve DT binding docs for max77686 and max77802 Javier Martinez Canillas
2015-07-17 6:29 ` [PATCH v2 1/4] mfd: max77686: Don't suggest in binding to use a deprecated property Javier Martinez Canillas
2015-07-20 8:10 ` Lee Jones
2015-07-20 10:12 ` Javier Martinez Canillas
2015-07-27 10:28 ` Javier Martinez Canillas
2015-07-27 10:33 ` Mark Brown
2015-07-27 10:40 ` Javier Martinez Canillas
2015-07-17 6:29 ` [PATCH v2 2/4] mfd: max77686: Use a generic name for the PMIC node in the example Javier Martinez Canillas
2015-07-17 9:11 ` Sergei Shtylyov
2015-07-17 9:19 ` Javier Martinez Canillas [this message]
2015-07-17 6:29 ` [PATCH v2 3/4] mfd: Add DT binding for Maxim MAX77802 IC Javier Martinez Canillas
2015-07-17 6:36 ` Krzysztof Kozlowski
[not found] ` <1437114567-17629-4-git-send-email-javier-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2015-07-23 15:16 ` Lee Jones
2015-07-23 16:09 ` Javier Martinez Canillas
2015-07-17 6:29 ` [PATCH v2 4/4] mfd: max77686: Split out regulator part from the DT binding Javier Martinez Canillas
2015-07-17 6:42 ` Krzysztof Kozlowski
2015-07-17 6:46 ` Javier Martinez Canillas
2015-07-17 6:49 ` Krzysztof Kozlowski
[not found] ` <CAJKOXPdih+qqGnEZub-hqeVF6POSuSGN-OWnLCgN9cW_5sYb+A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-17 6:59 ` Javier Martinez Canillas
2015-07-17 7:11 ` Krzysztof Kozlowski
[not found] ` <CAJKOXPdTKP21eO0dcD_Ec0YA8H5Jhy2YAFjS8hnQLgVe5cCNrA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-17 7:26 ` Javier Martinez Canillas
[not found] ` <1437114567-17629-5-git-send-email-javier-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2015-07-20 8:08 ` 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=55A8C89E.8010606@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=k.kozlowski@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 \
--cc=sergei.shtylyov@cogentembedded.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).