From: Joel Fernandes <joelf@ti.com>
To: Mark Rutland <mark.rutland@arm.com>,
Benoit Cousson <bcousson@baylibre.com>
Cc: Linux OMAP List <linux-omap@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: [PATCH v3 0/3] AM33XX crypto DTS patches
Date: Sat, 5 Oct 2013 14:04:34 -0500 [thread overview]
Message-ID: <1380999877-20884-1-git-send-email-joelf@ti.com> (raw)
These patches are some minor fixups and changes to commit messages to the
AM33XX crypto (aes, sham) patches with reference to the comments at:
http://comments.gmane.org/gmane.linux.drivers.devicetree/45961
Joel Fernandes (1):
ARM: dts: AM33XX: Fix AES interrupt number
Mark A. Greer (2):
ARM: dts: AM33XX: Add SHAM data and documentation
ARM: dts: AM33XX: Add AES data and documentation
.../devicetree/bindings/crypto/omap-aes.txt | 31 ++++++++++++++++++++++
.../devicetree/bindings/crypto/omap-sham.txt | 28 +++++++++++++++++++
arch/arm/boot/dts/am335x-bone.dts | 8 ++++++
arch/arm/boot/dts/am335x-evm.dts | 8 ++++++
arch/arm/boot/dts/am335x-evmsk.dts | 8 ++++++
arch/arm/boot/dts/am33xx.dtsi | 19 +++++++++++++
6 files changed, 102 insertions(+)
create mode 100644 Documentation/devicetree/bindings/crypto/omap-aes.txt
create mode 100644 Documentation/devicetree/bindings/crypto/omap-sham.txt
--
1.8.1.2
next reply other threads:[~2013-10-05 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 19:04 Joel Fernandes [this message]
2013-10-05 19:04 ` [PATCH v3 1/3] ARM: dts: AM33XX: Add SHAM data and documentation Joel Fernandes
2013-10-05 19:04 ` [PATCH v3 2/3] ARM: dts: AM33XX: Add AES " Joel Fernandes
2013-10-05 19:04 ` [PATCH v3 3/3] ARM: dts: AM33XX: Fix AES interrupt number Joel Fernandes
2013-10-08 15:51 ` [PATCH v3 0/3] AM33XX crypto DTS patches Benoit Cousson
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=1380999877-20884-1-git-send-email-joelf@ti.com \
--to=joelf@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.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
all inboxes | Powered by JetHome®