public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
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: Thu, 21 Apr 2016 11:59:24 +0200	[thread overview]
Message-ID: <7082850.i7ZQLBP0Xs@wuerfel> (raw)
In-Reply-To: <571838C5.4050102@mleia.com>

On Thursday 21 April 2016 05:19:49 Vladimir Zapolskiy wrote:
> Hi Sylvain,
> 
> On 20.04.2016 16:28, Sylvain Lemieux wrote:
> > Hi Vladimir,
> > 
> > On Mon, 2016-04-18 at 23:52 +0200, Arnd Bergmann wrote:
> >> On Monday 18 April 2016 17:22:28 Sylvain Lemieux wrote:
> >>> On Mon, 2016-04-18 at 07:45 +0300, Vladimir Zapolskiy wrote:
> >>>>> Once we have an agreement on who does this, please send a patch to
> >>>>> update the MAINTAINERS file.
> >>>>
> > Will you send a patch to update the MAINTAINERS file or do you want
> > me to send it?
> 
> I'll send to change, you'll be included as a maintainer, the record
> also needs some other updates, e.g. it is not about machine support
> but about SoC support etc.
> 
> Arnd, I'm not sure if MAINTAINERS update should go though a pull
> request (= no explicit SoB from an ARM maintainer) or if you expect
> to get a patch and apply it yourself, please advise.

Either way works. We tend to group MAINTAINER file updates with bugfixes,
so if you have any other fixes for 4.6 or 4.7, just throw it in the same
pull request you send us, otherwise send a separate patch.

> > Should we add the lpc32xx dts to the list of supported file?
> > 
> 
> There is a possibility to add files by regex, which makes sense
> to do after renaming dts files - this is in my first priority todo list.

The order is not important here, it's fine with me if you want to add
a regex for the new name even if the actual renaming is in a different
branch.

	Arnd

  reply	other threads:[~2016-04-21  9:59 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 [this message]
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=7082850.i7ZQLBP0Xs@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