public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: svens@stackframe.org
To: hans-christian.egtvedt@atmel.com
Cc: linux-kernel@vger.kernel.org, svens@stackframe.org
Subject: [Patch v2] AVR32: fix sys_execve build breakage
Date: Thu,  9 Dec 2010 09:26:40 +0100	[thread overview]
Message-ID: <1291883201-7903-1-git-send-email-svens@stackframe.org> (raw)
In-Reply-To: <1291874601.2794.5.camel@hcegtvedt>

> > commit d7627467b7a8dd6944885290a03a07ceb28c10eb change sys_execve()
> > arch/avr32, but the version in syscalls.h is still the old one.
> >
> > Signed-off-by: Sven Schnelle <svens@stackframe.org>
> > ---
> >  arch/avr32/include/asm/syscalls.h |    5 +++++
> >  1 files changed, 5 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/avr32/include/asm/syscalls.h b/arch/avr32/include/asm/syscalls.h
> > index ab608b7..dd69aa0 100644
> > --- a/arch/avr32/include/asm/syscalls.h
> > +++ b/arch/avr32/include/asm/syscalls.h
> > @@ -24,6 +24,11 @@ asmlinkage int sys_vfork(struct pt_regs *);
> >  asmlinkage int sys_execve(const char __user *, char __user *__user *,
> >  			  char __user *__user *, struct pt_regs *);
> >
> > +asmlinkage int sys_execve(const char __user *ufilename,
>
> Invalid patch, double definition of sys_execve.

This should be the right one. Stupid me.


  reply	other threads:[~2010-12-09  8:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21 23:28 AVR32 build fixes Sven Schnelle
2010-11-21 23:28 ` [PATCH 1/2] AVR32: Fix sys_execve breakage Sven Schnelle
2010-12-09  6:03   ` Hans-Christian Egtvedt
2010-12-09  8:26     ` svens [this message]
2010-12-09  8:26     ` [PATCH] " svens
2010-12-09  8:42       ` Hans-Christian Egtvedt
2010-12-09  8:28     ` svens
2010-11-21 23:28 ` [PATCH 2/2] [AVR32] Fix typo in atmel_usba_udc.c Sven Schnelle
2010-11-22  7:19   ` Hans-Christian Egtvedt

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=1291883201-7903-1-git-send-email-svens@stackframe.org \
    --to=svens@stackframe.org \
    --cc=hans-christian.egtvedt@atmel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox