All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Mikael Starvik <starvik@axis.com>,
	Jesper Nilsson <jespern@axis.com>,
	linux-cris-kernel <linux-cris-kernel@axis.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Chen Gang <gang.chen.5i5j@gmail.com>
Subject: Re: [PATCH -next] cris: Fix system call references for cris v10
Date: Mon, 8 Jun 2015 09:17:51 +0200	[thread overview]
Message-ID: <20150608071751.GL26605@axis.com> (raw)
In-Reply-To: <1433513419-7020-1-git-send-email-linux@roeck-us.net>

On Fri, Jun 05, 2015 at 04:10:19PM +0200, Guenter Roeck wrote:
> The newly wired system calls cause compile errors when building
> crisv10 images.
> 
> arch/cris/arch-v10/kernel/built-in.o: In function `sys_call_table':
> (.rodata+0x580): undefined reference to `_sys_sched_setattr'
> arch/cris/arch-v10/kernel/built-in.o: In function `sys_call_table':
> (.rodata+0x584): undefined reference to `_sys_sched_getattr'
> arch/cris/arch-v10/kernel/built-in.o: In function `sys_call_table':
> (.rodata+0x588): undefined reference to `_sys_renameat2'
> arch/cris/arch-v10/kernel/built-in.o: In function `sys_call_table':
> (.rodata+0x58c): undefined reference to `_sys_seccomp'
> arch/cris/arch-v10/kernel/built-in.o: In function `sys_call_table':
> (.rodata+0x590): undefined reference to `_sys_getrandom'
> arch/cris/arch-v10/kernel/built-in.o: In function `sys_call_table':
> (.rodata+0x594): undefined reference to `_sys_memfd_create'
> arch/cris/arch-v10/kernel/built-in.o: In function `sys_call_table':
> (.rodata+0x598): undefined reference to `_sys_bpf'
> arch/cris/arch-v10/kernel/built-in.o: In function `sys_call_table':
> (.rodata+0x59c): undefined reference to `_sys_execveat'
> 
> Fixes: 3e48d266639b ("CRIS: Wire up missing syscalls")
> Cc: Chen Gang <gang.chen.5i5j@gmail.com>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>

Hi Guenter!

Thanks, a similar patch should already be folded into the
original tree, could you verify with the latest for-next/linux-next?

/^JN - Jesper Nilsson
-- 
               Jesper Nilsson -- jesper.nilsson@axis.com

  reply	other threads:[~2015-06-08  7:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 14:10 [PATCH -next] cris: Fix system call references for cris v10 Guenter Roeck
2015-06-08  7:17 ` Jesper Nilsson [this message]
2015-06-08 14:49   ` Guenter Roeck

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=20150608071751.GL26605@axis.com \
    --to=jesper.nilsson@axis.com \
    --cc=gang.chen.5i5j@gmail.com \
    --cc=jespern@axis.com \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=starvik@axis.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 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.