mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhao Qunqin <zhaoqunqin@loongson.cn>
To: Krzysztof Kozlowski <krzk@kernel.org>
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 10:25:38 +0800	[thread overview]
Message-ID: <22cb222a-a34d-b2ff-88cf-2e9433aed310@loongson.cn> (raw)
In-Reply-To: <f9138082-1d17-4247-b365-7cb4eef88879@kernel.org>


在 2024/12/28 下午7:02, Krzysztof Kozlowski 写道:
> On 24/12/2024 08:25, Qunqin Zhao wrote:
>> This driver supports Loongson Security Module, which
>> provides the control for it's hardware encryption
>> acceleration child devices.
> Please wrap commit message according to Linux coding style / submission
> process (neither too early nor over the limit):
> https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
OK
>> 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,

but didn't receive a response from Arnold, so I resent the patch and added

soc@kernel.org to the mailing list.

>> ---
>> Changes in v2:
>> 	- Removed useless memset() in probe.
>> 	- Cleaned up coding style.
>> 	- Corrected the spelling.
>>
>>   MAINTAINERS                        |   7 +
>>   drivers/soc/loongson/Kconfig       |   9 +
>>   drivers/soc/loongson/Makefile      |   1 +
>>   drivers/soc/loongson/loongson_se.c | 523 +++++++++++++++++++++++++++++
>>   include/soc/loongson/se.h          | 135 ++++++++
>
> include/linux/soc/... or just keep it private to the driver. Why this
> has to be exposed to other users?

Looks like  include/linux/soc... is more suitable than include/soc/...

This driver is the base of other users,  one user will be added in next 
revision.

And may I ask which one do you think is more suitable to place this 
basic driver under SOC or MFD ?


Thanks.

> Best regards,
> Krzysztof


  reply	other threads:[~2025-01-03  2:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-24  7:25 Qunqin Zhao
2024-12-28 11:02 ` Krzysztof Kozlowski
2025-01-03  2:25   ` Zhao Qunqin [this message]
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

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=22cb222a-a34d-b2ff-88cf-2e9433aed310@loongson.cn \
    --to=zhaoqunqin@loongson.cn \
    --cc=arnd@arndb.de \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=krzk@kernel.org \
    --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 \
    /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

all inboxes | Powered by JetHome®