All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Chris Zankel <chris@zankel.net>,
	linux-xtensa@linux-xtensa.org, linux-arch@vger.kernel.org,
	Marc Gauthier <marc@tensilica.com>
Subject: Re: [PATCH 3/3] xtensa: switch to generic sys_execve()
Date: Wed, 24 Oct 2012 15:01:24 +0100	[thread overview]
Message-ID: <20121024140124.GE2616@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAMo8Bf+fkUTDPHh-sbVJj=8SOjMDfpywa=g1sMRFXWfpBhsDYA@mail.gmail.com>

On Wed, Oct 24, 2012 at 01:16:39PM +0400, Max Filippov wrote:
> On Wed, Oct 24, 2012 at 6:41 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > On Wed, Oct 24, 2012 at 05:48:37AM +0400, Max Filippov wrote:
> >> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> >> ---
> >>  arch/xtensa/include/asm/syscall.h     |    2 +-
> >>  arch/xtensa/include/asm/unistd.h      |    1 +
> >>  arch/xtensa/include/uapi/asm/unistd.h |    2 +-
> >>  arch/xtensa/kernel/process.c          |   25 -------------------------
> >>  4 files changed, 3 insertions(+), 27 deletions(-)
> >
> > All three applied, but there's a couple of things I'd like to have on top
> > of that.  Are you OK with the following incremental?
> 
> Yes. Looks like I need to send v2 to address Chris' comments,
> I can put these changes there as well.

Please, do.

      reply	other threads:[~2012-10-24 14:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24  1:48 [PATCH 0/3] xtensa: conversion to generic kernel_thread and friends Max Filippov
2012-10-24  1:48 ` [PATCH 1/3] xtensa: switch to generic kernel_thread() Max Filippov
2012-10-24  1:48 ` [PATCH 2/3] xtensa: switch to generic kernel_execve() Max Filippov
2012-10-24  1:48 ` [PATCH 3/3] xtensa: switch to generic sys_execve() Max Filippov
2012-10-24  2:41   ` Al Viro
2012-10-24  9:16     ` Max Filippov
2012-10-24 14:01       ` Al Viro [this message]

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=20121024140124.GE2616@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=chris@zankel.net \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=marc@tensilica.com \
    /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.