public inbox for linux-parisc@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: linux-parisc@vger.kernel.org
Cc: will@willdeacon.co.uk
Subject: queued parisc patches on top of kernel 3.9
Date: Wed, 24 Apr 2013 00:16:11 +0200	[thread overview]
Message-ID: <20130423221611.GA7841@p100.box> (raw)

Hello everyone,

I've queued up a few patches which I think would be really nice to get
into kernel 3.9 (which isn't that likely since 3.9 is pretty much
closed). Nevertheless, with those patches all my machines have survived
all my tests, including hackbench, using sysrq-t and an load of > 300.

If you want to try, I suggest that you pull the "fixes-3.9-urgent" branch of:

  git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git 

----------------------------------------------------------------
Helge Deller (2):
      parisc: increase kernel stack size to 32k
      parisc: disable -mlong-calls compiler option for kernel modules

John David Anglin (3):
      parisc: Provide __ucmpdi2 to resolve undefined references in 32 bit builds.
      parisc: Change kunmap macro to static inline function
      parisc: use spin_lock_irqsave/spin_unlock_irqrestore for PTE updates

Will Deacon (1):
      parisc: uaccess: fix compiler warnings caused by __put_user casting

 arch/parisc/Makefile                  |  6 +++--
 arch/parisc/include/asm/cacheflush.h  |  5 +++-
 arch/parisc/include/asm/pgtable.h     | 47 +++++++++++++++++++----------------
 arch/parisc/include/asm/thread_info.h |  2 +-
 arch/parisc/include/asm/uaccess.h     | 14 +++--------
 arch/parisc/kernel/cache.c            |  5 +---
 arch/parisc/kernel/parisc_ksyms.c     |  2 ++
 arch/parisc/lib/Makefile              |  3 ++-
 arch/parisc/lib/ucmpdi2.c             | 25 +++++++++++++++++++
 9 files changed, 68 insertions(+), 41 deletions(-)
 create mode 100644 arch/parisc/lib/ucmpdi2.c

                 reply	other threads:[~2013-04-23 22:16 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=20130423221611.GA7841@p100.box \
    --to=deller@gmx.de \
    --cc=linux-parisc@vger.kernel.org \
    --cc=will@willdeacon.co.uk \
    /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