[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e29d0306-329b-b5b8-aa50-4e3ab0ded1e2@intel.com>
Date: Mon, 30 Oct 2023 10:05:49 +0100
From: Przemek Kitszel <przemyslaw.kitszel@...el.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
Sean Christopherson <seanjc@...gle.com>
CC: Andy Whitcroft <apw@...onical.com>, Joe Perches <joe@...ches.com>,
Dwaipayan Ray <dwaipayanray1@...il.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
<workflows@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Jonathan Corbet <corbet@....net>, <linux-doc@...r.kernel.org>,
Jacob Keller <jacob.e.keller@...el.com>,
Mateusz Polchlopek <mateusz.polchlopek@...el.com>
Subject: Re: [PATCH] checkpatch: allow tags between co-developed-by and their
sign-off
On 10/29/23 10:35, Krzysztof Kozlowski wrote:
> 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@...el.com> has reported this to me.
>>>
>>> Heh, there's a tag for that...
>>>
>>> Reported-by: Mateusz Polchlopek <mateusz.polchlopek@...el.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
>
I would really like to see Inspired-by: and use it a lot, for cases that
some talk ignites an idea, but it's Suggested-by
Powered by blists - more mailing lists