From: Damien Le Moal <dlemoal@kernel.org>
To: Runa Guo-oc <RunaGuo-oc@zhaoxin.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Cc: CobeChen@zhaoxin.com, TimGuo@zhaoxin.com, TonyWWang@zhaoxin.com,
LeoLiu@zhaoxin.com, RunaGuo@zhaoxin.com
Subject: Re: [PATCH] Signed-off-by: Runa Guo-oc <RunaGuo-oc@zhaoxin.com>
Date: Tue, 27 Jun 2023 17:02:15 +0900 [thread overview]
Message-ID: <73aa50fd-2028-c492-59cd-b740a827e90c@kernel.org> (raw)
In-Reply-To: <b330e18d-4fd3-2649-aafd-4f941c111803@zhaoxin.com>
On 6/27/23 16:17, Runa Guo-oc wrote:
> On 2023/6/26 20:40, Damien Le Moal wrote:
>> On 6/26/23 20:29, Runa Guo-oc wrote:
>>> On 2023/6/16 16:34, Damien Le Moal wrote:
>>>> On 6/16/23 16:49, Runa Guo-oc wrote:
>>>>> [PATCH] ata:sata_zhaoxin: Add support for ZhaoXin Serial ATA
>>>>
>>>> Broken patch: the email subject is your SoB instead of the above line, which
>>>> should not be part of the message (it should be the subject). Please reformat
>>>> and resend.
>>>>
>>>
>>> Okay.
>>>
>>>>>
>>>>> Add ZhaoXin Serial ATA support for ZhaoXin CUPs.
>>>>
>>>> What is "ZhaoXin" ?
>>>
>>> Zhaoxin is a Chinese company that has mastered the core technology
>>> of independent general-purpose processors and its system platform chips,
>>> and is committed to providing users with efficient, compatible and secure
>>> independent general-purpose processors, chipsets and other products.
>>> for more information, you can visit here: https://www.zhaoxin.com/.
>>
>> A company marketing message is not very informative, technically speaking. What
>> is this chipset and on what board/machine can it be found ? That is the more
>> relevant information we need in this commit message.
>>
>
> The reason why it is called Zhaoxin SATA is actually to express that it
> applies
> to all Zhaoxin support of its separate chipset/SOC, for example,
> ZX-100S/ZX-200
> chipsets.
That is fine. I do not need a reason for the name. what I would like to see is
information about which product/board/soc this driver will be needed for. So
something like the above is actually fine (may be a little more details if you
have).
>
>>>
>>>> And what is "CUPs" ? Please spell this out.
>>>>
>>>
>>> Yes, this is a spelling error.
>>>
>>>>>
>>>>> Signed-off-by: Runa Guo-oc <RunaGuo-oc@zhaoxin.com>
>>>>> ---
>>>>> drivers/ata/Kconfig | 8 +
>>>>> drivers/ata/Makefile | 1 +
>>>>> drivers/ata/sata_zhaoxin.c | 384 +++++++++++++++++++++++++++++++++++++++++++++
>>>>> 3 files changed, 393 insertions(+)
>>>>> create mode 100644 drivers/ata/sata_zhaoxin.c
>>>>>
>>>>> diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig
>>>>> index 42b51c9..ae327f3 100644
>>>>> --- a/drivers/ata/Kconfig
>>>>> +++ b/drivers/ata/Kconfig
>>>>> @@ -553,6 +553,14 @@ config SATA_VITESSE
>>>>>
>>>>> If unsure, say N.
>>>>>
>>>>> +config SATA_ZHAOXIN
>>>>> + tristate "ZhaoXin SATA support"
>>
>> Same here. If ZhaoXin is only a company name, we need also a chipset model to be
>> informative regarding which HW this driver serves.
>>
>
> As mentioned before, the chipset models this driver serves are ZX-100S
> and ZX-200
> currently.
Fine. Just say so in the Kconfig entry then.
If in the future your company produces a different chipset model that needs a
different driver, then the entries can be clearly differentiated even if they
use the same company name (ZhaoXin). E.g. "ZhaoXin ZX-100S and ZX-200 chipset
support" vs "ZhaoXin XYZ-newgen chipset support". Adding entries should not
require modifying existing entries.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2023-06-27 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 7:49 [PATCH] Signed-off-by: Runa Guo-oc <RunaGuo-oc@zhaoxin.com> Runa Guo-oc
2023-06-16 8:34 ` Damien Le Moal
2023-06-26 11:29 ` Runa Guo-oc
2023-06-26 12:40 ` Damien Le Moal
2023-06-27 7:17 ` Runa Guo-oc
2023-06-27 8:02 ` Damien Le Moal [this message]
2023-06-27 8:51 ` Runa Guo-oc
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=73aa50fd-2028-c492-59cd-b740a827e90c@kernel.org \
--to=dlemoal@kernel.org \
--cc=CobeChen@zhaoxin.com \
--cc=LeoLiu@zhaoxin.com \
--cc=RunaGuo-oc@zhaoxin.com \
--cc=RunaGuo@zhaoxin.com \
--cc=TimGuo@zhaoxin.com \
--cc=TonyWWang@zhaoxin.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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