[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72kGXY4gOCC9kqbUht8e23bsQwddk47jE+wzGO8FidJvqA@mail.gmail.com>
Date: Thu, 6 Mar 2025 17:33:56 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Guilherme Giacomo Simoes <trintaeoitogc@...il.com>
Cc: a.hindborg@...nel.org, alex.gaynor@...il.com, aliceryhl@...gle.com,
apw@...onical.com, arnd@...db.de, aswinunni01@...il.com, axboe@...nel.dk,
benno.lossin@...ton.me, bhelgaas@...gle.com, bjorn3_gh@...tonmail.com,
boqun.feng@...il.com, dakr@...nel.org, dwaipayanray1@...il.com,
ethan.twardy@...il.com, fujita.tomonori@...il.com, gary@...yguo.net,
gregkh@...uxfoundation.org, joe@...ches.com, linux-kernel@...r.kernel.org,
lukas.bulwahn@...il.com, ojeda@...nel.org, pbonzini@...hat.com,
rust-for-linux@...r.kernel.org, tmgross@...ch.edu, walmeida@...rosoft.com
Subject: Re: [PATCH V6 2/2] checkpatch: check format of Vec<String> in modules
On Thu, Mar 6, 2025 at 5:32 PM Guilherme Giacomo Simoes
<trintaeoitogc@...il.com> wrote:
>
> the checkpatch don't will throw a warning message, because, he don't can
> perceive that he is within of array of author, firmware or alias of module!.
I wouldn't worry about that case -- it is unlikely we even have the
case, and even if we do, just manually checking it is fine. :)
Cheers,
Miguel
Powered by blists - more mailing lists