linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL RESEND] pxa for v3.20
Date: Fri, 23 Jan 2015 13:54:23 -0800	[thread overview]
Message-ID: <20150123215423.GD20896@quad.lixom.net> (raw)
In-Reply-To: <87egqpff9m.fsf@free.fr>

On Tue, Jan 20, 2015 at 08:01:09PM +0100, Robert Jarzmik wrote:
> Hello Arnd, Kevin, Olof,
> 
> Please consider this pxa code for next v3.20 cycle. It was a bit early, but I
> think the upcoming changes around pxa clocks should go for 3.21, and no pending
> patches are in review for v3.20. And yes, I messed up the previous git pull
> email address ...
> 
> The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
> 
>   Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
> 
> are available in the git repository at:
> 
>   https://github.com/rjarzmik/linux.git tags/pxa-for-3.20
> 
> for you to fetch changes up to a52d209336f8fc7483a8c7f4a8a7d2a8e1692a6c:
> 
>   hx4700: regulator: declare full constraints (2014-12-26 18:05:32 +0100)
> 
> ----------------------------------------------------------------
> arm: pxa: pxa for v3.20
> 
> This update deals mostly with regulator updates for fixing all the
> cases where a default regulator is needed, with non device-tree
> platforms. There's also a kconfig fix for device-tree pxa.
> 
> It should be noticed that all interrupts numbers were shifted by
> 16 (number of legacy interrupts).

Hi Robert,

Branch looks good, I'll merge this into next/fixes-non-critical. One nit below
though:

> ----------------------------------------------------------------
> Dmitry Eremin-Solenikov (3):
>       ARM: pxa: add regulator_has_full_constraints to corgi board file
>       ARM: pxa: add regulator_has_full_constraints to poodle board file
>       ARM: pxa: add regulator_has_full_constraints to spitz board file
> 
> Martin Vajnar (1):
>       hx4700: regulator: declare full constraints

Please use consistent patch subjects in the future. We've ended up using ARM:
<platform>: <foo> across all platforms these days.

I'm not going to ask you to respin just for this, but please remember to fix
future patches when you apply them if they're not already correct.


-Olof

  reply	other threads:[~2015-01-23 21:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 19:01 [GIT PULL RESEND] pxa for v3.20 Robert Jarzmik
2015-01-23 21:54 ` Olof Johansson [this message]
2015-01-24 14:18   ` Robert Jarzmik
2015-01-27  2:17     ` Olof Johansson
2015-01-27  4:42       ` Robert Jarzmik
2015-01-27  4:45         ` Olof Johansson

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=20150123215423.GD20896@quad.lixom.net \
    --to=olof@lixom.net \
    --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;
as well as URLs for NNTP newsgroup(s).