linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Greg Ungerer <gregungerer@westnet.com.au>,
	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: Mon, 24 Sep 2012 16:29:14 +0530	[thread overview]
Message-ID: <50603D02.50302@synopsys.com> (raw)
In-Reply-To: <20120923004636.GL13973@ZenIV.linux.org.uk>

On Sunday 23 September 2012 06:16 AM, Al Viro wrote:
> On Sat, Sep 22, 2012 at 09:16:11PM +1000, Greg Ungerer wrote:
>> 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.
> 
> Applied.  Other changes since the last update:
> 	* ppc breakage debugged and fixed
> 	* kernel_thread() unified on all converted architectures.

commit cc615abcde (mn10300: convert to generic kernel_thread) in the
experimental-kernel_thread has a minor syntactical error:

diff --git a/arch/mn10300/kernel/process.c b/arch/mn10300/kernel/process.c
index 26120a9..8ee09d8 100644
--- a/arch/mn10300/kernel/process.c
+++ b/arch/mn10300/kernel/process.c
@@ -225,7 +225,7 @@ int copy_thread(unsigned long clone_flags,
        p->thread.usp   = c_usp;

        if (unlikely(!kregs)) {
-               memset(c_regs, 0, sizeof(struct pt_regs);
+               memset(c_regs, 0, sizeof(struct pt_regs));


Thx,
-Vineet

  parent reply	other threads:[~2012-09-24 10:59 UTC|newest]

Thread overview: 29+ 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:20 ` 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     ` 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         ` Mark Salter
2012-09-21 16:26       ` [PATCH 2/3] c6x: switch to generic kernel_execve Mark Salter
2012-09-21 16:26         ` Mark Salter
2012-09-21 16:26       ` [PATCH 3/3] c6x: switch to generic sys_execve Mark Salter
2012-09-21 16:26         ` 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-23  0:46             ` Al Viro
2012-09-24 10:59             ` Vineet Gupta [this message]
2012-09-17  9:29 ` Michal Simek
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=50603D02.50302@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=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;
as well as URLs for NNTP newsgroup(s).