[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72=YQyqtpXZ+Hp9oySwfmBS6OJ1ik-zxXx4mSF34hruqbQ@mail.gmail.com>
Date: Fri, 16 Jun 2023 02:41:34 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: "Ethan D. Twardy" <ethan.twardy@...il.com>
Cc: Martin Rodriguez Reboredo <yakoyoku@...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 Wed, Jun 14, 2023 at 2:08 PM Ethan D. Twardy <ethan.twardy@...il.com> wrote:
>
> 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!
You did everything well! The patch looked fine to me, and the commit
message is detailed. The tags are all fine too. Thanks a lot for the
effort!
I had v2 of the script improvement patch series in my backlog, which
normalizes to `sed` (rather than use `grep`/`cut` etc.), adds a test
suite, and a few other things; but otherwise we could have easily
taken this one, because it is well done.
So, you did everything right, and you are more than welcome to send
more patches like that :)
Cheers,
Miguel
Powered by blists - more mailing lists