[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72mz7rjsQ6kP4ttsMwSozwFWk-CUzChYf+vkKtTV6QtSOg@mail.gmail.com>
Date: Wed, 3 May 2023 11:50:04 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Alice Ryhl <aliceryhl@...gle.com>
Cc: Miguel Ojeda <ojeda@...nel.org>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev
Subject: Re: [PATCH v1] rust: error: add ERESTARTSYS error code
On Wed, May 3, 2023 at 10:40 AM Alice Ryhl <aliceryhl@...gle.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
Powered by blists - more mailing lists