qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aleksandar Markovic <aleksandar.markovic@rt-rk.com>
To: qemu-devel@nongnu.org
Cc: Max Filippov <jcmvbkbc@gmail.com>,
	laurent@vivier.eu, amarkovic@wavecomp.com
Subject: [PATCH 9/9] linux-user: xtensa: Remove unused constant TARGET_NR_syscall_count
Date: Tue,  4 Feb 2020 13:07:38 +0100	[thread overview]
Message-ID: <1580818058-16159-10-git-send-email-aleksandar.markovic@rt-rk.com> (raw)
In-Reply-To: <1580818058-16159-1-git-send-email-aleksandar.markovic@rt-rk.com>

From: Aleksandar Markovic <amarkovic@wavecomp.com>

Currently, there is no usage of TARGET_NR_syscall_count for target
xtensa, and there is no obvious indication if there is some planned
usage in future.

CC: Max Filippov <jcmvbkbc@gmail.com>
Acked-by: Max Filippov <jcmvbkbc@gmail.com>
Signed-off-by: Aleksandar Markovic <amarkovic@wavecomp.com>
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
---
 linux-user/xtensa/syscall_nr.h | 2 --
 1 file changed, 2 deletions(-)

diff --git a/linux-user/xtensa/syscall_nr.h b/linux-user/xtensa/syscall_nr.h
index 3d19d0c..39bff65 100644
--- a/linux-user/xtensa/syscall_nr.h
+++ b/linux-user/xtensa/syscall_nr.h
@@ -466,6 +466,4 @@
 #define TARGET_NR_pidfd_open                         434
 #define TARGET_NR_clone3                             435
 
-#define TARGET_NR_syscall_count                      436
-
 #endif /* XTENSA_SYSCALL_NR_H */
-- 
2.7.4



  parent reply	other threads:[~2020-02-04 12:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 12:07 [PATCH 0/9] linux-user: Update syscall numbers to kernel 5.5 level Aleksandar Markovic
2020-02-04 12:07 ` [PATCH 1/9] linux-user: alpha: " Aleksandar Markovic
2020-02-04 12:07 ` [PATCH 2/9] linux-user: arm: " Aleksandar Markovic
2020-02-12 21:18   ` Laurent Vivier
2020-02-04 12:07 ` [PATCH 3/9] linux-user: m68k: " Aleksandar Markovic
2020-02-04 12:07 ` [PATCH 4/9] linux-user: microblaze: " Aleksandar Markovic
2020-02-04 12:07 ` [PATCH 5/9] linux-user: mips: " Aleksandar Markovic
2020-02-12 21:09   ` Laurent Vivier
2020-02-13  1:26     ` Aleksandar Markovic
2020-02-04 12:07 ` [PATCH 6/9] linux-user: sh4: " Aleksandar Markovic
2020-02-12 20:38   ` Laurent Vivier
2020-02-04 12:07 ` [PATCH 7/9] linux-user: x86_64: " Aleksandar Markovic
2020-02-04 12:07 ` [PATCH 8/9] linux-user: xtensa: " Aleksandar Markovic
2020-02-04 12:07 ` Aleksandar Markovic [this message]
2020-02-04 12:30 ` [PATCH 0/9] linux-user: " Aleksandar Markovic
2020-02-05 21:29 ` Stafford Horne
2020-02-12 21:34 ` Laurent Vivier
2020-02-13  0:28   ` Laurent Vivier

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=1580818058-16159-10-git-send-email-aleksandar.markovic@rt-rk.com \
    --to=aleksandar.markovic@rt-rk.com \
    --cc=amarkovic@wavecomp.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.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).