public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@redhat.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, laijs@cn.fujitsu.com,
	lizf@cn.fujitsu.com, rostedt@goodmis.org, fweisbec@gmail.com,
	mingo@elte.hu, hpa@zytor.com, tglx@linutronix.de,
	mhiramat@redhat.com, Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH 4/6] tracing: add tracing support for compat syscalls
Date: Tue, 9 Feb 2010 09:54:27 -0500	[thread overview]
Message-ID: <20100209145427.GA30309@redhat.com> (raw)
In-Reply-To: <20100209102100.GA23838@osiris.boeblingen.de.ibm.com>

On Tue, Feb 09, 2010 at 11:21:00AM +0100, Heiko Carstens wrote:
> > is there a way for s390 to use the common include/linux/compat.h file?
> > what other arch defs are required? 
> 
> The patch below is the smallest solution so that s390 still compiles
> and probably even works:
> 
> Subject: [PATCH] compat: have generic is_compat_task for !CONFIG_COMPAT
> 
> From: Heiko Carstens <heiko.carstens@de.ibm.com>
> 
> ..instead of an arch specific one.
> 
> Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
> ---
>  arch/s390/include/asm/compat.h  |    7 -------
>  arch/s390/kernel/ptrace.c       |    2 +-
>  arch/s390/kernel/setup.c        |    2 +-
>  arch/s390/mm/mmap.c             |    2 +-
>  drivers/s390/block/dasd_eckd.c  |    2 +-
>  drivers/s390/block/dasd_ioctl.c |    1 +
>  drivers/s390/char/fs3270.c      |    1 +
>  drivers/s390/char/vmcp.c        |    1 +
>  drivers/s390/cio/chsc_sch.c     |    1 +
>  drivers/s390/scsi/zfcp_cfdc.c   |    1 +
>  include/linux/compat.h          |    7 +++++++
>  11 files changed, 16 insertions(+), 11 deletions(-)
> 

looks good. I'll include this patch when I repost the revised series.

thanks!

-Jason

  reply	other threads:[~2010-02-09 14:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 21:21 [PATCH 0/6] tracing: add compat syscall support Jason Baron
2010-02-02 21:21 ` [PATCH 1/6] x86: add NR_syscalls_compat, make ia32 syscall table visible Jason Baron
2010-02-02 21:21 ` [PATCH 2/6] x86: add arch_compat_syscall_addr() Jason Baron
2010-02-02 21:21 ` [PATCH 3/6] tracing: remove syscall bitmaps in preparation for compat support Jason Baron
2010-02-02 21:21 ` [PATCH 4/6] tracing: add tracing support for compat syscalls Jason Baron
2010-02-03 12:52   ` Heiko Carstens
2010-02-08 15:43     ` Jason Baron
2010-02-08 16:34       ` Heiko Carstens
2010-02-09 10:21       ` Heiko Carstens
2010-02-09 14:54         ` Jason Baron [this message]
2010-02-02 21:21 ` [PATCH 5/6] syscalls: add define syscall prefix macro Jason Baron
2010-02-03 13:01   ` Heiko Carstens
2010-02-08 15:48     ` Jason Baron
2010-02-08 16:12       ` Arnd Bergmann
2010-02-08 17:54         ` Christoph Hellwig
2010-02-08 20:48           ` Arnd Bergmann
2010-02-08 16:53       ` Randy Dunlap
2010-02-08 17:11         ` Jason Baron
2010-02-10  3:00           ` Steven Rostedt
2010-02-02 21:22 ` [PATCH 6/6] x86: convert compat syscalls to use 'DEFINE_SYSCALL()' macros Jason Baron

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=20100209145427.GA30309@redhat.com \
    --to=jbaron@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hpa@zytor.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mhiramat@redhat.com \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tglx@linutronix.de \
    /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