From: Krzysztof Kozlowski <krzk@kernel.org>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Sean Christopherson <seanjc@google.com>
Cc: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
workflows@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Jacob Keller <jacob.e.keller@intel.com>,
Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Subject: Re: [PATCH] checkpatch: allow tags between co-developed-by and their sign-off
Date: Sun, 29 Oct 2023 10:35:26 +0100 [thread overview]
Message-ID: <0693460e-2104-49af-b1dc-5ffae0f279c5@kernel.org> (raw)
In-Reply-To: <887636af-6be7-f418-bfa4-d85501f2f40c@intel.com>
On 24/10/2023 11:15, Przemek Kitszel wrote:
> On 10/23/23 16:02, Sean Christopherson wrote:
>> +Mateusz
>>
>> On Mon, Oct 23, 2023, Przemek Kitszel wrote:
>>> Additional tags between Co-developed-by and corresponding Signed-off-by
>>> could include Reviewed-by tags collected by Submitter, which is also
>>> a Co-developer, but should sign-off at the very end of tags provided by
>>> the Submitter.
>>
>> ...
>>
>>> Mateusz Polchlopek <mateusz.polchlopek@intel.com> has reported this to me.
>>
>> Heh, there's a tag for that...
>>
>> Reported-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
>>
>> And it's usually a good idea to Cc the reporter in case there are questions they
>> can help answer.
>
> Heh ;) then I would get a checkpatch warning for not providing Link: to
> the report, somehow I wanted to avoid those for checkpatch contrib :)
You wanted Suggested-by. There is no bug here, so Reported-by is not
suitable.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-10-29 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 10:28 Przemek Kitszel
2023-10-23 14:02 ` Sean Christopherson
2023-10-24 9:15 ` Przemek Kitszel
2023-10-29 9:35 ` Krzysztof Kozlowski [this message]
2023-10-30 9:05 ` Przemek Kitszel
2023-10-23 14:16 ` Lukas Bulwahn
2023-10-23 14:25 ` Joe Perches
2023-10-24 9:15 ` Przemek Kitszel
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=0693460e-2104-49af-b1dc-5ffae0f279c5@kernel.org \
--to=krzk@kernel.org \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=jacob.e.keller@intel.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mateusz.polchlopek@intel.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=seanjc@google.com \
--cc=workflows@vger.kernel.org \
/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