mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gur Stavi <gur.stavi@huawei.com>
To: <przemyslaw.kitszel@intel.com>
Cc: <andrew+netdev@lunn.ch>, <cai.huoqing@linux.dev>,
	<corbet@lwn.net>, <davem@davemloft.net>, <edumazet@google.com>,
	<gongfan1@huawei.com>, <guoxin09@huawei.com>,
	<gur.stavi@huawei.com>, <helgaas@kernel.org>, <horms@kernel.org>,
	<kuba@kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <luosifu@huawei.com>,
	<meny.yossefi@huawei.com>, <netdev@vger.kernel.org>,
	<pabeni@redhat.com>, <shenchenyang1@hisilicon.com>,
	<shijing34@huawei.com>, <sumang@marvell.com>,
	<wulike1@huawei.com>, <zhoushuai28@huawei.com>
Subject: Re: [PATCH net-next v04 1/1] hinic3: module initialization and tx/rx logic
Date: Thu, 23 Jan 2025 10:20:16 +0200	[thread overview]
Message-ID: <20250123082016.3985519-1-gur.stavi@huawei.com> (raw)
In-Reply-To: <566b3d82-5e66-4e97-9808-a0e8e212fe67@intel.com>

>>>> Auxiliary driver registration.
>>>> Net device_ops registration but open/stop are empty stubs.
>>>> tx/rx logic.
>>>
>>> Take care for spelling: Tx/Rx; HW (just below).
>>
>> Please elaborate. Spelling of what?
>
>In all code comments and commit messages the acronyms and abbreviations
>have their proper spelling, like "Tx", "Rx", "HW', "SW", "ID".
>
>of course lowercase names are still allowed for variables/fields
>

Grepped drivers/net/ethernet (whole word only):

hw 34681   HW 3708   Hw  170
sw  1198   SW  675   Sw    3
rx  5913   RX 4042   Rx 4042
tx  5424   TX 4095   Tx 4907
id  5545   ID 1967   Id   56

I don't know a quick way to separate variables from comments but I
believe that there are very few hw and sw variables and most tx, rx
related variables will have some prefix or suffix so lots of the
whole-word-only come from comments.
Can we agree that while Hw, Sw and Id are improper, the remaining
forms are acceptable?

>>
>>>
>>>>
>>>> All major data structures of the driver are fully introduced with the
>>>> code that uses them but without their initialization code that requires
>>>> management interface with the hw.

  reply	other threads:[~2025-01-23  8:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16  7:51 [PATCH net-next v04 0/1] net: hinic3: Add a driver for Huawei 3rd gen NIC Gur Stavi
2025-01-16  7:51 ` [PATCH net-next v04 1/1] hinic3: module initialization and tx/rx logic Gur Stavi
2025-01-16  9:36   ` Przemek Kitszel
2025-01-22  7:07     ` Gur Stavi
2025-01-22 13:58       ` Przemek Kitszel
2025-01-23  8:20         ` Gur Stavi [this message]
2025-01-23  9:32           ` Przemek Kitszel
2025-01-16 18:10   ` Simon Horman
2025-01-21  9:47     ` Gur Stavi

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=20250123082016.3985519-1-gur.stavi@huawei.com \
    --to=gur.stavi@huawei.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=cai.huoqing@linux.dev \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gongfan1@huawei.com \
    --cc=guoxin09@huawei.com \
    --cc=helgaas@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luosifu@huawei.com \
    --cc=meny.yossefi@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=shenchenyang1@hisilicon.com \
    --cc=shijing34@huawei.com \
    --cc=sumang@marvell.com \
    --cc=wulike1@huawei.com \
    --cc=zhoushuai28@huawei.com \
    /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®