From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/4] arm: mvebu: adding SATA support: dt binding for Armada 370/XP
Date: Fri, 26 Oct 2012 16:57:59 +0200 [thread overview]
Message-ID: <20121026165759.01df4489@skate> (raw)
In-Reply-To: <20121026135225.GO21046@lunn.ch>
On Fri, 26 Oct 2012 15:52:25 +0200, Andrew Lunn wrote:
> > Now, about white spaces vs tab, I don't know what is the rule
> > for .dts file.
>
> I personally use tabs, but i don't see anything in the
> Documentation/CodingStyle.
>
> Maybe ask on the device tree mailing list?
Yes, it would be good to know and document what is the rule for .dts
files, and possibly extend checkpatch to cover those special rules
for .dts files.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-10-26 14:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 12:30 [PATCH V2 0/4] Adding SATA support for Armada 370/XP Gregory CLEMENT
2012-10-26 12:30 ` [PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP Gregory CLEMENT
2012-10-26 12:30 ` [PATCH V2 2/4] arm: mvebu: adding SATA support: dt binding for Armada 370/XP Gregory CLEMENT
2012-10-26 13:31 ` Jason Cooper
2012-10-26 13:34 ` Andrew Lunn
2012-10-26 13:47 ` Gregory CLEMENT
2012-10-26 13:52 ` Andrew Lunn
2012-10-26 14:57 ` Thomas Petazzoni [this message]
2012-10-26 15:02 ` Jason Cooper
2012-10-26 15:06 ` Gregory CLEMENT
2012-10-26 12:30 ` [PATCH V2 3/4] arm: mvebu: adding SATA support: configs update Gregory CLEMENT
2012-10-26 12:30 ` [PATCH V2 4/4] arm: mvebu: adding SATA support: dt binding for Armada 370/XP boards Gregory CLEMENT
2012-10-26 12:39 ` [PATCH V2 0/4] Adding SATA support for Armada 370/XP Andrew Lunn
2012-10-26 12:48 ` Thomas Petazzoni
2012-10-26 12:54 ` Andrew Lunn
2012-10-26 12:55 ` Gregory CLEMENT
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=20121026165759.01df4489@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).