public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-cris-kernel <linux-cris-kernel@axis.com>
Subject: [GIT PULL] CRIS changes for 3.19
Date: Sat, 20 Dec 2014 01:29:53 +0100	[thread overview]
Message-ID: <20141220002953.GR26817@axis.com> (raw)

Hi Linus,

Please pull the below branch for CRIS changes for 3.19,
mostly cleanup and build fixes for CRISv32 allmodconfig.

God Jul och Gott Nytt år!

The following changes since commit e589c9e13aeb0c5539bf1314b3a78442ea8fc0c2:

  Merge branch 'x86-apic-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2014-12-19 14:02:02 -0800)

are available in the git repository at:


  git://git.kernel.org/pub/scm/linux/kernel/git/jesper/cris.git tags/cris-changes-for-3.19

for you to fetch changes up to 8bcabff0589c1ef8fec9f98d525943217ae10971:

  CRISv32: Remove last remnants of ETRAX_SPI_MMC_BOARD (2014-12-20 00:06:13 +0100)

----------------------------------------------------------------
CRIS port changes for 3.19

----------------------------------------------------------------
Jesper Nilsson (13):
      CRISv32: Drop obsolete file for SPI driver
      CRISv32: Add missing include for mm.h
      CRIS: Export ioremap_nocache
      CRIS: Export missing function symbols
      CRISv32: Better handling of watchdog bite
      CRIS: Update init memory handling
      CRISv32: Rewrite of synchronous serial port driver
      CRISv32: Fix declaration mismatch
      CRIS: Use KALLSYMs if available in call stack dump
      CRISv32: Implement early console
      CRISv32: Select MTDRAM for axisflashmap
      CRISv32: ETRAXFS: Fix recursive spinlock
      CRISv32: Remove last remnants of ETRAX_SPI_MMC_BOARD

Sam Ravnborg (1):
      CRIS: Fix headers_install

 arch/cris/arch-v10/lib/usercopy.c                |   14 +-
 arch/cris/arch-v32/drivers/Kconfig               |    8 +-
 arch/cris/arch-v32/drivers/Makefile              |    1 -
 arch/cris/arch-v32/drivers/i2c.h                 |    1 -
 arch/cris/arch-v32/drivers/sync_serial.c         | 1430 ++++++++++++----------
 arch/cris/arch-v32/kernel/debugport.c            |   82 +-
 arch/cris/arch-v32/kernel/time.c                 |   29 +-
 arch/cris/arch-v32/lib/usercopy.c                |   15 +-
 arch/cris/arch-v32/mach-fs/pinmux.c              |  152 +--
 arch/cris/include/arch-v32/mach-fs/mach/pinmux.h |    2 -
 arch/cris/include/asm/Kbuild                     |    4 -
 arch/cris/include/uapi/asm/Kbuild                |    4 +-
 arch/cris/kernel/crisksyms.c                     |    9 +-
 arch/cris/kernel/traps.c                         |   61 +-
 arch/cris/mm/init.c                              |   38 +-
 arch/cris/mm/ioremap.c                           |    3 +-
 scripts/headers.sh                               |    2 -
 17 files changed, 1039 insertions(+), 816 deletions(-)

/^JN - Jesper Nilsson
-- 
               Jesper Nilsson -- jesper.nilsson@axis.com

                 reply	other threads:[~2014-12-20  0:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20141220002953.GR26817@axis.com \
    --to=jesper.nilsson@axis.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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