From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "O Mahony, Billy" <billy.o.mahony@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: Fix typo in qat.rst
Date: Mon, 27 Nov 2017 11:20:26 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC4F61B@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1511781216-2819-1-git-send-email-billy.o.mahony@intel.com>
> -----Original Message-----
> From: O Mahony, Billy
> Sent: Monday, November 27, 2017 11:14 AM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>;
> dev@dpdk.org
> Cc: O Mahony, Billy <billy.o.mahony@intel.com>
> Subject: [PATCH] cryptodev: Fix typo in qat.rst
>
> Signed-off-by: Billy O'Mahony <billy.o.mahony@intel.com>
> ---
> doc/guides/cryptodevs/qat.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst
> index cb17b6b..c8ef378 100644
> --- a/doc/guides/cryptodevs/qat.rst
> +++ b/doc/guides/cryptodevs/qat.rst
> @@ -166,7 +166,7 @@ Next, you need to expose the Virtual Functions
> (VFs) using the sysfs file system First find the BDFs (Bus-Device-Function) of
> the physical functions (PFs) of your device, e.g.::
>
> - lspci -d : 37c8
> + lspci -d:37c8
>
> You should see output similar to::
>
> --
> 2.7.4
Hi Billy,
Since this is a patch for documentation, the title should start with "doc:",
as "cryptodev: ..." suggests that the patch is fixing something in the library code.
I will fix it for you, since the rest of the patch looks ok to me.
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2017-11-27 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 11:13 Billy O'Mahony
2017-11-27 11:20 ` De Lara Guarch, Pablo [this message]
2017-11-27 15:33 ` O Mahony, Billy
2017-12-11 10:40 ` De Lara Guarch, Pablo
-- strict thread matches above, loose matches on Subject: below --
2017-11-25 22:11 Billy O'Mahony
2017-11-27 10:35 ` Trahe, Fiona
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=E115CCD9D858EF4F90C690B0DCB4D8976CC4F61B@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=billy.o.mahony@intel.com \
--cc=dev@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).