From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/12] ARM: shmobile: Rework include path for SoC files
Date: Mon, 10 Mar 2014 08:47:46 +0000 [thread overview]
Message-ID: <20140310084740.GC24411@verge.net.au> (raw)
In-Reply-To: <20140307023813.GG11702@verge.net.au>
On Fri, Mar 07, 2014 at 11:38:16AM +0900, Simon Horman wrote:
> On Mon, Feb 24, 2014 at 02:40:58PM +0900, Magnus Damm wrote:
> > ARM: shmobile: Rework include path for SoC files
> >
> > [PATCH 01/12] ARM: shmobile: Add temporary include workaround
> > [PATCH 02/12] ARM: shmobile: Rework include path for sh7372
> > [PATCH 03/12] ARM: shmobile: Rework include path for sh73a0
> > [PATCH 04/12] ARM: shmobile: Rework include path for EMEV2
> > [PATCH 05/12] ARM: shmobile: Rework include path for r8a7740
> > [PATCH 06/12] ARM: shmobile: Rework include path for r8a7778
> > [PATCH 07/12] ARM: shmobile: Rework include path for r8a7779
> > [PATCH 08/12] ARM: shmobile: Rework include path for r8a7790
> > [PATCH 09/12] ARM: shmobile: Rework include path for r8a7791
> > [PATCH 10/12] ARM: shmobile: Rework include path for r8a73a4
> > [PATCH 11/12] ARM: shmobile: Rework include path for r7s72100
> > [PATCH 12/12] ARM: shmobile: Rework include path for common bits
> >
> > Start converting the mach-shmobile subarchitecture from <mach/something.h>
> > to "something.h". This series covers shared code base and SoC code,
> > however actual header files are not moved yet. Upcoming series that
> > depend on this one will have to convert board code as well. When SoCs
> > code and board code have been converted then actual header files can
> > be moved and temporary include path workarounds can be removed.
> >
> > Signed-off-by: Magnus Damm <damm@opensource.se>
>
> Thanks, I have queued this up.
As Olof has indicated that he is not happy with the first patch of
the series I have dropped the entire series for now.
prev parent reply other threads:[~2014-03-10 8:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 5:40 [PATCH 00/12] ARM: shmobile: Rework include path for SoC files Magnus Damm
2014-02-24 5:41 ` [PATCH 01/12] ARM: shmobile: Add temporary include workaround Magnus Damm
2014-02-24 6:25 ` Magnus Damm
2014-02-24 5:41 ` [PATCH 02/12] ARM: shmobile: Rework include path for sh7372 Magnus Damm
2014-02-24 5:41 ` [PATCH 03/12] ARM: shmobile: Rework include path for sh73a0 Magnus Damm
2014-02-24 5:41 ` [PATCH 04/12] ARM: shmobile: Rework include path for EMEV2 Magnus Damm
2014-02-24 5:41 ` [PATCH 05/12] ARM: shmobile: Rework include path for r8a7740 Magnus Damm
2014-02-24 5:41 ` [PATCH 06/12] ARM: shmobile: Rework include path for r8a7778 Magnus Damm
2014-02-24 5:42 ` [PATCH 07/12] ARM: shmobile: Rework include path for r8a7779 Magnus Damm
2014-02-24 5:42 ` [PATCH 08/12] ARM: shmobile: Rework include path for r8a7790 Magnus Damm
2014-02-24 5:42 ` [PATCH 09/12] ARM: shmobile: Rework include path for r8a7791 Magnus Damm
2014-02-24 5:42 ` [PATCH 10/12] ARM: shmobile: Rework include path for r8a73a4 Magnus Damm
2014-02-24 5:42 ` [PATCH 11/12] ARM: shmobile: Rework include path for r7s72100 Magnus Damm
2014-02-24 5:42 ` [PATCH 12/12] ARM: shmobile: Rework include path for common bits Magnus Damm
2014-03-07 2:38 ` [PATCH 00/12] ARM: shmobile: Rework include path for SoC files Simon Horman
2014-03-10 8:47 ` 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=20140310084740.GC24411@verge.net.au \
--to=horms@verge.net.au \
--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).