From: Michal Simek <monstr@monstr.eu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] arch/microblaze changes for 3.11
Date: Wed, 10 Jul 2013 15:14:26 +0200 [thread overview]
Message-ID: <51DD5E32.8030603@monstr.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]
Hi Linus,
this Microblaze merge window is quite minimal.
I have also added to my branch one xilinx systemace sparse fix
because haven't got any reply from block maintainer.
Thanks,
Michal
The following changes since commit 9e895ace5d82df8929b16f58e9f515f6d54ab82d:
Linux 3.10-rc7 (2013-06-22 09:47:31 -1000)
are available in the git repository at:
git://git.monstr.eu/linux-2.6-microblaze.git next
for you to fetch changes up to 4937a269cb063915d50e47c68493679b7fe0ffb7:
xilinx systemace: Fix sparse warnings (2013-07-10 07:47:12 +0200)
----------------------------------------------------------------
Graeme Smecher (1):
microblaze: Don't mark arch_kgdb_ops as const.
Michal Simek (3):
microblaze: Enable KGDB in defconfig
microblaze: Move __NR_syscalls from uapi
xilinx systemace: Fix sparse warnings
arch/microblaze/configs/mmu_defconfig | 4 +++-
arch/microblaze/include/asm/unistd.h | 3 +++
arch/microblaze/include/uapi/asm/unistd.h | 2 --
arch/microblaze/kernel/kgdb.c | 2 +-
drivers/block/xsysace.c | 4 ++--
5 files changed, 9 insertions(+), 6 deletions(-)
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
reply other threads:[~2013-07-10 13:14 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=51DD5E32.8030603@monstr.eu \
--to=monstr@monstr.eu \
--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