From: Abdiel Janulgue <abdiel.janulgue@gmail.com>
To: rust-for-linux@vger.kernel.org
Cc: daniel.almeida@collabora.com, a.hindborg@kernel.org,
linux-kernel@vger.kernel.org, dakr@redhat.com,
airlied@redhat.com, miguel.ojeda.sandonis@gmail.com,
wedsonaf@gmail.com, Abdiel Janulgue <abdiel.janulgue@gmail.com>
Subject: [PATCH v2 1/2] rust: error: Add EOVERFLOW
Date: Fri, 1 Nov 2024 13:33:23 +0200 [thread overview]
Message-ID: <20241101113422.2615566-2-abdiel.janulgue@gmail.com> (raw)
In-Reply-To: <20241101113422.2615566-1-abdiel.janulgue@gmail.com>
Trivial addition for missing EOVERFLOW error. This is used in the
subsequent patch that might require returning EOVERFLOW as a resut
of `checked_mul`.
Signed-off-by: Abdiel Janulgue <abdiel.janulgue@gmail.com>
---
rust/kernel/error.rs | 1 +
1 file changed, 1 insertion(+)
diff --git a/rust/kernel/error.rs b/rust/kernel/error.rs
index 7cd3bbab52f2..92bfdaaedb02 100644
--- a/rust/kernel/error.rs
+++ b/rust/kernel/error.rs
@@ -63,6 +63,7 @@ macro_rules! declare_err {
declare_err!(EPIPE, "Broken pipe.");
declare_err!(EDOM, "Math argument out of domain of func.");
declare_err!(ERANGE, "Math result not representable.");
+ declare_err!(EOVERFLOW, "Value too large for defined data type.");
declare_err!(ERESTARTSYS, "Restart the system call.");
declare_err!(ERESTARTNOINTR, "System call was interrupted by a signal and will be restarted.");
declare_err!(ERESTARTNOHAND, "Restart if no handler.");
--
2.43.0
next prev parent reply other threads:[~2024-11-01 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 11:33 [PATCH v2 0/2] Add dma coherent allocator abstraction Abdiel Janulgue
2024-11-01 11:33 ` Abdiel Janulgue [this message]
2024-11-01 11:33 ` [PATCH v2 2/2] rust: add " Abdiel Janulgue
2024-11-03 3:41 ` kernel test robot
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=20241101113422.2615566-2-abdiel.janulgue@gmail.com \
--to=abdiel.janulgue@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=airlied@redhat.com \
--cc=dakr@redhat.com \
--cc=daniel.almeida@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
/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).