From: Lubomir Rintel <lkundrak@v3.sk>
To: Olof Johansson <olof@lixom.net>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] ARM: dts: mmp2: devicetree updates
Date: Thu, 20 Jun 2019 17:07:19 +0200 [thread overview]
Message-ID: <20190620150724.1406757-1-lkundrak@v3.sk> (raw)
Hi,
Here's a couple of updates for the MMP2 SoC devicetree files.
They're pretty much independent of each other, can be applied in any
order.
Lubo
next reply other threads:[~2019-06-20 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 15:07 Lubomir Rintel [this message]
2019-06-20 15:07 ` [PATCH 1/5] ARM: dts: mmp2: trivial whitespace fix Lubomir Rintel
2019-06-20 15:07 ` [PATCH 2/5] ARM: dts: mmp2: fix the SPI nodes Lubomir Rintel
2019-06-20 15:07 ` [PATCH 3/5] ARM: dts: mmp2: rename the USB PHY node Lubomir Rintel
2019-06-20 15:07 ` [PATCH 4/5] ARM: dts: mmp2: add camera interfaces Lubomir Rintel
2019-06-20 15:07 ` [PATCH 5/5] ARM: dts: mmp2: specify reg-shift for the UARTs Lubomir Rintel
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=20190620150724.1406757-1-lkundrak@v3.sk \
--to=lkundrak@v3.sk \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--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