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: Mon, 18 Apr 2016 17:03:04 +0200 [thread overview]
Message-ID: <4171701.NnjsU8HtkL@wuerfel> (raw)
In-Reply-To: <5714664C.7080201@mleia.com>
On Monday 18 April 2016 07:45:00 Vladimir Zapolskiy wrote:
> Hi Arnd,
>
> On 16.04.2016 22:34, Arnd Bergmann wrote:
> > 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.
>
> for v4.5 and v4.6 I collected my own patches from LAKML after review,
> I started to do it for v4.7, but probably a bit later than desired.
>
> Could you please remind me, when do ARM maintainers generally stop
> applying "for-next" pull requests?
There is no strict rule. We like to get patches as early as possible
though, and if you send a lot of stuff late we may ask for it to be
deferred until the following release.
If you have a lot of patches that go in early, it's more likely that
later follow-on patches get merged too.
Arnd
next prev parent reply other threads:[~2016-04-18 15:03 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 ` [PATCH 0/3] arm: dts: lpc32xx: update ssp / spi nodes Arnd Bergmann
2016-04-18 4:45 ` Vladimir Zapolskiy
2016-04-18 15:03 ` Arnd Bergmann [this message]
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=4171701.NnjsU8HtkL@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.