linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: OMAP2+: Kconfig: minor cleanup for SOC names
Date: Tue,  8 May 2012 15:02:53 -0700	[thread overview]
Message-ID: <1336514576-4870-1-git-send-email-khilman@ti.com> (raw)

The CONFIG_SOC_* names for do not need an OMAP in the name since
these are not called OMAP in most places.  Drop the OMAP in the Kconfig
names to improve readability.

Also fixes an obvious bug found in the TI81xx code which suggests that
nobody is using the highest 32 interrupts on these SoCs, or nobody
is using mainline for TI81xx.

Kevin Hilman (3):
  ARM: OMAP2+: INTC: fix Kconfig option for TI81XX
  ARM: OMAP2+: Kconfig: convert SOC_OMAPTI81XX to SOC_TI81XX
  ARM: OMAP2+: Kconfig: convert SOC_OMAPAM33XX to SOC_AM33XX

 arch/arm/mach-omap2/Kconfig  |    8 ++++----
 arch/arm/mach-omap2/common.h |    4 ++--
 arch/arm/mach-omap2/io.c     |    8 ++++----
 arch/arm/mach-omap2/irq.c    |    2 +-
 4 files changed, 11 insertions(+), 11 deletions(-)

-- 
1.7.9.2

             reply	other threads:[~2012-05-08 22:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 22:02 Kevin Hilman [this message]
2012-05-08 22:02 ` [PATCH 1/3] ARM: OMAP2+: INTC: fix Kconfig option for TI81XX Kevin Hilman
2012-05-08 22:02 ` [PATCH 2/3] ARM: OMAP2+: Kconfig: convert SOC_OMAPTI81XX to SOC_TI81XX Kevin Hilman
2012-05-08 22:02 ` [PATCH 3/3] ARM: OMAP2+: Kconfig: convert SOC_OMAPAM33XX to SOC_AM33XX Kevin Hilman
2012-05-09 11:21   ` Hiremath, Vaibhav
2012-05-09 18:44     ` Tony Lindgren
2012-05-09  6:37 ` [PATCH 0/3] ARM: OMAP2+: Kconfig: minor cleanup for SOC names Shilimkar, Santosh
2012-05-09  8:36 ` Hiremath, Vaibhav

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=1336514576-4870-1-git-send-email-khilman@ti.com \
    --to=khilman@ti.com \
    --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).