parisc updates for v3.10

Linus,

please pull the parisc architecture updates for v3.10 from:

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

Main fixes and updates in this patch series are:
- we faced kernel stack corruptions because of multiple delivery of interrupts
- added kernel stack overflow checks
- added possibility to use dedicated stacks for irq processing
- initial support for page sizes > 4k
- more information in /proc/interrupts (e.g. TLB flushes and number of IPI calls)
- documented how the parisc gateway page works
- and of course quite some other smaller cleanups and fixes.

Thanks,
Helge

----------------------------------------------------------------
Damian Hobson-Garcia (1):
parisc: Provide default implementation for dma_{alloc, free}_attrs

Helge Deller (7):
parisc: fix partly 16/64k PAGE_SIZE boot
parisc: document the parisc gateway page
parisc: implement atomic64_dec_if_positive()
parisc: add kernel stack overflow check
parisc: implement irq stacks
parisc: more irq statistics in /proc/interrupts
parisc: tlb flush counting fix for SMP and UP

John David Anglin (2):
parisc: use long branch in fork_like macro
parisc: only re-enable interrupts if we need to schedule or deliver signals when returning to userspace

Mike Frysinger (1):
parisc: fix NATIVE set up in build

Rolf Eike Beer (1):
parisc: fix whitespace errors in arch/parisc/kernel/traps.c

Zhao Hongjiang (1):
parisc: remove the second argument of kmap_atomic

 arch/parisc/Kconfig                   |   9 +++
 arch/parisc/Kconfig.debug             |  11 ++++
 arch/parisc/Makefile                  |   4 +-
 arch/parisc/include/asm/atomic.h      |  23 ++++++++
 arch/parisc/include/asm/dma-mapping.h |   3 +
 arch/parisc/include/asm/hardirq.h     |  32 ++++++++++-
 arch/parisc/include/asm/processor.h   |  20 ++++++-
 arch/parisc/include/asm/thread_info.h |   2 +-
 arch/parisc/include/asm/tlbflush.h    |   2 +
 arch/parisc/kernel/cache.c            |   6 +-
 arch/parisc/kernel/entry.S            |  68 +++++++++++++++++++---
 arch/parisc/kernel/hpmc.S             |   4 +-
 arch/parisc/kernel/irq.c              | 104 +++++++++++++++++++++++++++++++++-
 arch/parisc/kernel/pacache.S          |  33 ++++++-----
 arch/parisc/kernel/setup.c            |   2 +
 arch/parisc/kernel/smp.c              |  14 +----
 arch/parisc/kernel/syscall.S          |  34 +++++++++--
 arch/parisc/kernel/traps.c            |  24 ++++----
 arch/parisc/kernel/vmlinux.lds.S      |   2 +-
 arch/parisc/mm/init.c                 |   2 +
 drivers/parisc/sba_iommu.c            |  19 +++++--
 21 files changed, 348 insertions(+), 70 deletions(-)

Hi Guys,

Does this mean that the parisc tree I have in linux-next
(git://git.kernel.org/pub/scm/linux/kernel/git/jejb/parisc-2.6.git#for-next)
is defunct?

Cheers,
Stephen Rothwell                    [email protected]

Hi Stephen,

Not sure. It will be either James or me who will send pull requests... Of course we will agree who of us will do that and from which tree.

So, would it hurt if you add a second parisc tree for linux-next? I've just created a "for-next" branch in my git repository:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git#for-next

Helge

Hi Helge,

I have no problem having both trees in linux-next (as long as you don't tread on each other's toes and cause merge problem too often :-)).

I have added your tree from today (noting that it is empty). I have set you and the parisc mailing list as contacts.

Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.

Cheers,
Stephen Rothwell 
[email protected]

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.