public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Steven Miao (Steven Miao)" <realmz6@gmail.com>
To: <torvalds@linux-foundation.org>
Cc: <uclinux-dist-devel@blackfin.uclinux.org>,
	<linux-kernel@vger.kernel.org>
Subject: [uclinux-dist-devel] [GIT PULL] Blackfin updates for 3.10
Date: Thu, 9 May 2013 19:14:21 +0800	[thread overview]
Message-ID: <1368098061-666-1-git-send-email-realmz6@gmail.com> (raw)

Hi Linus,

please pull blackfin updates for Linux 3.10, some minor changes for performance and bug fixes.

The following changes since commit c1be5a5b1b355d40e6cf79cc979eb66dafa24ad1:

  Linux 3.9 (2013-04-28 17:36:01 -0700)

are available in the git repository at:

  https://github.com/realmz/blackfin-linux.git tags/for-linus

for you to fetch changes up to 5ae89ee043ce96e3790e6c75f3807c8e37d98634:

  bfin cache: dcplb map: add 16M dcplb map for BF60x (2013-05-09 18:22:45 +0800)

----------------------------------------------------------------
blackfin updates for Linux 3.9

----------------------------------------------------------------
Aaron Wu (1):
      Platform Nand: Set the GPIO for NAND read as input

Geert Uytterhoeven (1):
      blackfin: twi: Remove bogus #endif

James Cosin (1):
      blackfin: fix bootup core clock and system clock display

Sonic Zhang (3):
      blackfin: dmc: Improve DDR2 write through in DMC effict controller.
      bf609: rsi: Add bf609 rsi MMR macro and board platform data.
      blackfin: rename vmImage to uImage after we move to buildroot

Steven Miao (2):
      blackfin: smp: fix smp build after drop asm/system.h
      bfin cache: dcplb map: add 16M dcplb map for BF60x

 arch/blackfin/Makefile                             |    6 ++--
 arch/blackfin/boot/Makefile                        |   16 +++++-----
 arch/blackfin/include/asm/atomic.h                 |    2 ++
 arch/blackfin/include/asm/bfin_sdh.h               |   31 ++++++++++++++++++--
 arch/blackfin/include/asm/bitops.h                 |    1 +
 arch/blackfin/include/asm/def_LPBlackfin.h         |    2 ++
 arch/blackfin/include/asm/mem_init.h               |    9 ++++++
 arch/blackfin/kernel/cplb-nompu/cplbinit.c         |   16 ++++++++--
 arch/blackfin/kernel/cplb-nompu/cplbmgr.c          |   27 ++++++++++++++---
 arch/blackfin/kernel/cplbinfo.c                    |    9 ++++--
 arch/blackfin/kernel/setup.c                       |    2 +-
 arch/blackfin/mach-bf537/boards/stamp.c            |    1 +
 arch/blackfin/mach-bf538/boards/ezkit.c            |    1 -
 .../mach-bf609/include/mach/cdefBF60x_base.h       |    2 ++
 14 files changed, 101 insertions(+), 24 deletions(-)


             reply	other threads:[~2013-05-09 11:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09 11:14 Steven Miao (Steven Miao) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-05-09 11:28 [uclinux-dist-devel] [GIT PULL] Blackfin updates for 3.10 Steven Miao (Steven Miao)
2013-05-09 21:53 ` Linus Torvalds
2013-05-10  0:27   ` Stephen Rothwell
2013-05-10  2:48     ` Steven Miao
2013-05-11 19:37       ` Mike Frysinger
2013-05-13  2:40         ` Steven Miao
2013-05-13  0:04       ` Stephen Rothwell
2013-05-10  2:58     ` Bob Liu
2013-05-10  2:56   ` Bob Liu

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=1368098061-666-1-git-send-email-realmz6@gmail.com \
    --to=realmz6@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.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