[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4a1096e9-500e-d764-0a79-289e6559cfb1@gmail.com>
Date: Wed, 14 Jun 2023 13:44:30 -0300
From: Martin Rodriguez Reboredo <yakoyoku@...il.com>
To: "Ethan D. Twardy" <ethan.twardy@...il.com>,
Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...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>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Tom Rix <trix@...hat.com>, Tiago Lam <tiagolam@...il.com>,
Kees Cook <keescook@...omium.org>, Finn Behrens <me@...enk.de>,
"open list:RUST" <rust-for-linux@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
"open list:CLANG/LLVM BUILD SUPPORT" <llvm@...ts.linux.dev>
Subject: Re: [PATCH v2 1/1] scripts/rust_is_available: Fix clang version check
On 6/14/23 09:08, Ethan D. Twardy wrote:
> Greetings, Martin!
>
> Thanks very much for your testing and review. Do I need to take any
> further action to make this patch ready for review? I sent out a v3
> version of the patch, where the only change was adding Reviewed-By and
> Tested-By tags to my git commit--since this is my first time
> contributing to this community, I wasn't sure whether I needed to do
> that. Thanks!
>
> Sincerely,
>
> Ethan Twardy
Unless other reviewers requested changes, you have to rebase your
work or you want to make a modification, it is not necessary to send a
new version of the patch series, generally, maintainers will, and have
to, add any Reviewed-bys or Tested-bys prior to merging.
Powered by blists - more mailing lists