From: "Jayatheerthan, Jay" <jay.jayatheerthan@intel.com>
To: "jerinj@marvell.com" <jerinj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>, Ray Kinsella <mdr@ashroe.eu>,
Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [dpdk-dev] [PATCH] doc: fix build error with sphinx 4.5.0
Date: Mon, 2 May 2022 07:00:18 +0000 [thread overview]
Message-ID: <DM6PR11MB43482A6C0BABC8A66BCD05FFFDC19@DM6PR11MB4348.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220501145721.3776509-1-jerinj@marvell.com>
Looks good, thanks!
Acked-by: Jay Jayatheerthan <jay.jayatheerthan@intel.com>
-Jay
> -----Original Message-----
> From: jerinj@marvell.com <jerinj@marvell.com>
> Sent: Sunday, May 1, 2022 8:27 PM
> To: dev@dpdk.org; Jayatheerthan, Jay <jay.jayatheerthan@intel.com>; Jerin Jacob <jerinj@marvell.com>; Ray Kinsella
> <mdr@ashroe.eu>; Pavan Nikhilesh <pbhagavatula@marvell.com>
> Cc: thomas@monjalon.net; david.marchand@redhat.com; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: fix build error with sphinx 4.5.0
>
> From: Jerin Jacob <jerinj@marvell.com>
>
> Latest sphinx checks c language syntax more aggressively.
> Fix the following warning by correcting c language syntax.
>
> doc/guides/prog_guide/event_ethernet_rx_adapter.rst:243:
> WARNING: Could not lex literal_block as "c". Highlighting skipped.
>
> Fixes: 3c838062b91f ("eventdev: introduce event vector Rx capability")
> Cc: Pavan Nikhilesh <pbhagavatula@marvell.com>
> Cc: stable@dpdk.org
>
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> ---
> doc/guides/prog_guide/event_ethernet_rx_adapter.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/prog_guide/event_ethernet_rx_adapter.rst b/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
> index 67b11e1563..3b4ef502b2 100644
> --- a/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
> +++ b/doc/guides/prog_guide/event_ethernet_rx_adapter.rst
> @@ -257,8 +257,8 @@ A loop processing ``rte_event_vector`` containing mbufs is shown below.
> /* Process each mbuf. */
> }
> break;
> - case ...
> - ...
> + case default:
> + /* Handle other event_types. */
> }
>
> Rx event vectorization for SW Rx adapter
> --
> 2.36.0
next prev parent reply other threads:[~2022-05-02 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 14:57 jerinj
2022-05-02 7:00 ` Jayatheerthan, Jay [this message]
2022-05-09 16:07 ` Jerin Jacob
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=DM6PR11MB43482A6C0BABC8A66BCD05FFFDC19@DM6PR11MB4348.namprd11.prod.outlook.com \
--to=jay.jayatheerthan@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mdr@ashroe.eu \
--cc=pbhagavatula@marvell.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).