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 fixes for 4.0-rc4
Date: Thu, 12 Mar 2015 08:57:45 +0100 [thread overview]
Message-ID: <550146F9.2030505@monstr.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
Hi Linus,
please pull these two patches to your tree. One is just preparation
patch for the second which is fixing the problem with syscalls.
Thanks,
Michal
The following changes since commit 13a7a6ac0a11197edcd0f756a035f472b42cdf8b:
Linux 4.0-rc2 (2015-03-03 09:04:59 -0800)
are available in the git repository at:
git://git.monstr.eu/linux-2.6-microblaze.git tags/microblaze-4.0-rc4
for you to fetch changes up to c2219eda547813c0c50dba90d9e989ae36cc3ab8:
microblaze: Fix syscall error recovery for invalid syscall IDs (2015-03-04 15:12:27 +0100)
----------------------------------------------------------------
Microblaze patches for 4.0-rc4
- Fix syscall error recovery
----------------------------------------------------------------
Jamie Garside (1):
microblaze: Fix syscall error recovery for invalid syscall IDs
Michal Simek (1):
microblaze: Coding style cleanup
arch/microblaze/kernel/entry.S | 7 ++++---
1 file changed, 4 insertions(+), 3 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: 198 bytes --]
reply other threads:[~2015-03-12 7:57 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=550146F9.2030505@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