xenomai.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: xenomai@lists.linux.dev, jan.kiszka@siemens.com
Cc: Florian Bezdeka <florian.bezdeka@siemens.com>
Subject: [PATCH v3 1/7] cobalt/posix/syscall32: Remove unused mq_fetch_timeout
Date: Tue, 01 Aug 2023 11:29:35 +0200	[thread overview]
Message-ID: <20230630-florian-y2038-part-four-upstreaming-v3-1-2aea39ad909a@siemens.com> (raw)
In-Reply-To: <20230630-florian-y2038-part-four-upstreaming-v3-0-2aea39ad909a@siemens.com>

Removal of unused (and broken) code. Using cobalt_get_u_timespec would
have been wrong and sys32_fetch_timespec would have been correct.

Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
---
 kernel/cobalt/posix/syscall32.c | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/kernel/cobalt/posix/syscall32.c b/kernel/cobalt/posix/syscall32.c
index 780d276b1..c82cc60a2 100644
--- a/kernel/cobalt/posix/syscall32.c
+++ b/kernel/cobalt/posix/syscall32.c
@@ -318,12 +318,6 @@ COBALT_SYSCALL32emu(mq_timedreceive64, primary,
 	return ret ?: cobalt_copy_to_user(u_len, &clen, sizeof(*u_len));
 }
 
-static inline int mq_fetch_timeout(struct timespec64 *ts,
-				   const void __user *u_ts)
-{
-	return u_ts == NULL ? -EFAULT : cobalt_get_u_timespec(ts, u_ts);
-}
-
 COBALT_SYSCALL32emu(mq_notify, primary,
 		    (mqd_t fd, const struct compat_sigevent *__user u_cev))
 {

-- 
2.39.2


  reply	other threads:[~2023-08-01  9:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01  9:29 [PATCH v3 0/7] y2038: Add time64_t support to scheduler and thread APIs Florian Bezdeka
2023-08-01  9:29 ` Florian Bezdeka [this message]
2023-08-01  9:29 ` [PATCH v3 2/7] y2038: cobalt/uapi: Migrate struct sched_param_ex to time64_t Florian Bezdeka
2023-08-01  9:29 ` [PATCH v3 3/7] y2038: cobalt/uapi: Remove __user_old_{timespec,itimerspec,timeval,timex} Florian Bezdeka
2023-08-01  9:29 ` [PATCH v3 4/7] y2038: cobalt/{thread,sched}: Remove obsolete compat handling Florian Bezdeka
2023-08-01  9:29 ` [PATCH v3 5/7] cobalt/uapi: Move to data types with fixed sizes Florian Bezdeka
2023-08-01  9:29 ` [PATCH v3 6/7] include/rtdm/serial.h: " Florian Bezdeka
2023-08-01  9:29 ` [PATCH v3 7/7] include/rtdm/serial.h: Fix compat support of struct rtser_config Florian Bezdeka
2023-08-01 20:49   ` Richard Weinberger
2023-08-09  6:47 ` [PATCH v3 0/7] y2038: Add time64_t support to scheduler and thread APIs Jan Kiszka

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=20230630-florian-y2038-part-four-upstreaming-v3-1-2aea39ad909a@siemens.com \
    --to=florian.bezdeka@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@lists.linux.dev \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).