public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] OMAP: AM3xxx: cpu_is dead code removal
Date: Wed, 30 May 2012 16:43:04 -0700	[thread overview]
Message-ID: <877gvt44mv.fsf@ti.com> (raw)

Tony,

These couple patches didn't make it for v3.5 because of some cross-tree
dependencies.  All the dependencies are now merged (after Linus merged
arm-soc/next/pm), so here's the remaining patches.

Not sure if you want to get them in for 3.5-rc or queue them in your
cleanup branch for v3.6.  Up to you.

Kevin


The following changes since commit cdd3a354a05b0c33fe33ab11a0fb0838396cad19:

  Merge tag 'pm' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2012-05-22 09:41:01 -0700)

are available in the git repository at:


  git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.5/cleanup/am3xxx-cpu-is-leftovers

for you to fetch changes up to 96f3994929c05a21d757a83613d2710b780ea2b4:

  ARM: OMAP: SoC detection: remove unused cpu_is macros (2012-05-25 15:48:48 -0700)

----------------------------------------------------------------
Kevin Hilman (2):
      ARM: OMAP3: clock data: cleanup AM3[35]x SoC detection
      ARM: OMAP: SoC detection: remove unused cpu_is macros

 arch/arm/mach-omap2/clock3xxx_data.c  |    2 +-
 arch/arm/plat-omap/include/plat/cpu.h |   33 ---------------------------------
 2 files changed, 1 insertion(+), 34 deletions(-)

             reply	other threads:[~2012-05-30 23:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 23:43 Kevin Hilman [this message]
2012-06-04 10:31 ` [GIT PULL] OMAP: AM3xxx: cpu_is dead code removal Tony Lindgren

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=877gvt44mv.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /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