From 3b8b63bf133e855d942abb67de931ce08b7a4452 Mon Sep 17 00:00:00 2001
From: dzwdz
Date: Tue, 20 Sep 2022 23:35:33 +0200
Subject: shared: rename ufs_request to better fit its role in userland

The old name could have suggested that it held a response to a request
received by fs_wait. The new name is unfortunately very similar to
the `struct vfs_request` already used internally in the kernel, but
it's better at conveying that it contains a filesystem request yet to
be handled.

vfs_request - virtual filesystem request (a bad name in hindsight)
ufs_request - user filesystem request
---
 src/kernel/syscalls.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/kernel/syscalls.c')

diff --git a/src/kernel/syscalls.c b/src/kernel/syscalls.c
index 62acf5f..aa3c28f 100644
--- a/src/kernel/syscalls.c
+++ b/src/kernel/syscalls.c
@@ -258,7 +258,7 @@ long _syscall_close(handle_t hid) {
 	SYSCALL_RETURN(0);
 }
 
-handle_t _syscall_fs_wait(char __user *buf, long max_len, struct fs_wait_response __user *res) {
+handle_t _syscall_fs_wait(char __user *buf, long max_len, struct ufs_request __user *res) {
 	struct vfs_backend *backend = process_current->controlled;
 	// TODO can be used to tell if you're init
 	if (!backend) SYSCALL_RETURN(-1);
-- 
cgit v1.2.3