linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/4] ARM: mvebu: cleanup for v3.9
Date: Sat, 12 Jan 2013 23:29:11 +0000	[thread overview]
Message-ID: <mailman.25.1358033378.1035.linux-arm-kernel@lists.infradead.org> (raw)
In-Reply-To: <pull-1358033364-983365>

The following changes since commit d1c3ed669a2d452cacfb48c2d171a1f364dae2ed:

  Linux 3.8-rc2 (2013-01-02 18:13:21 -0800)

are available in the git repository at:

  git://git.infradead.org/users/jcooper/linux.git tags/cleanup_for_v3.9

for you to fetch changes up to b96e1b1c3c5319294edb0970b6d5bf099c0e85eb:

  ARM: Kirkwood: Cleanup unneeded include files (2013-01-12 21:50:10 +0000)

----------------------------------------------------------------
mvebu cleanup for v3.9
 - remove unneeded includes due to DT conversion

----------------------------------------------------------------
Andrew Lunn (1):
      ARM: Kirkwood: Cleanup unneeded include files

Thomas Petazzoni (1):
      arm: kirkwood: dockstar: remove useless include of SDIO header

 arch/arm/mach-kirkwood/board-ib62x0.c   | 1 -
 arch/arm/mach-kirkwood/board-mplcec4.c  | 1 -
 arch/arm/mach-kirkwood/dockstar-setup.c | 1 -
 3 files changed, 3 deletions(-)

  reply	other threads:[~2013-01-12 23:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12 23:29 [GIT PULL 0/4] ARM: mvebu: changes for v3.9 Jason Cooper
2013-01-12 23:29 ` Jason Cooper [this message]
2013-01-12 23:29 ` [GIT PULL 2/4] ARM: mvebu: drivers " Jason Cooper
2013-01-12 23:29 ` [GIT PULL 3/4] ARM: mvebu: boards " Jason Cooper
2013-01-12 23:29 ` [GIT PULL 4/4] ARM: mvebu: dt " Jason Cooper
     [not found] ` <E1TuAWu-0004Jx-Hn@merlin.infradead.org>
2013-01-13  1:05   ` [GIT PULL 2/4] ARM: mvebu: drivers " Russell King - ARM Linux
2013-01-13  1:28     ` Jason Cooper
     [not found] ` <E1TuAWD-0004Ec-1G@merlin.infradead.org>
2013-01-13  1:06   ` [GIT PULL 3/4] ARM: mvebu: boards " Russell King - ARM Linux
     [not found] ` <E1TuAWi-0004H4-K6@merlin.infradead.org>
2013-01-13  1:06   ` [GIT PULL 4/4] ARM: mvebu: dt " Russell King - ARM Linux
2013-01-13  1:30     ` Jason Cooper
2013-01-23  2:48 ` [GIT PULL V2 0/4] ARM: mvebu: changes " Jason Cooper
2013-01-23  2:48   ` [GIT PULL V2 1/4] ARM: mvebu: cleanup " Jason Cooper
2013-01-28  5:57     ` Olof Johansson
2013-01-23  2:48   ` [GIT PULL V2 2/4] ARM: mvebu: drivers " Jason Cooper
2013-01-28  5:53     ` Olof Johansson
2013-01-28 11:53       ` Chris Ball
2013-01-28 16:10         ` Jason Cooper
2013-01-23  2:48   ` [GIT PULL V2 3/4] ARM: mvebu: boards " Jason Cooper
2013-01-23  2:48   ` [GIT PULL V2 4/4] ARM: mvebu: dt " Jason Cooper
  -- strict thread matches above, loose matches on Subject: below --
2013-02-01 15:51 [GIT PULL 0/4] ARM: mvebu: changes " Jason Cooper
2013-02-01 15:51 ` [GIT PULL 1/4] ARM: mvebu: cleanup " Jason Cooper
2013-02-05  7:10   ` Olof Johansson
2013-02-16 19:55 Jason Cooper
2013-02-19 17:09 ` Arnd Bergmann

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=mailman.25.1358033378.1035.linux-arm-kernel@lists.infradead.org \
    --to=jason@lakedaemon.net \
    --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).