From: Greg Ungerer <gregungerer@westnet.com.au>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Mark Salter <msalter@redhat.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [RFC] status of execve() work - per-architecture patches solicited
Date: Sat, 22 Sep 2012 21:16:11 +1000 [thread overview]
Message-ID: <505D9DFB.8080002@westnet.com.au> (raw)
In-Reply-To: <20120921183934.GK13973@ZenIV.linux.org.uk>
On 09/22/2012 04:39 AM, Al Viro wrote:
> On Fri, Sep 21, 2012 at 12:26:36PM -0400, Mark Salter wrote:
>> Here are a set of c6x patches to work with your experimental-kernel_thread
>> branch.
>>
>> Mark Salter (3):
>> c6x: add ret_from_kernel_thread(), simplify kernel_thread()
>> c6x: switch to generic kernel_execve
>> c6x: switch to generic sys_execve
>
> Applied and pushed...
>
> FWIW, the current status:
>
> alpha - done, tested on hardware
> arm - done, tested on qemu
> c6x - done by maintainer
> frv - done, untested
> m68k - done, tested on aranym; there's a known issue in copy_thread() in
> case of coldfire-MMU, presumably to be handled in m68k tree (I can do it
> in this one instead, if m68k folks would prefer it that way)
I sent the patch to the m68k-linux list. Its been acked by Geert.
http://marc.info/?l=linux-m68k&m=134742688015639&w=2
I was going to push it through the m68knommu git tree, but I don't mind
if you would rather take it with your changes.
Regards
Greg
next prev parent reply other threads:[~2012-09-22 11:16 UTC|newest]
Thread overview: 22+ 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
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-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 [this message]
2012-09-23 0:46 ` Al Viro
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 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=505D9DFB.8080002@westnet.com.au \
--to=gregungerer@westnet.com.au \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msalter@redhat.com \
--cc=viro@ZenIV.linux.org.uk \
/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