All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v2 15/19] ARM: kirkwood: move SoC headers to mach-kirkwood/include/mach
Date: Fri, 20 Feb 2015 08:19:51 +0100	[thread overview]
Message-ID: <54E6E017.6010009@denx.de> (raw)
In-Reply-To: <1424415855-10456-16-git-send-email-yamada.m@jp.panasonic.com>

On 20.02.2015 08:04, Masahiro Yamada wrote:
> Move arch/arm/include/asm/arch-kirkwood/*
>    -> arch/arm/mach-kirkwood/include/mach/*
>
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> Cc: Prafulla Wadaskar <prafulla@marvell.com>
> Cc: Luka Perkov <luka.perkov@sartura.hr>
> Cc: Stefan Roese <sr@denx.de>

Acked-by: Stefan Roese <sr@denx.de>

Thanks,
Stefan

  reply	other threads:[~2015-02-20  7:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  7:03 [U-Boot] [RFC PATCH v2 0/19] ARM: start to move SoC code into arch/arm/mach-* Masahiro Yamada
2015-02-20  7:03 ` [U-Boot] [RFC PATCH v2 01/19] ARM: at91: move board select menu and common settings Masahiro Yamada
2015-02-20  7:03 ` [U-Boot] [RFC PATCH v2 02/19] ARM: prepare for moving SoC sources into mach-* Masahiro Yamada
2015-02-20  7:03 ` [U-Boot] [RFC PATCH v2 03/19] ARM: at91: collect SoC sources into mach-at91 Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 04/19] ARM: tegra: collect SoC sources into mach-tegra Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 05/19] ARM: davinci: move SoC sources to mach-davinci Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 06/19] ARM: kirkwood: move SOC sources to mach-kirkwood Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 07/19] ARM: nomadik: move SoC sources to mach-nomadik Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 08/19] ARM: highbank: move SoC sources to mach-highbank Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 09/19] ARM: orion5x: move SoC sources to mach-orion5x Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 10/19] ARM: versatile: move SoC sources to mach-versatile Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 11/19] ARM: keystone: move SoC sources to mach-keystone Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 12/19] kbuild: prepare for moving headers into mach-*/include/mach Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 13/19] ARM: at91: move SoC headers to mach-at91/include/mach Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 14/19] ARM: davinci: move SoC headers to mach-davinci/include/mach Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 15/19] ARM: kirkwood: move SoC headers to mach-kirkwood/include/mach Masahiro Yamada
2015-02-20  7:19   ` Stefan Roese [this message]
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 16/19] ARM: nomadik: move SoC headers to mach-nomadik/include/mach Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 17/19] ARM: orion5x: move SoC headers to mach-orion5x/include/mach Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 18/19] ARM: keystone: move SoC headers to mach-keystone/include/mach Masahiro Yamada
2015-02-20  7:04 ` [U-Boot] [RFC PATCH v2 19/19] ARM: prepare for including <mach/*.h> Masahiro Yamada
2015-02-20  7:29 ` [U-Boot] [RFC PATCH v2 0/19] ARM: start to move SoC code into arch/arm/mach-* Masahiro Yamada

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=54E6E017.6010009@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.