DPDK website maintenance
 help / color / mirror / Atom feed
From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: skillwell <skillwell@163.com>, "web@dpdk.org" <web@dpdk.org>
Subject: Re: web content mismatch
Date: Fri, 28 Jun 2024 09:33:22 +0000	[thread overview]
Message-ID: <PH8PR11MB6803AD73ECF2916438F82359D7D02@PH8PR11MB6803.namprd11.prod.outlook.com> (raw)
In-Reply-To: <319a6b38.9156.1905e08cb47.Coremail.skillwell@163.com>

> From:skillwell <skillwell@163.com>
> Sent:Friday, June 28, 2024 9:49 AM
> To:web@dpdk.org <web@dpdk.org>
> Subject:web content mismatch
> 
> Hi

Hi Skillwell, 

>   thank you for reading this email!
>   In dpdk offical website: https://doc.dpdk.org/guides/sample_app_ug/dma.html

The documentation itself is generated from the DPDK source-code repo; and then hosted on the website.
This email list is usually for the "normal" website (https://dpdk.org) and not the docs.
The documentation is available in git, see the docs/ directory in   https://git.dpdk.org/dpdk/tree

>   There may be a quotation of code that dosen't match the introduction in "13.4.3. The Lcores Processing Functions".
>   It's suppose to be the code of rte_eth_rx_burst() after the second paragraph;
>   I hope this is helpful!

The code snippet indeed seems a duplicate/incorrect. Would you like to submit a git patch to fix?
Modifying the following file, and updating it to the intended code snippet would be a welcome fixup to the DPDK docs:
https://git.dpdk.org/dpdk/tree/doc/guides/sample_app_ug/dma.rst#n288

(The contributing guide details the steps in case you're not familiar: https://doc.dpdk.org/guides/contributing/patches.html)

Regards, -Harry

      reply	other threads:[~2024-06-28  9:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28  8:49 skillwell
2024-06-28  9:33 ` Van Haaren, Harry [this message]

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=PH8PR11MB6803AD73ECF2916438F82359D7D02@PH8PR11MB6803.namprd11.prod.outlook.com \
    --to=harry.van.haaren@intel.com \
    --cc=skillwell@163.com \
    --cc=web@dpdk.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).