[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72nUkuQ+Bpi6+UE6hMwtngs=yiZcH826mt-wox=7Nq9wWw@mail.gmail.com>
Date: Tue, 13 Jun 2023 01:36:07 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Sven Van Asbroeck <thesven73@...il.com>
Cc: Alice Ryhl <aliceryhl@...gle.com>, rust-for-linux@...r.kernel.org,
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>,
linux-kernel@...r.kernel.org, patches@...ts.linux.dev,
Wedson Almeida Filho <walmeida@...rosoft.com>
Subject: Re: [PATCH v1] rust: error: integrate Rust error type with `errname`
On Mon, Jun 12, 2023 at 9:04 PM Miguel Ojeda
<miguel.ojeda.sandonis@...il.com> wrote:
>
> Applied to `rust-next` -- reworded for clarity. Thanks!
When working on the KUnit changes that require this, I noticed this
didn't include the `CONFIG_SYMBOLIC_ERRNAME=n` support we originally
had on the `rust` branch.
So I added the `errname` helper and force-pushed.
Cheers,
Miguel
Powered by blists - more mailing lists