From: Guilherme Giacomo Simoes <trintaeoitogc@gmail.com>
To: charmitro@posteo.net
Cc: 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,
linux-kernel@vger.kernel.org, lukas.bulwahn@gmail.com,
miguel.ojeda.sandonis@gmail.com, ojeda@kernel.org,
pbonzini@redhat.com, rust-for-linux@vger.kernel.org,
tmgross@umich.edu, trintaeoitogc@gmail.com,
walmeida@microsoft.com
Subject: Re: [PATCH V2 1/2] rust: module: change author to be a array
Date: Fri, 14 Feb 2025 22:11:45 -0300 [thread overview]
Message-ID: <20250215011145.146552-1-trintaeoitogc@gmail.com> (raw)
In-Reply-To: <m2y0y8b7p0.fsf@posteo.net>
Charalampos Mitrodimas <charmitro@posteo.net> wrotes:
> I wonder if we should make this "for author in authors", for code
> clarity concerns.
You is write, I will make this change.
> It could be that you developed this with an old tree history. You missed
> changing the author for the samples/rust/rust_driver_platform.rs sample.
Yes, my bad.
I will include this driver
Thanks,
Guilherme
next prev parent reply other threads:[~2025-02-15 1:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 18:45 [PATCH V2 0/2] author field in module! macro should be a array Guilherme Giacomo Simoes
2025-02-14 18:45 ` [PATCH V2 1/2] rust: module: change author to " Guilherme Giacomo Simoes
2025-02-14 20:19 ` Charalampos Mitrodimas
2025-02-15 1:11 ` Guilherme Giacomo Simoes [this message]
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=20250215011145.146552-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=charmitro@posteo.net \
--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=miguel.ojeda.sandonis@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox