DPDK patches and discussions
 help / color / mirror / Atom feed
From: "11" <caowenbo@mucse.com>
To: "'Stephen Hemminger'" <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: RE: [[PATCH v1] 0/8] *** SUBJECT HERE ***
Date: Wed, 2 Aug 2023 10:35:40 +0800	[thread overview]
Message-ID: <58940EA8D4720377+005301d9c4ea$07dee5e0$179cb1a0$@mucse.com> (raw)
In-Reply-To: <20230801190519.597c89d0@hermes.local>

Your git commit headings are messed up with extra [].
Yes, this is my problem :) 
David has been mentioned before , I'm re edit the cover-letter now.
Thanks a lot.

Regards wenbo
-----Original Message-----
From: Stephen Hemminger <stephen@networkplumber.org> 
Sent: 2023年8月2日 10:31
To: Wenbo Cao <caowenbo@mucse.com>
Cc: dev@dpdk.org
Subject: Re: [[PATCH v1] 0/8] *** SUBJECT HERE ***

On Tue,  1 Aug 2023 07:21:29 +0000
Wenbo Cao <caowenbo@mucse.com> wrote:

> *** BLURB HERE ***
> 
> Wenbo Cao (8):
>   net/rnp: add skeleton
>   net/rnp: add ethdev probe and remove
>   net/rnp: add device init and uninit
>   net/rnp: add mbx basic api feature
>   net/rnp add reset code for Chip Init process
>   net/rnp add port info resource init
>   net/rnp add devargs runtime parsing functions
>   net/rnp handle device interrupts
> 
>  MAINTAINERS                         |   6 +
>  doc/guides/nics/features/rnp.ini    |   8 +
>  doc/guides/nics/index.rst           |   1 +
>  doc/guides/nics/rnp.rst             |  43 ++
>  drivers/net/meson.build             |   1 +
>  drivers/net/rnp/base/rnp_api.c      |  71 +++
>  drivers/net/rnp/base/rnp_api.h      |  17 +
>  drivers/net/rnp/base/rnp_cfg.h      |   7 +
>  drivers/net/rnp/base/rnp_dma_regs.h |  73 +++  
> drivers/net/rnp/base/rnp_eth_regs.h | 124 +++++
>  drivers/net/rnp/base/rnp_hw.h       | 193 +++++++
>  drivers/net/rnp/base/rnp_mac_regs.h | 279 ++++++++++
>  drivers/net/rnp/meson.build         |  18 +
>  drivers/net/rnp/rnp.h               | 217 ++++++++
>  drivers/net/rnp/rnp_ethdev.c        | 823 ++++++++++++++++++++++++++++
>  drivers/net/rnp/rnp_logs.h          |  43 ++
>  drivers/net/rnp/rnp_mbx.c           | 522 ++++++++++++++++++
>  drivers/net/rnp/rnp_mbx.h           | 139 +++++
>  drivers/net/rnp/rnp_mbx_fw.c        | 781 ++++++++++++++++++++++++++
>  drivers/net/rnp/rnp_mbx_fw.h        | 401 ++++++++++++++
>  drivers/net/rnp/rnp_osdep.h         |  30 +
>  drivers/net/rnp/rnp_rxtx.c          |  83 +++
>  drivers/net/rnp/rnp_rxtx.h          |  14 +
>  23 files changed, 3894 insertions(+)
>  create mode 100644 doc/guides/nics/features/rnp.ini  create mode 
> 100644 doc/guides/nics/rnp.rst  create mode 100644 
> drivers/net/rnp/base/rnp_api.c  create mode 100644 
> drivers/net/rnp/base/rnp_api.h  create mode 100644 
> drivers/net/rnp/base/rnp_cfg.h  create mode 100644 
> drivers/net/rnp/base/rnp_dma_regs.h
>  create mode 100644 drivers/net/rnp/base/rnp_eth_regs.h
>  create mode 100644 drivers/net/rnp/base/rnp_hw.h  create mode 100644 
> drivers/net/rnp/base/rnp_mac_regs.h
>  create mode 100644 drivers/net/rnp/meson.build  create mode 100644 
> drivers/net/rnp/rnp.h  create mode 100644 drivers/net/rnp/rnp_ethdev.c  
> create mode 100644 drivers/net/rnp/rnp_logs.h  create mode 100644 
> drivers/net/rnp/rnp_mbx.c  create mode 100644 
> drivers/net/rnp/rnp_mbx.h  create mode 100644 
> drivers/net/rnp/rnp_mbx_fw.c  create mode 100644 
> drivers/net/rnp/rnp_mbx_fw.h  create mode 100644 
> drivers/net/rnp/rnp_osdep.h  create mode 100644 
> drivers/net/rnp/rnp_rxtx.c  create mode 100644 
> drivers/net/rnp/rnp_rxtx.h

Your git commit headings are messed up with extra [].




  reply	other threads:[~2023-08-02  2:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01  7:21 Wenbo Cao
2023-08-01  7:55 ` David Marchand
2023-08-02  2:30 ` Stephen Hemminger
2023-08-02  2:35   ` 11 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-01  6:43 Wenbo Cao

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='58940EA8D4720377+005301d9c4ea$07dee5e0$179cb1a0$@mucse.com' \
    --to=caowenbo@mucse.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).