linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] Add support for pxa27x device-tree machine
Date: Thu, 30 Oct 2014 07:55:48 +0100	[thread overview]
Message-ID: <87k33i6o7f.fsf@free.fr> (raw)
In-Reply-To: <1413127731-1187-1-git-send-email-robert.jarzmik@free.fr> (Robert Jarzmik's message of "Sun, 12 Oct 2014 17:28:47 +0200")

Robert Jarzmik <robert.jarzmik@free.fr> writes:

> Hi,
>
> This is the second version of this patchset, to provide a device-tree machine
> support for pxa27x.
>
> Since latest review by Arnd :
>  - patches 1, 3 and 4 were ok
>  - patch 2 was respined

Okay, let's see where we stand.
Mark, do my answer on patch 1/4 was good enough, or would you rather have patch
1/4 melt into patch 4/4 ? I don't care going one way or the other around, so
just tell me.

Arnd, if the patches are good to go, could I have an ack ?

Cheers.

--
Robert

  parent reply	other threads:[~2014-10-30  6:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12 15:28 [PATCH v2 0/4] Add support for pxa27x device-tree machine Robert Jarzmik
2014-10-12 15:28 ` [PATCH v2 1/4] arm: pxa: add device-tree irq init for pxa27x Robert Jarzmik
2014-10-13 10:34   ` Mark Rutland
2014-10-13 18:18     ` Robert Jarzmik
2014-10-12 15:28 ` [PATCH v2 2/4] arm: pxa: move init functions into generic.h Robert Jarzmik
2014-10-12 15:28 ` [PATCH v2 3/4] arm: pxa: remove unecessary includes from pxa-dt Robert Jarzmik
2014-10-12 15:28 ` [PATCH v2 4/4] arm: pxa: add pxa27x device-tree support Robert Jarzmik
2014-10-30  6:55 ` Robert Jarzmik [this message]
2014-10-30  7:07   ` [PATCH v2 0/4] Add support for pxa27x device-tree machine Arnd Bergmann
2014-11-03  7:32     ` Robert Jarzmik
2014-11-03 10:11       ` Arnd Bergmann

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=87k33i6o7f.fsf@free.fr \
    --to=robert.jarzmik@free.fr \
    --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).