Linux SOC development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Zhao Qunqin <zhaoqunqin@loongson.cn>
Cc: arnd@arndb.de, olof@lixom.net, soc@kernel.org,
	soc@lists.linux.dev, linux-kernel@vger.kernel.org,
	loongarch@lists.linux.dev, xry111@xry111.site,
	christophe.jaillet@wanadoo.fr
Subject: Re: [PATCH V2 RESEND] soc: loongson: add Loongson Security Module driver
Date: Fri, 3 Jan 2025 09:47:10 +0100	[thread overview]
Message-ID: <1c6de9fe-949e-4e0a-bcb6-7640bad575dc@kernel.org> (raw)
In-Reply-To: <ad947db9-119b-4931-ab13-31ea25a66db9@kernel.org>

On 03/01/2025 09:46, Krzysztof Kozlowski wrote:
> On 03/01/2025 09:35, Zhao Qunqin wrote:
>>
>> 在 2025/1/3 下午3:26, Krzysztof Kozlowski 写道:
>>> On 03/01/2025 03:25, Zhao Qunqin wrote:
>>>> 在 2024/12/28 下午7:02, Krzysztof Kozlowski 写道:
>>>>>> Only ACPI firmware is supported.
>>>>>>
>>>>>> Signed-off-by: Qunqin Zhao <zhaoqunqin@loongson.cn>
>>>>> I don't get why you are sending this to soc. This is loongson specific
>>>>> and is supposed to go via Loongson maintainers.
>>>>>
>>>>> And why is this a resend?
>>>> There are no platform-specific maintainers, So I initially sent the
>>>> patch to Arnd,
>>> What do you mean by "no platform-specific maintainers"? This
>>> architecture and this platform is abandoned?
>>
>> Sorry for my poor english. This architecture and this  platform is not 
>> ababdoned.
>>
>> What I mean is that there are no Loongson staff to maintain 
>> drivers/soc/loongson.
> 
> But there are maintainers of the platform, are they? Someone cares about
> Loongson or not?
> 
> If someone cares, then Cc this person and this person is responsible for
> handling your patches. This is called "maintainer".
> 
> If no one cares, then platform is abandoned and we should consider
> calling it orphaned in Linux.
> 
>>
>> The current maintainer  for drivers/soc/loongson is Arnd.
> 
> I don't think so. First, it is unusual. Second, maintainers disagree

^^^ By "maintainers" I meant here the "MAINTAINERS" file, so
scripts/get_maintainers.pl.

> with you on above statement.
> 
> You keep disagreeing here with me and I am afraid we will end up in
> endless discussion, so to reiterate because maybe I wrote my emails too
> soft or too conditional, instead of stating the desired outcome:
> Please send your Loongson SoC drivers to Loongson maintainers and they
> are supposed to take it. If they do not take it, I will send patch for
> making the platform orphaned.


Best regards,
Krzysztof

      reply	other threads:[~2025-01-03  8:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-24  7:25 [PATCH V2 RESEND] soc: loongson: add Loongson Security Module driver Qunqin Zhao
2024-12-28 11:02 ` Krzysztof Kozlowski
2025-01-03  2:25   ` Zhao Qunqin
2025-01-03  7:26     ` Krzysztof Kozlowski
2025-01-03  8:35       ` Zhao Qunqin
2025-01-03  8:46         ` Krzysztof Kozlowski
2025-01-03  8:47           ` Krzysztof Kozlowski [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=1c6de9fe-949e-4e0a-bcb6-7640bad575dc@kernel.org \
    --to=krzk@kernel.org \
    --cc=arnd@arndb.de \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=olof@lixom.net \
    --cc=soc@kernel.org \
    --cc=soc@lists.linux.dev \
    --cc=xry111@xry111.site \
    --cc=zhaoqunqin@loongson.cn \
    /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