From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi][PATCH v2] ARM: dts: sunxi: h3/h5 :Add DAI nodes
Date: Tue, 5 Sep 2017 08:41:26 +0200 [thread overview]
Message-ID: <20170905064126.5tpu5s7kuywofgvg@flea> (raw)
In-Reply-To: <20170904174721.21985-1-codekipper@gmail.com>
On Mon, Sep 04, 2017 at 07:47:21PM +0200, codekipper at gmail.com wrote:
> From: Marcus Cooper <codekipper@gmail.com>
>
> Add the new DAI blocks to the device tree. I2S0 and I2S1 are for
> connecting to an external codec.
>
> Signed-off-by: Marcus Cooper <codekipper@gmail.com>
Applied, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170905/3ef6f2e8/attachment-0001.sig>
prev parent reply other threads:[~2017-09-05 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 17:47 [linux-sunxi][PATCH v2] ARM: dts: sunxi: h3/h5 :Add DAI nodes codekipper at gmail.com
2017-09-05 6:41 ` Maxime Ripard [this message]
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=20170905064126.5tpu5s7kuywofgvg@flea \
--to=maxime.ripard@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