From: vz@mleia.com (Vladimir Zapolskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm: dts: lpc32xx: update ssp / spi nodes
Date: Tue, 19 Apr 2016 02:12:56 +0300 [thread overview]
Message-ID: <571569F8.3030905@mleia.com> (raw)
In-Reply-To: <1461014548.27294.10.camel@localhost>
Hi Sylvain,
On 19.04.2016 00:22, Sylvain Lemieux wrote:
> Hi Vladimir and Arnd,
>
> On Mon, 2016-04-18 at 07:45 +0300, 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>
>>>>
> ...
>>>>
>>> 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.
>>
> Vladimir, would it be possible for you to add my change, after review
> is done on LAKML, for the lpc32xx pull request you will do for 4.7?
definitely.
For your information I updated my tree https://github.com/vzapolskiy/linux.git
recently, for DTS changes you may want to rebase the changeset on top of
lpc32xx/dt branch.
By the way I plan to rename board DTS files to match lpc32*-*.dts pattern,
but I can postpone doing it until your changes are included.
>>> Once we have an agreement on who does this, please send a patch to
>>> update the MAINTAINERS file.
>>
>> I'll send a change on behalf of myself, at this point I don't think that
>> pure lpc32xx maintenance (deliberately here I exclude development!) task
>> takes more than 20 hours per month, which is affordable for me,
>> Sylvain please express your view.
>>
> I can provide support for pure lpc32xx maintenance task
> (I also exclude development); I can free up to 10-15 hours a
> month for doing testing and patch review.
Sounds good, thank you. Do you want to take over maintenance on v4.8
cycle?
> Is there any documentation available on the process
> to submit a merge request to the mailing list?
>
> ...
As for me I thoroughly observe what other ARM SoC maintainers do, and
ask questions if something remains uncertain.
--
With best wishes,
Vladimir
prev parent reply other threads:[~2016-04-18 23:12 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
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 [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=571569F8.3030905@mleia.com \
--to=vz@mleia.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 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.