public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@in.ibm.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-s390@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	dhowells@redhat.com
Subject: Re: [s390] Build failure with latest 2.6.36-rc1 git (sys_execve)
Date: Mon, 23 Aug 2010 19:07:40 +0530	[thread overview]
Message-ID: <4C7279A4.5040606@in.ibm.com> (raw)
In-Reply-To: <20100819094444.28e7b2e4@mschwide.boeblingen.de.ibm.com>

Martin Schwidefsky wrote:
> On Thu, 19 Aug 2010 10:30:06 +0530
> Sachin Sant <sachinp@in.ibm.com> wrote:
>
>   
>> Latest 2.6.36-rc1 git fails to build on a s390 with
>>
>> arch/s390/kernel/process.c:272: error: conflicting types for 'sys_execve'
>> arch/s390/kernel/entry.h:45: error: previous declaration of 'sys_execve' was here
>> make[1]: *** [arch/s390/kernel/process.o] Error 1
>>
>> This error was introduced via commit :
>>
>> commit d7627467b7a8dd6944885290a03a07ceb28c10eb
>> Make do_execve() take a const filename pointer
>>
>> I guess the corresponding definition of sys_execve()
>> in arch/s390/kernel/entry.h also needs an update.
>>     
>
> Fix is uploaded to git390. Tomorrows -next tree should work again.
>   
The patch is still missing from Linus's tree.
2.6.36-rc2-git1 (9ee4747..) fails with the same error.

Thanks
-Sachin


-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------


      reply	other threads:[~2010-08-23 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19  5:00 [s390] Build failure with latest 2.6.36-rc1 git (sys_execve) Sachin Sant
2010-08-19  7:44 ` Martin Schwidefsky
2010-08-23 13:37   ` Sachin Sant [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=4C7279A4.5040606@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=schwidefsky@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox