linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: msm: Remove unused board files
Date: Mon, 28 Oct 2013 13:43:23 -0700	[thread overview]
Message-ID: <1382993006-27359-2-git-send-email-davidb@codeaurora.org> (raw)
In-Reply-To: <1382993006-27359-1-git-send-email-davidb@codeaurora.org>

These board files were added in 2010, and have never been compiled in
the tree.  If these targets were to be included, at this point, they
would need to be done using device tree, so there is no reason to keep
these files around.

Signed-off-by: David Brown <davidb@codeaurora.org>
---
Note that this patch was made with -D.  I can send the full patch on
request, and have also made the tree available at: 

  git://git.kernel.org/pub/scm/linux/kernel/git/davidb/linux-msm.git for-3.14/big-cleanup

 arch/arm/mach-msm/board-mahimahi.c |  88 ----------------------------
 arch/arm/mach-msm/board-sapphire.c | 117 -------------------------------------
 2 files changed, 205 deletions(-)
 delete mode 100644 arch/arm/mach-msm/board-mahimahi.c
 delete mode 100644 arch/arm/mach-msm/board-sapphire.c

diff --git a/arch/arm/mach-msm/board-mahimahi.c b/arch/arm/mach-msm/board-mahimahi.c
deleted file mode 100644
index 7d9981c..0000000
diff --git a/arch/arm/mach-msm/board-sapphire.c b/arch/arm/mach-msm/board-sapphire.c
deleted file mode 100644
index 3276051..0000000
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2013-10-28 20:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 20:43 [PATCH 0/4] Remove older ARM msm SoC support David Brown
2013-10-28 20:43 ` David Brown [this message]
2013-10-28 20:43 ` [PATCH 2/4] ARM: msm: Remove 7x00 support David Brown
2013-10-29 13:21   ` Daniel Walker
2013-10-29 15:37     ` Olof Johansson
2013-10-29 17:08       ` Daniel Walker
2013-10-29 17:39         ` Olof Johansson
2013-10-29 18:40           ` Tony Lindgren
2013-10-29 19:03           ` Daniel Walker
2013-10-30 23:08       ` Kevin Hilman
2013-10-30 23:25         ` Daniel Walker
2013-10-31  0:36           ` Olof Johansson
2013-10-31  2:45             ` Daniel Walker
2013-10-31  5:19               ` Olof Johansson
2013-10-31 12:07                 ` Daniel Walker
2013-10-31 15:53                   ` Olof Johansson
2013-10-31 16:33                     ` Daniel Walker
2013-10-31 17:12           ` Kevin Hilman
2013-10-31 17:35             ` Daniel Walker
2013-10-31 18:51               ` Kevin Hilman
2013-10-31 19:39                 ` Daniel Walker
2013-10-31 19:23               ` Russell King - ARM Linux
2013-10-31 19:43                 ` Daniel Walker
2013-10-28 20:43 ` [PATCH 3/4] ARM: msm: Remove 7x30 support David Brown
2013-10-29 21:15   ` [PATCH 3/4] ARM: msm: Remove 7x30 supporty Daniel Walker
2013-10-30 13:23     ` Arnd Bergmann
2013-10-28 20:43 ` [PATCH 4/4] ARM: msm: Remove 8x50 support David Brown
2013-10-29 21:19   ` Daniel Walker
2013-10-30 13:30     ` Arnd Bergmann
2013-10-30 15:50       ` Daniel Walker

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=1382993006-27359-2-git-send-email-davidb@codeaurora.org \
    --to=davidb@codeaurora.org \
    --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).