linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	hpa@zytor.com, luto@kernel.org
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: [PATCH] x86/syscalls: deasmlinkage syscall table definition
Date: Tue, 3 Mar 2020 23:36:42 +0300	[thread overview]
Message-ID: <20200303203642.GA9737@avx2> (raw)

I think that "sys_call_ptr_t" type being function pointer to asmlinkage
function is enough, array itself doesn't need to be asmlinkage.

It is not referenced by assembly code anymore anyway.

Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
---

 arch/x86/entry/syscall_64.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- a/arch/x86/entry/syscall_64.c
+++ b/arch/x86/entry/syscall_64.c
@@ -24,7 +24,7 @@ SYSCALL_DEFINE0(ni_syscall)
 #define __SYSCALL_64(nr, sym, qual) [nr] = sym,
 #define __SYSCALL_X32(nr, sym, qual)
 
-asmlinkage const sys_call_ptr_t sys_call_table[__NR_syscall_max+1] = {
+const sys_call_ptr_t sys_call_table[__NR_syscall_max + 1] = {
 	/*
 	 * Smells like a compiler bug -- it doesn't work
 	 * when the & below is removed.
@@ -41,7 +41,7 @@ asmlinkage const sys_call_ptr_t sys_call_table[__NR_syscall_max+1] = {
 #define __SYSCALL_64(nr, sym, qual)
 #define __SYSCALL_X32(nr, sym, qual) [nr] = sym,
 
-asmlinkage const sys_call_ptr_t x32_sys_call_table[__NR_syscall_x32_max+1] = {
+const sys_call_ptr_t x32_sys_call_table[__NR_syscall_x32_max + 1] = {
 	/*
 	 * Smells like a compiler bug -- it doesn't work
 	 * when the & below is removed.

                 reply	other threads:[~2020-03-03 20:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200303203642.GA9737@avx2 \
    --to=adobriyan@gmail.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).