From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: dt: list all compatible strings for at91
Date: Wed, 19 Mar 2014 11:46:08 +0100 [thread overview]
Message-ID: <20140319104607.GM12021@piout.net> (raw)
In-Reply-To: <5329727E.40604@atmel.com>
On 19/03/2014 at 11:33:34 +0100, Nicolas Ferre wrote :
> On 19/03/2014 11:26, Alexandre Belloni :
> > Avoids getting the newly introduced warning:
> > WARNING: DT compatible string "atmel,at91sam9g45-adc" appears un-documented -- check ./Documentation/devicetree/bindings/
> > + compatible = "atmel,at91sam9g45-adc";
> >
> > Introduced by:
> > bff5da433525 checkpatch: add DT compatible string documentation checks
> >
> > Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>
> Ok, if it is needed.
>
> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>
> BTW, I do not see the devicetree maintainers in the list of CC. If it is
> done for other architectures, I am fine with it, but if we are the only
> one to start this move, I would like them to be aware.
>
Right, I'll resend.
Marvell is already listing all their compatibles but there is still the
issue for nvidia and fsl.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-19 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 10:26 [PATCH] Documentation: dt: list all compatible strings for at91 Alexandre Belloni
2014-03-19 10:33 ` Nicolas Ferre
2014-03-19 10:46 ` Alexandre Belloni [this message]
2014-03-19 16:14 ` Rob Herring
2014-03-20 16:21 ` Alexandre Belloni
2014-03-21 11:14 ` Alexandre Belloni
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=20140319104607.GM12021@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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