From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm: dts: lpc32xx: update ssp / spi nodes
Date: Sat, 16 Apr 2016 21:34:46 +0200 [thread overview]
Message-ID: <3938626.hTOUROu3U1@wuerfel> (raw)
In-Reply-To: <1460636437-21764-1-git-send-email-slemieux.tyco@gmail.com>
On Thursday 14 April 2016 08:20:34 slemieux.tyco at gmail.com wrote:
> From: Sylvain Lemieux <slemieux@tycoint.com>
>
> This patchset change the following:
> 1) adds clock properties to spi peripheral devices,
> clock ids are taken from dt-bindings/clock/lpc32xx-clock.h
>
> 2) disable, by default, the SSP0/SPI1 and SSP1/SPI2 shared pinout;
> shared pin should be enable in board specific dts, as needed.
>
> 3) enable SSP0 used by PHY3250.
>
> Sylvain Lemieux (3):
> arm: dts: lpc32xx: add clock properties to spi nodes
> arm: dts: lpc32xx: disabled ssp0/spi1 & ssp1/spi2 by default
> arm: dts: phy3250: enable ssp0
>
> arch/arm/boot/dts/lpc32xx.dtsi | 16 ++++++++++++++
> arch/arm/boot/dts/phy3250.dts | 1 +
> 2 files changed, 15 insertions(+)
>
>
The patches look fine, but it's unclear what you want to happen with them
as long as the maintainer situation is not resolved. I've seen patches
from Vladimir and you recently, and none from Roland, so I think it would
be good if one or both of you could officially step up to be maintainers
and collect all patches to forward them to arm at kernel.org for inclusion.
Once we have an agreement on who does this, please send a patch to
update the MAINTAINERS file.
For the patch descriptions, please always start the subject with 'ARM',
not 'arm' to follow the common convention, and always add a multi-line
description even for trivial patches.
Arnd
next prev parent reply other threads:[~2016-04-16 19:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 12:20 [PATCH 0/3] arm: dts: lpc32xx: update ssp / spi nodes slemieux.tyco at gmail.com
2016-04-14 12:20 ` [PATCH 1/3] arm: dts: lpc32xx: add clock properties to " slemieux.tyco at gmail.com
2016-04-18 2:39 ` Vladimir Zapolskiy
2016-04-18 18:41 ` Sylvain Lemieux
2016-04-14 12:20 ` [PATCH 2/3] arm: dts: lpc32xx: disabled ssp0/spi1 & ssp1/spi2 by default slemieux.tyco at gmail.com
2016-04-14 12:20 ` [PATCH 3/3] arm: dts: phy3250: enable ssp0 slemieux.tyco at gmail.com
2016-04-18 2:47 ` Vladimir Zapolskiy
2016-04-18 18:34 ` Sylvain Lemieux
2016-04-16 19:34 ` Arnd Bergmann [this message]
2016-04-18 4:45 ` [PATCH 0/3] arm: dts: lpc32xx: update ssp / spi nodes Vladimir Zapolskiy
2016-04-18 15:03 ` Arnd Bergmann
2016-04-18 21:22 ` Sylvain Lemieux
2016-04-18 21:52 ` Arnd Bergmann
2016-04-20 13:28 ` Sylvain Lemieux
2016-04-21 2:19 ` Vladimir Zapolskiy
2016-04-21 9:59 ` Arnd Bergmann
2016-04-18 23:12 ` Vladimir Zapolskiy
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=3938626.hTOUROu3U1@wuerfel \
--to=arnd@arndb.de \
--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