[dpdk-dev,v1] doc: fix sphinx highlighting warnings
Commit Message
Fix warnings raised by Python Sphinx 1.4.5:
guides/sample_app_ug/ip_pipeline.rst:334:
WARNING: Could not lex literal_block as "ini". Highlighting skipped.
guides/sample_app_ug/l2_forward_real_virtual.rst:467:
WARNING: Could not lex literal_block as "c". Highlighting skipped.
guides/sample_app_ug/l3_forward.rst:293:
WARNING: Could not lex literal_block as "c". Highlighting skipped.
guides/sample_app_ug/vm_power_management.rst:162:
WARNING: Could not lex literal_block as "xml". Highlighting skipped.
These warnings arise from invalid syntax in code-block directives.
Fixes: f1e779ec5b50 ("doc: update ip pipeline app guide")
Fixes: d0dff9ba445e ("doc: sample application user guide")
Fixes: c75f4e6a7a2b ("doc: add vm power mgmt app")
Signed-off-by: John McNamara <john.mcnamara@intel.com>
---
doc/guides/sample_app_ug/ip_pipeline.rst | 2 +-
doc/guides/sample_app_ug/l2_forward_real_virtual.rst | 2 +-
doc/guides/sample_app_ug/l3_forward.rst | 2 +-
doc/guides/sample_app_ug/vm_power_management.rst | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
Comments
2016-07-17 14:11, John McNamara:
> Fix warnings raised by Python Sphinx 1.4.5:
>
> guides/sample_app_ug/ip_pipeline.rst:334:
> WARNING: Could not lex literal_block as "ini". Highlighting skipped.
>
> guides/sample_app_ug/l2_forward_real_virtual.rst:467:
> WARNING: Could not lex literal_block as "c". Highlighting skipped.
>
> guides/sample_app_ug/l3_forward.rst:293:
> WARNING: Could not lex literal_block as "c". Highlighting skipped.
>
> guides/sample_app_ug/vm_power_management.rst:162:
> WARNING: Could not lex literal_block as "xml". Highlighting skipped.
>
> These warnings arise from invalid syntax in code-block directives.
>
> Fixes: f1e779ec5b50 ("doc: update ip pipeline app guide")
> Fixes: d0dff9ba445e ("doc: sample application user guide")
> Fixes: c75f4e6a7a2b ("doc: add vm power mgmt app")
>
> Signed-off-by: John McNamara <john.mcnamara@intel.com>
Applied, thanks
@@ -337,7 +337,7 @@ Generic example of configuration file section:
<variable_name_1> = <value_1>
- ...
+ ; ...
<variable_name_N> = <value_N>
@@ -472,7 +472,7 @@ If the table is full, the whole packets table is transmitted using the l2fwd_sen
l2fwd_send_packet(struct rte_mbuf *m, uint8_t port)
{
unsigned lcore_id, len;
- struct lcore_queue_conf \*qconf;
+ struct lcore_queue_conf *qconf;
lcore_id = rte_lcore_id();
qconf = &lcore_queue_conf[lcore_id];
@@ -298,7 +298,7 @@ The get_ipv4_dst_port() function is shown below:
int ret = 0;
union ipv4_5tuple_host key;
- ipv4_hdr = (uint8_t \*)ipv4_hdr + offsetof(struct ipv4_hdr, time_to_live);
+ ipv4_hdr = (uint8_t *)ipv4_hdr + offsetof(struct ipv4_hdr, time_to_live);
m128i data = _mm_loadu_si128(( m128i*)(ipv4_hdr));
@@ -167,7 +167,7 @@ Virtio-Serial channels are configured via libvirt XML:
</controller>
<channel type='unix'>
<source mode='bind' path='/tmp/powermonitor/{vm_name}.{channel_num}'/>
- <target type='virtio' name='virtio.serial.port.poweragent.{vm_channel_num}/>
+ <target type='virtio' name='virtio.serial.port.poweragent.{vm_channel_num}'/>
<address type='virtio-serial' controller='0' bus='0' port='{N}'/>
</channel>