From: Guilherme Giacomo Simoes <trintaeoitogc@gmail.com>
To: a.hindborg@kernel.org, alex.gaynor@gmail.com,
aliceryhl@google.com, apw@canonical.com, arnd@arndb.de,
aswinunni01@gmail.com, axboe@kernel.dk, benno.lossin@proton.me,
bhelgaas@google.com, bjorn3_gh@protonmail.com,
boqun.feng@gmail.com, dakr@kernel.org, dwaipayanray1@gmail.com,
ethan.twardy@gmail.com, fujita.tomonori@gmail.com,
gary@garyguo.net, gregkh@linuxfoundation.org, joe@perches.com,
lukas.bulwahn@gmail.com, ojeda@kernel.org, pbonzini@redhat.com,
tmgross@umich.edu, walmeida@microsoft.com
Cc: trintaeoitogc@gmail.com, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH V2 0/2] author field in module! macro should be a array
Date: Fri, 14 Feb 2025 15:45:48 -0300 [thread overview]
Message-ID: <20250214184550.120775-1-trintaeoitogc@gmail.com> (raw)
In the module! macro, the author field has a string type. Once that the
modules can has more than one author, this is impossible in the current
scenary.
- Change the author field for accept a array string type and enable
module creations with more than one author.
- In modules that use the author field, change its value to a string
array.
- Change the check patch to find poorly formatted arrays in the macro
module!
---
V2 changes
- Merge the changes in module.rs and in modules that contains a author of
module in a only one commit.
- Remove uneccessary "FOR EXAMPLE" in checkpatch
- Change from ERROR to WARN in message that is throw in checkpatch
- Remove the hungarian style namings in checkptach
- Improve code formatting in checkpatch
Guilherme Giacomo Simoes (2):
rust: module: change author to be a array
checkpatch: throw error in malformed arrays
drivers/block/rnull.rs | 2 +-
rust/kernel/net/phy.rs | 4 +--
rust/kernel/pci.rs | 2 +-
rust/macros/lib.rs | 4 +--
rust/macros/module.rs | 8 +++---
samples/rust/rust_driver_pci.rs | 2 +-
samples/rust/rust_minimal.rs | 2 +-
samples/rust/rust_misc_device.rs | 2 +-
samples/rust/rust_print_main.rs | 2 +-
scripts/checkpatch.pl | 43 ++++++++++++++++++++++++++++++++
10 files changed, 58 insertions(+), 13 deletions(-)
--
2.34.1
next reply other threads:[~2025-02-14 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 18:45 Guilherme Giacomo Simoes [this message]
2025-02-14 18:45 ` [PATCH V2 1/2] rust: module: change author to be a array Guilherme Giacomo Simoes
2025-02-14 20:19 ` Charalampos Mitrodimas
2025-02-15 1:11 ` Guilherme Giacomo Simoes
2025-02-15 1:39 ` Benno Lossin
2025-02-15 13:52 ` Guilherme Giacomo Simoes
2025-02-15 14:34 ` Benno Lossin
2025-02-16 12:35 ` kernel test robot
2025-02-14 18:45 ` [PATCH V2 2/2] checkpatch: throw error in malformed arrays Guilherme Giacomo Simoes
2025-02-15 5:24 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250214184550.120775-1-trintaeoitogc@gmail.com \
--to=trintaeoitogc@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=apw@canonical.com \
--cc=arnd@arndb.de \
--cc=aswinunni01@gmail.com \
--cc=axboe@kernel.dk \
--cc=benno.lossin@proton.me \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=dwaipayanray1@gmail.com \
--cc=ethan.twardy@gmail.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=ojeda@kernel.org \
--cc=pbonzini@redhat.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=walmeida@microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.