From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/06] ARM: shmobile: Kconfig and Makefile cleanups
Date: Wed, 27 Aug 2014 04:19:33 +0000 [thread overview]
Message-ID: <20140827041929.GA12976@verge.net.au> (raw)
In-Reply-To: <20140820133121.808.91022.sendpatchset@w520>
On Mon, Aug 25, 2014 at 01:04:50PM +0900, Magnus Damm wrote:
> On Fri, Aug 22, 2014 at 12:05 PM, Simon Horman <horms@verge.net.au> wrote:
> > On Wed, Aug 20, 2014 at 10:31:21PM +0900, Magnus Damm wrote:
> >> ARM: shmobile: Kconfig and Makefile cleanups
> >>
> >> [PATCH 01/06] ARM: shmobile: Consolidate GPIOLIB Kconfig bits
> >> [PATCH 02/06] ARM: shmobile: Introduce a Kconfig entry for R-Mobile
> >> [PATCH 03/06] ARM: shmobile: Introduce a Kconfig entry for R-Car Gen1
> >> [PATCH 04/06] ARM: shmobile: Introduce a Kconfig entry for R-Car Gen2
> >> [PATCH 05/06] ARM: shmobile: Cleanup pm-rcar.o build using Kconfig
> >> [PATCH 06/06] ARM: shmobile: Cleanup pm-rmobile.o build using Kconfig
> >>
> >> Update the ARM mach-shmobile Kconfig and Makefile to prepare for
> >> multiplatform support of R-Mobile SoCs. While at it do various
> >> cleanups - thanks to Simon Horman for suggesting using Kconfig
> >> for pm-rmobile.o. I applied the same idea to patch 5. Thanks to
> >> Geert Uytterhoeven for pointing out the mess in the Kconfig files,
> >> hopefully this cleanup series is a step in the right direction.
> >
> > Hi Magnus,
> >
> > could you let me know what the status of this series is?
>
> Hi Simon,
>
> Please use the V2 series, it should be OK as-is.
>
> [PATCH v2 00/05] ARM: shmobile: Kconfig and Makefile cleanups V2
>
> Thanks for your help!
Done, thanks.
prev parent reply other threads:[~2014-08-27 4:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 13:31 [PATCH 00/06] ARM: shmobile: Kconfig and Makefile cleanups Magnus Damm
2014-08-20 14:26 ` Geert Uytterhoeven
2014-08-22 3:05 ` Simon Horman
2014-08-25 4:04 ` Magnus Damm
2014-08-27 4:19 ` Simon Horman [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=20140827041929.GA12976@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.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).