From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/5] dts: sun8i-h3: complete UART I2C for H3
Date: Thu, 15 Sep 2016 16:58:16 +0200 [thread overview]
Message-ID: <20160915145816.GK10128@lukather> (raw)
In-Reply-To: <1473703967-21356-1-git-send-email-jorik@kippendief.biz>
On Mon, Sep 12, 2016 at 08:12:42PM +0200, jorik at kippendief.biz wrote:
> From: Jorik Jonker <jorik@kippendief.biz>
>
> This is my fifth attempt to complete the UART/I2C definitions on H3.
>
> Many thanks to Maxime and Chen-Yu for helping me understand the
> philosophy behind the DTS/DTSI structure. I hope I get it and five
> times is a charm :-)
I queued it, 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: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160915/87dc4dd1/attachment.sig>
prev parent reply other threads:[~2016-09-15 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 18:12 [PATCH v5 0/5] dts: sun8i-h3: complete UART I2C for H3 jorik at kippendief.biz
2016-09-12 18:12 ` [PATCH v5 1/5] dts: sun8i-h3: add pinmux definitions for UART2-3 jorik at kippendief.biz
2016-09-12 18:12 ` [PATCH v5 2/5] dts: sun8i-h3: split off RTS/CTS for UART1 in seperate pinmux jorik at kippendief.biz
2016-09-12 18:12 ` [PATCH v5 3/5] dts: sun8i-h3: associate exposed UARTs on Orange Pi Boards jorik at kippendief.biz
2016-09-12 18:12 ` [PATCH v5 4/5] dts: sun8i-h3: add pinmux definitions for I2C0-2 jorik at kippendief.biz
2016-09-12 18:12 ` [PATCH v5 5/5] dts: sun8i-h3: add I2C0-2 peripherals to H3 SOC jorik at kippendief.biz
2016-09-15 14:58 ` 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=20160915145816.GK10128@lukather \
--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