From: Guilherme Giacomo Simoes <trintaeoitogc@gmail.com>
To: gary@garyguo.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,
gregkh@linuxfoundation.org, joe@perches.com,
linux-kernel@vger.kernel.org, lukas.bulwahn@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 2/3] rust: macros: change author field to array
Date: Thu, 13 Feb 2025 14:46:02 -0300 [thread overview]
Message-ID: <20250213174602.200524-1-trintaeoitogc@gmail.com> (raw)
In-Reply-To: <20250213113420.5d2b7d97@eugeo>
Gary Guo <gary@garyguo.net> wrotes:
> Spelling out commit SHA doesn't work for patches because it will change
> when applied.
Hmm, I was think that they would stayed the same
> Also, this patch needs to be the same commit as the one changing
> macros, otherwise the tree won't compile when bisecting.
This really make sense, I will send a v2
Thanks,
Guilherme
prev parent reply other threads:[~2025-02-13 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 19:48 [PATCH 2/3] rust: macros: change author field to array Guilherme Giacomo Simoes
2025-02-12 19:48 ` [PATCH 3/3] checkpatch: throw error in malformed arrays Guilherme Giacomo Simoes
2025-02-13 11:17 ` Joe Perches
2025-02-13 18:20 ` Guilherme Giacomo Simoes
2025-02-13 11:34 ` [PATCH 2/3] rust: macros: change author field to array Gary Guo
2025-02-13 17:46 ` Guilherme Giacomo Simoes [this message]
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=20250213174602.200524-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).