public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: vz@mleia•com (Vladimir Zapolskiy)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] NXP LPC32xx Platform Updates for v4.6 #1
Date: Thu, 3 Mar 2016 04:05:44 +0200	[thread overview]
Message-ID: <56D79BF8.1030508@mleia.com> (raw)
In-Reply-To: <11608683.muXZLfFRbg@wuerfel>

Hi Arnd,

On 03.03.2016 01:27, Arnd Bergmann wrote:
> On Thursday 03 March 2016 00:56:43 Vladimir Zapolskiy wrote:
>> I would really appreciate, if this pull request is accepted for v4.6, if it
>> happens then most probably v4.7 will contain all needed irqchip fixes --
>> this pull request removes a duplicated timer driver, which in turn strictly
>> depends on a legacy platform clock driver (removed) and on hardware irq
>> numbering provided by a legacy irqchip driver (will be removed in v4.7
>> hopefully).
> 
> As far as I can tell, Olof merged the series into the next/cleanup
> branch on Feb 24, but did not make that clear enough in his reply.
> 
> I don't see anything holding up your patches from going into 4.6,
> everything should be fine, let me know if there are any other
> problems here, and please check if the arm-soc/for-next branch
> works for you.
> 

I've checked it and everything is fine, thank you for pointing it out.

--
With best wishes,
Vladimir

      reply	other threads:[~2016-03-03  2:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11  1:41 [GIT PULL] NXP LPC32xx Platform Updates for v4.6 #1 Vladimir Zapolskiy
2016-02-24 21:36 ` Olof Johansson
2016-02-25 14:14   ` Sylvain Lemieux
2016-02-29  0:18     ` Vladimir Zapolskiy
2016-02-29 13:35       ` Sylvain Lemieux
2016-03-02 22:56   ` Vladimir Zapolskiy
2016-03-02 23:27     ` Arnd Bergmann
2016-03-03  2:05       ` 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=56D79BF8.1030508@mleia.com \
    --to=vz@mleia$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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