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/user/app/tests/kernel/path.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/user/app/tests/kernel/path.c')

diff --git a/src/user/app/tests/kernel/path.c b/src/user/app/tests/kernel/path.c
index ddaf692..fd6eeec 100644
--- a/src/user/app/tests/kernel/path.c
+++ b/src/user/app/tests/kernel/path.c
@@ -66,7 +66,7 @@ static void test_path_simplify(void) {
 static void mount_resolve_drv(const char *path) {
 	if (fork2_n_mount(path)) return;
 
-	struct fs_wait_response res;
+	struct ufs_request res;
 	while (!c0_fs_wait(NULL, 0, &res)) {
 		// TODO does the first argument of c0_fs_respond need to be non-const?
 		c0_fs_respond((void*)path, strlen(path), 0);
-- 
cgit v1.2.3