[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20241209131443.415158-1-trintaeoitogc@gmail.com>
Date: Mon, 9 Dec 2024 10:14:43 -0300
From: guilherme giacomo simoes <trintaeoitogc@...il.com>
To: daniel@...lak.dev
Cc: a.hindborg@...nel.org,
alex.gaynor@...il.com,
aliceryhl@...gle.com,
benno.lossin@...ton.me,
bjorn3_gh@...tonmail.com,
boqun.feng@...il.com,
fujita.tomonori@...il.com,
gary@...yguo.net,
linux-kernel@...r.kernel.org,
miguel.ojeda.sandonis@...il.com,
ojeda@...nel.org,
rust-for-linux@...r.kernel.org,
tahbertschinger@...il.com,
tmgross@...ch.edu,
trintaeoitogc@...il.com,
walmeida@...rosoft.com,
wcampbell1995@...il.com
Subject: Re: [PATCH] rust: macros: add authors
Daniel Sedlak <daniel@...lak.dev> wrote:
> That is true, it could be part of `checkpatch.pl`, however I would argue
> that if we can overcame the formatting problems by repeating the field,
> instead of modifying `checkpatch.pl`, then none code is better than some
> code (regarding modifying `checkpatch.pl`).
I understand, but if we choose have a multiples author, firmware and alias
fields, we need modify some codes in `module.rs`, and I think that in the end
is the same work, because if we choose have a multiples fields we need change
modify the module.rs and if we choose have a array we need modify the
checkpatch.pl...
It seems for me is the same work.
Unless you convince me otherswise, I think that is the best thing is to
maintain this as a array, and avoid boring scrolling screen.
On the other hand, I understand that the module that have a author, alias or
firmware a lot is the minority, and the marjority modules we don't need
scrolling screen a lot.
Thanks and regards,
guilherme
Powered by blists - more mailing lists