From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: rust-for-linux@vger.kernel.org, Trevor Gross <tmgross@umich.edu>,
Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [PATCH v2 2/2] docs: rust: Add description of Rust documentation test as KUnit ones
Date: Mon, 29 Jan 2024 18:47:37 +0100 [thread overview]
Message-ID: <CANiq72kjF5-+NrpE03Psv_P1hkxwGww9YCFZRDenmMqGFZ+5Pw@mail.gmail.com> (raw)
In-Reply-To: <20240123075325.1270967-2-dirk.behme@de.bosch.com>
Hi Dirk,
A couple answers to your questions from v2 (I answer here instead of
v3 for context).
On Tue, Jan 23, 2024 at 8:53 AM Dirk Behme <dirk.behme@de.bosch.com> wrote:
>
> * Sorry for the typo Miguel! :)
No problem at all! :)
> * Miguel: As you wrote most of the text, can I add you Signed-off-by instead
> of the Co-developed-by?
No worries -- but note that it is not "Signed-off-by" vs.
"Co-developed-by", i.e. please see this section:
https://docs.kernel.org/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by
For instance, if you want to be the main author, it should be:
Co-developed-by: Miguel Ojeda <ojeda@kernel.org>
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
I can fix it on my side if there is no v4, no worries.
Cheers,
Miguel
next prev parent reply other threads:[~2024-01-29 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 7:53 [PATCH v2 1/2] docs: rust: Move testing to a separate page Dirk Behme
2024-01-23 7:53 ` [PATCH v2 2/2] docs: rust: Add description of Rust documentation test as KUnit ones Dirk Behme
2024-01-29 17:47 ` Miguel Ojeda [this message]
2024-01-23 8:47 ` [PATCH v2 1/2] docs: rust: Move testing to a separate page Trevor Gross
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=CANiq72kjF5-+NrpE03Psv_P1hkxwGww9YCFZRDenmMqGFZ+5Pw@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=dirk.behme@de.bosch.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).