All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: kyle@mcmartin.ca
Cc: linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: What's in parisc-2.6.git
Date: Mon, 28 Sep 2009 22:19:21 +0200	[thread overview]
Message-ID: <4AC11A49.7080009@gmx.de> (raw)
In-Reply-To: <20090928162522.GA22368@hera.kernel.org>

On 09/28/2009 06:25 PM, Kyle McMartin wrote:
> Rebased on top of v2.6.32-rc1, fixed tracehook. Seems to build alright
> on my pa8800 in a few different configs. Is anything missing?


I did tested it on my boxes as well, and it seems OK.
Nothing important missing.
Thanks Kyle!

Helge

> regards, Kyle
>
> The following changes since commit 17d857be649a21ca90008c6dc425d849fa83db5c:
>    Linus Torvalds (1):
>          Linux 2.6.32-rc1
>
> are available in the git repository at:
>
>    git://git.kernel.org/pub/scm/linux/kernel/git/kyle/parisc-2.6.git parisc
>
> Christoph Hellwig (1):
>        parisc: convert to asm-generic/hardirq.h
>
> Helge Deller (2):
>        parisc: rename parisc's vmalloc_start to parisc_vmalloc_start
>        parisc: Fix linker script breakage.
>
> James Bottomley (1):
>        parisc: add me to Maintainers
>
> Jaswinder Singh Rajput (1):
>        parisc: includecheck fix: signal.c
>
> Julia Lawall (1):
>        parisc: correct use of SHF_ALLOC
>
> Kyle McMartin (7):
>        parisc: tracehook_report_syscall
>        parisc: tracehook_signal_handler
>        parisc: add missing TI_TASK macro in syscall.S
>        parisc: split syscall_trace into two halves
>        parisc: stop using task->ptrace for {single,block}step flags
>        parisc: add skeleton syscall.h
>        parisc: HAVE_ARCH_TRACEHOOK
>
> Tim Abbott (1):
>        parisc: Make THREAD_SIZE available to assembly files and linker scripts.
>
>   MAINTAINERS                           |    1 +
>   arch/parisc/Kconfig                   |    1 +
>   arch/parisc/include/asm/fixmap.h      |    4 +-
>   arch/parisc/include/asm/hardirq.h     |   20 +---------------
>   arch/parisc/include/asm/ptrace.h      |    5 +++-
>   arch/parisc/include/asm/syscall.h     |   40 +++++++++++++++++++++++++++++++
>   arch/parisc/include/asm/thread_info.h |   14 +++++++----
>   arch/parisc/kernel/asm-offsets.c      |    4 +-
>   arch/parisc/kernel/entry.S            |   21 ++++++++--------
>   arch/parisc/kernel/irq.c              |    5 ----
>   arch/parisc/kernel/module.c           |    2 +-
>   arch/parisc/kernel/ptrace.c           |   42 ++++++++++++++++----------------
>   arch/parisc/kernel/signal.c           |    5 +++-
>   arch/parisc/kernel/syscall.S          |   22 +++++++++++------
>   arch/parisc/kernel/vmlinux.lds.S      |   10 ++++++++
>   arch/parisc/mm/init.c                 |   11 ++++----
>   16 files changed, 127 insertions(+), 80 deletions(-)
>   create mode 100644 arch/parisc/include/asm/syscall.h
>

  reply	other threads:[~2009-09-28 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28 16:25 What's in parisc-2.6.git Kyle McMartin
2009-09-28 20:19 ` Helge Deller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-23 16:15 what's " Kyle McMartin
2009-06-24  0:29 ` John David Anglin
2009-06-24  0:41   ` Kyle McMartin

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=4AC11A49.7080009@gmx.de \
    --to=deller@gmx.de \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.