From: Al Viro <viro@ZenIV.linux.org.uk>
To: linux-arch@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] status of execve() work - per-architecture patches solicited
Date: Fri, 7 Sep 2012 19:22:10 +0100 [thread overview]
Message-ID: <20120907182210.GF13973@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20120907182004.GE13973@ZenIV.linux.org.uk>
On Fri, Sep 07, 2012 at 07:20:04PM +0100, Al Viro wrote:
> To architecture maintainers: please, review the current
> situation in git.kernel.org/pub/scm/linux/kernel/git/viro/signal #execve2
It should be commit 50343ee2889f5a8cff1aa30110f07b0e01563500 right now.
next prev parent reply other threads:[~2012-09-07 18:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 18:20 [RFC] status of execve() work - per-architecture patches solicited Al Viro
2012-09-07 18:22 ` Al Viro [this message]
2012-09-10 13:40 ` Greg Ungerer
2012-09-10 16:49 ` Al Viro
2012-09-11 3:39 ` Greg Ungerer
2012-09-13 13:27 ` Greg Ungerer
2012-09-13 13:27 ` Greg Ungerer
2012-09-10 22:20 ` Mark Salter
2012-09-10 22:20 ` [PATCH 1/2] c6x: implement ret_from_kernel_execve() and switch to generic kernel_execve() Mark Salter
2012-09-10 22:20 ` [PATCH 2/2] c6x: switch to generic sys_execve() Mark Salter
2012-09-17 3:26 ` [RFC] status of execve() work - per-architecture patches solicited Al Viro
2012-09-21 16:26 ` Mark Salter
2012-09-21 16:26 ` [PATCH 1/3] c6x: add ret_from_kernel_thread(), simplify kernel_thread() Mark Salter
2012-09-21 16:26 ` [PATCH 2/3] c6x: switch to generic kernel_execve Mark Salter
2012-09-21 16:26 ` [PATCH 3/3] c6x: switch to generic sys_execve Mark Salter
2012-09-21 18:39 ` [RFC] status of execve() work - per-architecture patches solicited Al Viro
2012-09-22 11:16 ` Greg Ungerer
2012-09-23 0:46 ` Al Viro
2012-09-24 10:59 ` Vineet Gupta
2012-09-24 10:59 ` Vineet Gupta
2012-09-17 9:29 ` Michal Simek
2012-09-17 22:57 ` Al Viro
2012-09-19 12:20 ` Vineet Gupta
2012-09-19 12:20 ` Vineet Gupta
2012-09-19 13:32 ` Al Viro
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=20120907182210.GF13973@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@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.