From: Xiubo Li <Li.Xiubo@freescale.com>
To: broonie@kernel.org, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
rdunlap@infradead.org, gregkh@linuxfoundation.org,
robh+dt@kernel.org, pawel.moll@arm.com, linux@arm.linux.org.uk
Cc: devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Xiubo Li <Li.Xiubo@freescale.com>
Subject: [PATCHv4 0/2] add DT endianness binding support.
Date: Fri, 9 May 2014 10:04:31 +0800 [thread overview]
Message-ID: <1399601073-19278-1-git-send-email-Li.Xiubo@freescale.com> (raw)
Changes in V4:
- Fix one comment from Markus Pargmann.
- Fix some comments.
Changes in V3:
- Follow Mark Rutland's advice.
- Document common case of the endianess usage.
Changes in V2:
- Namespace the properties using the prefix sring.
- Add one binding ducomentation off regmap.
Xiubo Li (2):
dt/bindings: Add the DT binding documentation for endianness
regmap: add DT endianness binding support.
.../devicetree/bindings/endianness/endianness.txt | 48 +++++++
drivers/base/regmap/regmap-i2c.c | 2 +
drivers/base/regmap/regmap-spi.c | 2 +
drivers/base/regmap/regmap.c | 147 +++++++++++++++++++--
4 files changed, 188 insertions(+), 11 deletions(-)
create mode 100644 Documentation/devicetree/bindings/endianness/endianness.txt
--
1.8.4
next reply other threads:[~2014-05-09 2:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 2:04 Xiubo Li [this message]
2014-05-09 2:04 ` [PATCHv4 1/2] dt/bindings: Add the DT binding documentation for endianness Xiubo Li
2014-05-09 16:32 ` Mark Rutland
2014-05-09 17:02 ` Mark Brown
2014-05-09 18:12 ` Mark Rutland
[not found] ` <1399601073-19278-1-git-send-email-Li.Xiubo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-05-09 2:04 ` [PATCHv4 2/2] regmap: add DT endianness binding support Xiubo Li
2014-05-09 16:47 ` Mark Rutland
2014-05-19 4:11 ` Li.Xiubo
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=1399601073-19278-1-git-send-email-Li.Xiubo@freescale.com \
--to=li.xiubo@freescale.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--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).