From: Thomas Monjalon <thomas@monjalon.net>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: dev@dpdk.org, "De Lara Guarch,
Pablo" <pablo.de.lara.guarch@intel.com>,
"Jozwiak, TomaszX" <tomaszx.jozwiak@intel.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/qat: fix typo
Date: Mon, 17 Sep 2018 09:56:24 +0200 [thread overview]
Message-ID: <2055857.TpLNcSUbBa@xps> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B4358960044D@IRSMSX101.ger.corp.intel.com>
Hi,
10/08/2018 17:20, Trahe, Fiona:
> > -/**< Intel(R) QAT Symmetric Crypto PMD device name */
> > +/**< Intel(R) QAT Symmetric Crypto PMD driver name */
> > #define CRYPTODEV_NAME_QAT_SYM_PMD crypto_qat
The comment is above, so the syntax should be /**, not /**<
Do you want me to fix it when pulling in master?
next prev parent reply other threads:[~2018-09-17 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 15:20 Trahe, Fiona
2018-08-13 14:39 ` Jozwiak, TomaszX
2018-08-23 12:55 ` Akhil Goyal
2018-09-17 7:56 ` Thomas Monjalon [this message]
2018-09-17 9:01 ` Trahe, Fiona
-- strict thread matches above, loose matches on Subject: below --
2017-06-29 11:16 Pablo de Lara
2017-06-29 19:46 ` Jain, Deepak K
2017-06-30 6:23 ` De Lara Guarch, Pablo
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=2055857.TpLNcSUbBa@xps \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=tomaszx.jozwiak@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 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).