linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yanteng Si <si.yanteng@linux.dev>
To: corbet@lwn.net, Frank Sae <Frank.Sae@motor-comm.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	netdev@vger.kernel.org
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	Parthiban.Veerasooran@microchip.com,
	linux-kernel@vger.kernel.org,
	"andrew+netdev @ lunn . ch" <andrew+netdev@lunn.ch>,
	lee@trager.us, horms@kernel.org, linux-doc@vger.kernel.org,
	geert+renesas@glider.be, xiaogang.fan@motor-comm.com,
	fei.zhang@motor-comm.com, hua.sun@motor-comm.com
Subject: Re: [PATCH net-next v4 14/14] yt6801: update ethernet documentation and maintainer
Date: Tue, 15 Apr 2025 11:13:43 +0800	[thread overview]
Message-ID: <06e7bfb3-88fb-41ba-876c-a31cb46f3557@linux.dev> (raw)
In-Reply-To: <20250408092835.3952-15-Frank.Sae@motor-comm.com>

Hi Frank, Xiaogang, Zhang Fei, and Sun Hua,

在 4/8/25 5:28 PM, Frank Sae 写道:
> Add the yt6801.rst in ethernet/motorcomm folder
> Add the yt6801 entry in the index.rst.
> Add myself as the maintainer for the motorcomm ethernet driver.
Would it be possible to split it into two patches?

patch 1 Add docs
patch 2 Modify MAINTAINERS

> 
> Signed-off-by: Frank Sae <Frank.Sae@motor-comm.com>
> ---
>   .../device_drivers/ethernet/index.rst         |  1 +
>   .../ethernet/motorcomm/yt6801.rst             | 20 +++++++++++++++++++
>   MAINTAINERS                                   |  8 ++++++++
>   3 files changed, 29 insertions(+)
>   create mode 100644 Documentation/networking/device_drivers/ethernet/motorcomm/yt6801.rst
> 
> diff --git a/Documentation/networking/device_drivers/ethernet/index.rst b/Documentation/networking/device_drivers/ethernet/index.rst
> index 05d822b90..7a158af55 100644
> --- a/Documentation/networking/device_drivers/ethernet/index.rst
> +++ b/Documentation/networking/device_drivers/ethernet/index.rst
> @@ -46,6 +46,7 @@ Contents:
>      mellanox/mlx5/index
>      meta/fbnic
>      microsoft/netvsc
> +   motorcomm/yt6801
>      neterion/s2io
>      netronome/nfp
>      pensando/ionic
> diff --git a/Documentation/networking/device_drivers/ethernet/motorcomm/yt6801.rst b/Documentation/networking/device_drivers/ethernet/motorcomm/yt6801.rst
> new file mode 100644
> index 000000000..dd1e59c33
> --- /dev/null
> +++ b/Documentation/networking/device_drivers/ethernet/motorcomm/yt6801.rst
> @@ -0,0 +1,20 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +================================================================

> +Linux Base Driver for Motorcomm(R) Gigabit PCI Express Adapters
The title is great!

> +================================================================
> +

> +Motorcomm Gigabit Linux driver.
> +Copyright (c) 2021 - 2024 Motor-comm Co., Ltd.
I'm not sure if it's appropriate to write it this way. I don't object to 
them, but I think it's a bit strange to put them below the title.

Actually, this is a suitable place to write an introduction.

> +
> +

> +Contents
> +========
> +
> +- Support
Could this be all of the content? It appears to deviate slightly from 
the title.

> +
> +

> +Support
> +=======
> +If you got any problem, contact Motorcomm support team via support@motor-comm.com
> +and Cc: netdev.
I think this part of the content can be written in the code comments.

> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4c5c2e2c1..1d7700e6b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -16351,6 +16351,14 @@ F:	drivers/most/
>   F:	drivers/staging/most/
>   F:	include/linux/most.h
>   
> +MOTORCOMM ETHERNET DRIVER
> +M:	Frank <Frank.Sae@motor-comm.com>
> +L:	netdev@vger.kernel.org
> +S:	Maintained
> +W:	https://www.motor-comm.com/

> +F:	Documentation/networking/device_drivers/ethernet/motorcomm/*
I'm quite interested in the long-term planning of this directory. 
Because compared with the documents in other parallel directories 
(wangxun is not a good example), there is still a great deal of content 
that needs to be written. Of course, I'm not sure if there are any 
engineers in your team whose mother tongue is Chinese. If it's 
convenient, it would be even better if a Chinese document could be 
prepared as well.


Thanks,
Yanteng


  reply	other threads:[~2025-04-15  3:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  9:28 [PATCH net-next v4 00/14] yt6801: Add Motorcomm yt6801 PCIe driver Frank Sae
2025-04-08  9:28 ` [PATCH net-next v4 01/14] yt6801: Add support for a pci table in this module Frank Sae
2025-04-14  9:19   ` Philipp Stanner
2025-04-08  9:28 ` [PATCH net-next v4 02/14] yt6801: Implement mdio register Frank Sae
2025-04-08  9:28 ` [PATCH net-next v4 03/14] yt6801: Implement pci_driver shutdown Frank Sae
2025-04-08  9:28 ` [PATCH net-next v4 07/14] net:phy:motorcomm: Add PHY_INTERFACE_MODE_INTERNAL to support YT6801 Frank Sae
2025-04-08 13:11   ` Andrew Lunn
2025-04-08  9:28 ` [PATCH net-next v4 08/14] yt6801: Implement the fxgmac_hw_init function Frank Sae
2025-04-08  9:28 ` [PATCH net-next v4 12/14] yt6801: Implement pci_driver suspend and resume Frank Sae
2025-04-08  9:28 ` [PATCH net-next v4 14/14] yt6801: update ethernet documentation and maintainer Frank Sae
2025-04-15  3:13   ` Yanteng Si [this message]
2025-04-08 10:14 ` [PATCH net-next v4 04/14] yt6801: Implement the fxgmac_init function Frank Sae
2025-04-08 10:14 ` [PATCH net-next v4 05/14] yt6801: Implement the .ndo_open function Frank Sae
2025-04-08 10:14 ` [PATCH net-next v4 06/14] yt6801: Implement the fxgmac_start function Frank Sae
2025-04-08 10:14 ` [PATCH net-next v4 09/14] yt6801: Implement the poll functions Frank Sae
2025-04-08 10:14 ` [PATCH net-next v4 10/14] yt6801: Implement .ndo_start_xmit function Frank Sae
2025-04-08 10:15 ` [PATCH net-next v4 11/14] yt6801: Implement some net_device_ops function Frank Sae
2025-04-08 10:30 ` [PATCH net-next v4 00/14] yt6801: Add Motorcomm yt6801 PCIe driver Russell King (Oracle)
2025-04-11  9:50   ` Frank Sae
2025-04-11 12:10     ` Russell King (Oracle)
2025-04-13 20:33     ` Andrew Lunn
2025-04-17  6:06       ` Frank Sae
2025-04-17 10:10         ` Russell King (Oracle)
2025-09-09 13:49         ` Shengyu Qu

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=06e7bfb3-88fb-41ba-876c-a31cb46f3557@linux.dev \
    --to=si.yanteng@linux.dev \
    --cc=Frank.Sae@motor-comm.com \
    --cc=Parthiban.Veerasooran@microchip.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fei.zhang@motor-comm.com \
    --cc=geert+renesas@glider.be \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --cc=hua.sun@motor-comm.com \
    --cc=kuba@kernel.org \
    --cc=lee@trager.us \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=masahiroy@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=xiaogang.fan@motor-comm.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;
as well as URLs for NNTP newsgroup(s).