public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/08] ARM: shmobile: Rework include path (Try 2, Part 1)
Date: Fri, 06 Jun 2014 12:24:08 +0200	[thread overview]
Message-ID: <4635749.xI9zCngNoZ@wuerfel> (raw)
In-Reply-To: <CAMuHMdWuaeZOAA-=k7nHQafxJh7h-jQqtfEGJKiEmraZXu2p+g@mail.gmail.com>

On Friday 06 June 2014 11:11:46 Geert Uytterhoeven wrote:
> 
> On Tue, May 20, 2014 at 9:59 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
> > ARM: shmobile: Rework include path (Try 2, Part 1)
> >
> > [PATCH 01/08] ARM: shmobile: Move intc.h, cleanup sh_intc.h usage
> > [PATCH 02/08] ARM: shmobile: Move dma-register.h
> > [PATCH 03/08] ARM: shmobile: Move clock.h
> > [PATCH 04/08] ARM: shmobile: Move most of irqs.h, keep some for pinctl
> > [PATCH 05/08] ARM: shmobile: Move common.h
> > [PATCH 06/08] ARM: shmobile: Move pm-rmobile.h, cleanup sh73xx.h
> > [PATCH 07/08] ARM: shmobile: Move pm-rcar.h, cleanup r8a7779 case
> > [PATCH 08/08] ARM: shmobile: Move rcar-gen2.h, cleanup r8a7790 case
> >
> > Olof, here my latest take on the header move that you requested earlier.
> >
> > This particular series hopefully follows your proposed way and moves the
> > most common shared header files for mach-shmobile from <mach/foobar.h>
> > to "foobar.h" without any workaround. Left are still per-SoC header files
> > that will be moved once I know you are comformatble with this format.
> 
> Olof didn't scream, so I guess he's comfortable with it? 
> Olof?
> 
> If the propagation part is an issue, what about Simon applying it to a separate
> branch, to be merged into both soc-for-v3.17 and boards-for-v3.17?

I certainly love it.

> > Please note that these are only lightly compile tested with a handful
> > of defconfigs, but any potential issue should be trivial to fix.
> 
> Indeed. And it touches arch/arm/mach-shmobile only.
> 
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>

Acked-by: Arnd Bergmann <arnd@arndb.de>

      parent reply	other threads:[~2014-06-06 10:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20  7:59 [PATCH 00/08] ARM: shmobile: Rework include path (Try 2, Part 1) Magnus Damm
2014-05-20  7:59 ` [PATCH 01/08] ARM: shmobile: Move intc.h, cleanup sh_intc.h usage Magnus Damm
2014-05-20  8:00 ` [PATCH 02/08] ARM: shmobile: Move dma-register.h Magnus Damm
2014-05-20  8:00 ` [PATCH 03/08] ARM: shmobile: Move clock.h Magnus Damm
2014-05-20  8:00 ` [PATCH 04/08] ARM: shmobile: Move most of irqs.h, keep some for pinctl Magnus Damm
2014-05-20  8:00 ` [PATCH 05/08] ARM: shmobile: Move common.h Magnus Damm
2014-05-20  8:00 ` [PATCH 06/08] ARM: shmobile: Move pm-rmobile.h, cleanup sh73xx.h Magnus Damm
2014-05-20  8:00 ` [PATCH 07/08] ARM: shmobile: Move pm-rcar.h, cleanup r8a7779 case Magnus Damm
2014-05-20  8:01 ` [PATCH 08/08] ARM: shmobile: Move rcar-gen2.h, cleanup r8a7790 case Magnus Damm
2014-06-06  9:11 ` [PATCH 00/08] ARM: shmobile: Rework include path (Try 2, Part 1) Geert Uytterhoeven
2014-06-06 10:14   ` Simon Horman
2014-06-06 10:24   ` Arnd Bergmann [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=4635749.xI9zCngNoZ@wuerfel \
    --to=arnd@arndb.de \
    --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