mirror of https://lore.kernel.org/lkml/
 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.8-rc3
Date: Mon, 07 Jan 2013 15:52:22 +0100	[thread overview]
Message-ID: <50EAE126.4020407@monstr.eu> (raw)

Hi Linus,

this is fixed pull request (origin one was sent some days ago).
I have fixed defconfigs as you suggested. In that meantime I have
also found 3 other things which needs to be fixed which are also
included (Highmem fixup and pci warnings reported by 0-day testing system).

Thanks,
Michal



The following changes since commit d1c3ed669a2d452cacfb48c2d171a1f364dae2ed:
   Linus Torvalds (1):
         Linux 3.8-rc2

are available in the git repository at:

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

Michal Simek (6):
       microblaze: Microblaze wants sys_fork for noMMU too
       microblaze: Change section flags for noMMU
       microblaze: Kill __kmap_atomic()
       microblaze: Add finit_module syscall
       microblaze: Fix pci compilation and sparse warnings
       microblaze: Update microblaze defconfigs

  arch/microblaze/configs/mmu_defconfig     |   52 ++++++++++++++------
  arch/microblaze/configs/nommu_defconfig   |   73 +++++++++++++++++-----------
  arch/microblaze/include/asm/highmem.h     |    2 +-
  arch/microblaze/include/asm/uaccess.h     |    2 +-
  arch/microblaze/include/asm/unistd.h      |    2 -
  arch/microblaze/include/uapi/asm/unistd.h |    3 +-
  arch/microblaze/kernel/syscall_table.S    |    1 +
  arch/microblaze/pci/pci-common.c          |   11 ++--
  8 files changed, 90 insertions(+), 56 deletions(-)



-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

                 reply	other threads:[~2013-01-07 14:59 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=50EAE126.4020407@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

Powered by JetHome