From: <jerinj@marvell.com>
To: <dev@dpdk.org>, Jay Jayatheerthan <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
Date: Sun, 1 May 2022 20:27:21 +0530 [thread overview]
Message-ID: <20220501145721.3776509-1-jerinj@marvell.com> (raw)
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 reply other threads:[~2022-05-01 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 14:57 jerinj [this message]
2022-05-02 7:00 ` Jayatheerthan, Jay
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=20220501145721.3776509-1-jerinj@marvell.com \
--to=jerinj@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jay.jayatheerthan@intel.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).