[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231211162717.105915-1-piroyangg@gmail.com>
Date: Tue, 12 Dec 2023 00:27:17 +0800
From: Piro Yang <piroyangg@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Piro Yang <piroyangg@...il.com>, linux-staging@...ts.linux.dev,
Linux Outreachy <outreachy@...ts.linux.dev>,
linux-kernel@...r.kernel.org
Subject: [PATCH v2]staging:vme_user:fix the issue of using the wrong error code
the error code of ENOSYS indicates Invalid system call number, but there is not system call
Signed-off-by: Piro Yang <piroyangg@...il.com>
---
drivers/staging/vme_user/vme.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/vme_user/vme.c b/drivers/staging/vme_user/vme.c
index 5c416c31ec57..9bc2d35405af 100644
--- a/drivers/staging/vme_user/vme.c
+++ b/drivers/staging/vme_user/vme.c
@@ -341,7 +341,7 @@ int vme_slave_set(struct vme_resource *resource, int enabled,
if (!bridge->slave_set) {
dev_err(bridge->parent, "Function not supported\n");
- return -ENOSYS;
+ return -EINVAL;
}
if (!(((image->address_attr & aspace) == aspace) &&
--
2.25.1
Powered by blists - more mailing lists