From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH v1] rust: error: add ERESTARTSYS error code
Date: Wed, 3 May 2023 11:50:04 +0200 [thread overview]
Message-ID: <CANiq72mz7rjsQ6kP4ttsMwSozwFWk-CUzChYf+vkKtTV6QtSOg@mail.gmail.com> (raw)
In-Reply-To: <20230503083941.499090-1-aliceryhl@google.com>
On Wed, May 3, 2023 at 10:40 AM Alice Ryhl <aliceryhl@google.com> wrote:
>
> This error code was probably excluded here originally because it never
> actually reaches user programs when a syscall returns it. However, from
The reason is that commit 266def2a0f5b ("rust: error: add codes from
`errno-base.h`") only introduced the ones from
`include/uapi/asm-generic/errno-base.h`, but not the ones from
`include/linux/errno.h` (or `include/uapi/asm-generic/errno.h`).
Given this is an independent patch, should we introduce the rest too, at once?
Cheers,
Miguel
next prev parent reply other threads:[~2023-05-03 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 8:39 [PATCH v1] rust: error: add ERESTARTSYS error code Alice Ryhl
2023-05-03 9:50 ` Miguel Ojeda [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-26 22:57 [PATCH] rust: bindings: fix sorting of rust/bindings/bindings_helper.h's #includes materoy
2023-05-03 10:59 ` [PATCH v1] rust: error: add ERESTARTSYS error code Alice Ryhl
2023-05-03 11:02 ` Alice Ryhl
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=CANiq72mz7rjsQ6kP4ttsMwSozwFWk-CUzChYf+vkKtTV6QtSOg@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--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).