From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Guo, Jia" <jia.guo@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Guo@dpdk.org" <Guo@dpdk.org>
Subject: Re: [PATCH v3] doc: add known uio_pci_generic issue for i40e
Date: Thu, 19 Jan 2017 14:53:54 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2026B77E7@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <01BA8470C017D6468C8290E4B9C5E1E83B1D4A6F@shsmsx102.ccr.corp.intel.com>
> -----Original Message-----
> From: Guo, Jia
> Sent: Thursday, January 19, 2017 1:50 PM
> To: Mcnamara, John <john.mcnamara@intel.com>; Zhang, Helin
> <helin.zhang@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>
> Cc: dev@dpdk.org; Guo@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v3] doc: add known uio_pci_generic issue
> for i40e
>
> Hi,john
> The "bind uio_pci_generic`` is not the definitely command, but very
> appreciate for your correcting the other syntax issue. I will involve them
> in v4, Thanks very much.
Hi Jeff,
Variables, functions, program names, file names and any other literal should
be in backtick quotes, as outlined in the DPDK Documentation:
http://dpdk.org/doc/guides/contributing/documentation.html#code-and-literal-block-sections
So uio_pci_generic should be quoted with backticks. If you want to add bind then do:
``--bind= uio_pci_generic`` or similar.
Either way it shouldn't be quoted using the "smart" Unicode or non-Unicode quotes as in the
patch. All quotes should be straight ASCII double quotes (""). The Html/PDF renderers
will convert to the correct quotes as required.
> > related `linux kernel commit
> > + < https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
> > stable.git/commit/drivers/pci/quirks.c?id=8bcf4525c5d43306c5fd07e132bc
> > 8650
> > e3491aec>`_.
Also, this link generates a doc build error. I think because of the space
between the < and the https:.
John
next prev parent reply other threads:[~2017-01-19 14:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 2:35 [PATCH] doc: add known issue for uio_pci_generic in XL710 Jeff Guo
2016-02-12 16:39 ` [PATCH v2] doc: add known uio_pci_generic issue for i40e Jeff Guo
2017-01-16 20:30 ` Ferruh Yigit
2017-01-17 17:00 ` Wu, Jingjing
2017-01-17 17:36 ` Ferruh Yigit
2017-01-18 2:48 ` Guo, Jia
2017-01-18 18:49 ` Ferruh Yigit
2016-07-06 14:10 ` Jeff Guo
2017-01-09 7:16 ` [PATCH] doc: add known issue for uio_pci_generic in XL710 Wu, Jingjing
2017-01-12 3:27 ` [PATCH v2] doc: add known uio_pci_generic issue for i40e Jeff Guo
2017-01-17 14:12 ` Wu, Jingjing
2017-01-19 10:52 ` [PATCH v3] " Jeff Guo
2017-01-19 10:56 ` Jeff Guo
2017-01-19 11:17 ` Mcnamara, John
2017-01-19 13:50 ` Guo, Jia
2017-01-19 14:53 ` Mcnamara, John [this message]
2017-01-20 2:28 ` Guo, Jia
2017-01-19 12:06 ` Ferruh Yigit
2017-01-19 13:53 ` Guo, Jia
2017-01-19 13:56 ` [PATCH v4] " Jeff Guo
2017-01-20 2:51 ` Jeff Guo
2017-01-22 1:46 ` Jeff Guo
2017-01-22 2:03 ` Jeff Guo
2017-01-23 8:04 ` Mcnamara, John
2017-01-23 11:44 ` Ferruh Yigit
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=B27915DBBA3421428155699D51E4CFE2026B77E7@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=Guo@dpdk.org \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jia.guo@intel.com \
--cc=jingjing.wu@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.