From: Benjamin Berg <benjamin@sipsolutions.net>
To: linux-um@lists.infradead.org
Cc: Benjamin Berg <benjamin.berg@intel.com>
Subject: [PATCH v2 3/5] um: Remove unused os_stop_process
Date: Fri, 13 Sep 2024 15:44:40 +0200 [thread overview]
Message-ID: <20240913134442.967599-4-benjamin@sipsolutions.net> (raw)
In-Reply-To: <20240913134442.967599-1-benjamin@sipsolutions.net>
From: Benjamin Berg <benjamin.berg@intel.com>
The function is not used anywhere.
Signed-off-by: Benjamin Berg <benjamin.berg@intel.com>
---
arch/um/include/shared/os.h | 1 -
arch/um/os-Linux/process.c | 5 -----
2 files changed, 6 deletions(-)
diff --git a/arch/um/include/shared/os.h b/arch/um/include/shared/os.h
index 4bdd4fb5dd80..a94093bfa5e4 100644
--- a/arch/um/include/shared/os.h
+++ b/arch/um/include/shared/os.h
@@ -200,7 +200,6 @@ extern void report_enomem(void);
/* process.c */
extern void os_alarm_process(int pid);
-extern void os_stop_process(int pid);
extern void os_kill_process(int pid, int reap_child);
extern void os_kill_ptraced_process(int pid, int reap_child);
diff --git a/arch/um/os-Linux/process.c b/arch/um/os-Linux/process.c
index b25c226c5491..d1f5e6002805 100644
--- a/arch/um/os-Linux/process.c
+++ b/arch/um/os-Linux/process.c
@@ -23,11 +23,6 @@ void os_alarm_process(int pid)
kill(pid, SIGALRM);
}
-void os_stop_process(int pid)
-{
- kill(pid, SIGSTOP);
-}
-
void os_kill_process(int pid, int reap_child)
{
kill(pid, SIGKILL);
--
2.46.0
next prev parent reply other threads:[~2024-09-13 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 13:44 [PATCH v2 0/5] Minor cleanups for UML Benjamin Berg
2024-09-13 13:44 ` [PATCH v2 1/5] um: Remove unused os_process_pc Benjamin Berg
2024-09-13 13:44 ` [PATCH v2 2/5] um: Remove unused os_process_parent Benjamin Berg
2024-09-13 13:44 ` Benjamin Berg [this message]
2024-09-13 13:44 ` [PATCH v2 4/5] um: Remove unused os_getpgrp function Benjamin Berg
2024-09-13 13:44 ` [PATCH v2 5/5] um: Set HAVE_EFFICIENT_UNALIGNED_ACCESS for x86 Benjamin Berg
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=20240913134442.967599-4-benjamin@sipsolutions.net \
--to=benjamin@sipsolutions.net \
--cc=benjamin.berg@intel.com \
--cc=linux-um@lists.infradead.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).