public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 3.10-rc5
Date: Tue, 04 Jun 2013 09:46:21 +0200	[thread overview]
Message-ID: <51AD9B4D.5060705@monstr.eu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]

Hi Linus,

please pull these two fixes to your tree.
One is fixing warning reported by sparse and the second warning
was reported by Geert in his build regressions/improvements status update
for -rc4.

Thanks,
Michal

The following changes since commit d683b96b072dc4680fc74964eca77e6a23d1fa6e:

  Linux 3.10-rc4 (2013-06-02 17:11:17 +0900)

are available in the git repository at:

  git://git.monstr.eu/linux-2.6-microblaze.git next

for you to fetch changes up to 62bc82a82bb1e2b5ee5048c088af7260ddb2b7b5:

  microblaze: Use static inline functions in cacheflush.h (2013-06-03 11:33:23 +0200)

----------------------------------------------------------------
Michal Simek (2):
      microblaze: Fix sparse warnings
      microblaze: Use static inline functions in cacheflush.h

 arch/microblaze/include/asm/cacheflush.h | 34 ++++++++++++++++++----------------
 arch/microblaze/include/asm/uaccess.h    |  4 ++--
 2 files changed, 20 insertions(+), 18 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-06-04  7:46 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=51AD9B4D.5060705@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