From: Krzysztof Kozlowski <krzk@kernel.org>
To: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
Dragan Simic <dsimic@manjaro.org>
Cc: FUKAUMI Naoki <naoki@radxa.com>,
Joseph Kogut <joseph.kogut@gmail.com>,
heiko@sntech.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, jonas@kwiboo.se, kever.yang@rock-chips.com,
honyuenkwun@gmail.com, quentin.schulz@cherry.de,
pbrobinson@gmail.com, amadeus@jmu.edu.cn, jbx6244@gmail.com,
devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v6 0/3] Add Radxa CM5 and IO Board
Date: Fri, 14 Nov 2025 11:34:27 +0100 [thread overview]
Message-ID: <99309e42-dfdc-4632-8681-c9763b9e8ad4@kernel.org> (raw)
In-Reply-To: <f156cd48-d764-43c8-99ed-24ab212d8eee@collabora.com>
On 14/11/2025 09:51, Cristian Ciocaltea wrote:
> On 11/14/25 9:17 AM, Dragan Simic wrote:
>> Hello Krzysztof,
>>
>> On Friday, November 14, 2025 08:10 CET, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>> On 14/11/2025 06:03, FUKAUMI Naoki wrote:
>>>> On 11/12/25 09:46, Dragan Simic wrote:
>>>>> On Wednesday, November 12, 2025 00:26 CET, FUKAUMI Naoki <naoki@radxa.com> wrote:
>>>>>> On 11/11/25 23:33, Dragan Simic wrote:
>>>>>>> On Tuesday, November 11, 2025 12:52 CET, FUKAUMI Naoki <naoki@radxa.com> wrote:
>>>>>>>> On 11/6/25 02:48, Joseph Kogut wrote:
>>>>>>>>> On Wed, Nov 5, 2025 at 4:15 AM FUKAUMI Naoki <naoki@radxa.com> wrote:
>>>>>>>>>> I'd like to clarify the situation regarding the v6 patch series I submitted.
>>>>>>>>>>
>>>>>>>>>> The original device tree work for the Radxa CM5 and IO Board was
>>>>>>>>>> authored by Joseph Kogut. I took over the responsibility of getting it
>>>>>>>>>> upstreamed with his agreement.
>>>>>>>>>
>>>>>>>>> I'll confirm this. I've been in communication with Naoki. They made a
>>>>>>>>> large number of revisions to my original patch series, which I think
>>>>>>>>> have technical merit. I suggested they submit the patches themselves,
>>>>>>>>> and gave them explicit permission to add my Signed-off-by and CC me.
>>>>>>>>>
>>>>>>>>> I assume this was the correct way for them to continue the work I
>>>>>>>>> started, but if not, please let us know the best way to proceed.
>>>>>>>>
>>>>>>>> Can anyone help us?
>>>>>>>
>>>>>>> I'm not exactly sure how to resolve the current situation, but for
>>>>>>> Signed-off-by tags to be present, in this case you'd need to have
>>>>>>> Co-developed-by tags as well, because the final patch versions,
>>>>>>> which would be submitted by Naoki, would differ significantly from
>>>>>>> the versions that Joseph actively worked on, if I understood
>>>>>>> everything correctly. Though, for Joseph's Signed-off-by tags to
>>>>>>> be included there, he would also need to participate actively in
>>>>>>> the development of the final patch versions.
>>>>>>
>>>>>> https://www.kernel.org/doc/html/latest/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by
>>>>>>
>>>>>> If
>>>>>> ----
>>>>>> From: Joseph Kogut <joseph.kogut@gmail.com>
>>>>>>
>>>>>> <changelog>
>>>>>>
>>>>>> Signed-off-by: Joseph Kogut <joseph.kogut@gmail.com>
>>>>>> Co-developed-by: FUKAUMI Naoki <naoki@radxa.com>
>>>>>> Signed-off-by: FUKAUMI Naoki <naoki@radxa.com>
>>>>>> ----
>>>>>> then I can submit my patch series?
>>>>>
>>>>> Actually, the Co-developed-by tags would be pointing to Joseph
>>>>> in that case, but as I described it above, this approach basically
>>>>> cannot be used, because Joseph's original work differs a lot from
>>>>> what you'd actually submit to the mailing list(s).
>>>>>
>>>>>> Or,
>>>>>>
>>>>>>> Another option, technically a bit simpler, would be to include just
>>>>>>> Originally-by tags for Joseph, which would indicate that Joseph gave
>>>>>>> up on the development of the patches and handed them over to Naoki
>>>>>>> for future development and submission to the mailing lists. Though,
>>>>>>> that would require Joseph to publicly state exactly that.
>>>>>>
>>>>>> I cannot find any documentation about "Originally-by".
>>>>>> Is this correct?
>>>>>> ----
>>>>>> <changelog>
>>>>>>
>>>>>> Originally-by: Joseph Kogut <joseph.kogut@gmail.com>
>>>
>>> There is no such tag. Don't invent tags.
>>
>> True, it doesn't exist officially, but it's been used fairly often.
>
> Hmm, actually this tag seems to be documented, or at least given as an example:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/maintainer-tip.rst?h=v6.18-rc5#n309
Yes, for the tip folks (so three people). If you send to the TIP, their
maintainer profile applies. There are also other specific rules in TIP
which are in contrary to common (as most used) process, e.g. completely
reversed tags (see also Konstantin's explanation about the order which
he implemented in b4).
If you want to use it outside of tip, first this should be added to
common docs and checkpatch. Just like b4 should be changed if you want
to use their order of tags.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-14 10:34 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 5:13 [PATCH v6 0/3] Add Radxa CM5 and IO Board FUKAUMI Naoki
2025-11-05 5:13 ` [PATCH v6 1/3] dt-bindings: arm: rockchip: Add Radxa CM5 " FUKAUMI Naoki
2025-11-05 6:43 ` Krzysztof Kozlowski
2025-11-05 6:57 ` FUKAUMI Naoki
2025-11-05 7:08 ` Krzysztof Kozlowski
2025-11-14 7:12 ` Krzysztof Kozlowski
2025-11-14 7:37 ` FUKAUMI Naoki
2025-11-14 7:42 ` Krzysztof Kozlowski
2025-11-14 7:47 ` FUKAUMI Naoki
2025-11-14 7:51 ` Krzysztof Kozlowski
2025-11-14 8:24 ` FUKAUMI Naoki
2025-11-14 8:32 ` Dragan Simic
2025-11-14 10:08 ` Heiko Stübner
2025-11-14 10:12 ` Dragan Simic
2025-11-14 10:30 ` Krzysztof Kozlowski
2025-11-14 10:35 ` Krzysztof Kozlowski
2025-11-14 13:57 ` Dragan Simic
2025-11-14 8:33 ` Krzysztof Kozlowski
2025-11-05 5:13 ` [PATCH v6 2/3] arm64: dts: rockchip: Add Radxa CM5 FUKAUMI Naoki
2025-11-05 6:45 ` Krzysztof Kozlowski
2025-11-05 5:13 ` [PATCH v6 3/3] arm64: dts: rockchip: Add Radxa CM5 IO Board FUKAUMI Naoki
2025-11-05 6:46 ` Krzysztof Kozlowski
2025-11-05 18:27 ` Jimmy Hon
2025-11-05 23:38 ` FUKAUMI Naoki
2025-11-06 3:17 ` FUKAUMI Naoki
2025-11-06 3:38 ` Dragan Simic
2025-11-06 3:31 ` Dragan Simic
2025-11-06 4:29 ` FUKAUMI Naoki
2025-11-06 4:53 ` Jimmy Hon
2025-11-06 5:08 ` FUKAUMI Naoki
2025-11-06 5:50 ` Jimmy Hon
2025-11-10 3:18 ` Dragan Simic
2025-11-06 8:40 ` Shawn Lin
2025-11-05 12:15 ` [PATCH v6 0/3] Add Radxa CM5 and " FUKAUMI Naoki
2025-11-05 17:48 ` Joseph Kogut
2025-11-11 11:52 ` FUKAUMI Naoki
2025-11-11 14:33 ` Dragan Simic
2025-11-11 23:26 ` FUKAUMI Naoki
2025-11-12 0:46 ` Dragan Simic
2025-11-12 1:01 ` FUKAUMI Naoki
2025-11-12 1:14 ` Dragan Simic
2025-11-14 5:03 ` FUKAUMI Naoki
2025-11-14 7:10 ` Krzysztof Kozlowski
2025-11-14 7:17 ` Dragan Simic
2025-11-14 7:22 ` Krzysztof Kozlowski
2025-11-14 7:26 ` Dragan Simic
2025-11-14 7:28 ` Krzysztof Kozlowski
2025-11-14 8:10 ` Dragan Simic
2025-11-14 8:51 ` Cristian Ciocaltea
2025-11-14 10:34 ` Krzysztof Kozlowski [this message]
2025-11-14 8:06 ` FUKAUMI Naoki
2025-11-14 8:46 ` FUKAUMI Naoki
2025-11-05 18:10 ` Jimmy Hon
2025-11-05 23:27 ` FUKAUMI Naoki
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=99309e42-dfdc-4632-8681-c9763b9e8ad4@kernel.org \
--to=krzk@kernel.org \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=honyuenkwun@gmail.com \
--cc=jbx6244@gmail.com \
--cc=jonas@kwiboo.se \
--cc=joseph.kogut@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=naoki@radxa.com \
--cc=pbrobinson@gmail.com \
--cc=quentin.schulz@cherry.de \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).