DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ayuj Verma <ayverma@marvell.com>
To: <akhil.goyal@nxp.com>, <arkadiuszx.kusztal@intel.com>,
	<fiona.trahe@intel.com>
Cc: <shallyv@marvell.com>, <ssahu@marvell.com>,
	<kkotamarthy@marvell.com>, <adesai@marvell.com>, <dev@dpdk.org>,
	Ayuj Verma <ayverma@marvell.com>
Subject: [dpdk-dev] [PATCH v1] fix alphabetical ordering of headers
Date: Fri, 12 Apr 2019 12:33:21 +0530	[thread overview]
Message-ID: <1555052602-19155-1-git-send-email-ayverma@marvell.com> (raw)
Message-ID: <20190412070321.89frM2nchDsFmE-rALO-MRHJXofChEPWet-9iwWff6E@z> (raw)

rte_crypto_sym.h is included prior to rte_crypto_asym.h
in rte_crypto.h, which breaks alphabetical order.

include rte_crypto_sym.h in rte_crypto_asym.h fixes this.

Ayuj Verma (1):
  lib/crypto: fix alphabetical ordering of headers

 lib/librte_cryptodev/rte_crypto.h      | 1 -
 lib/librte_cryptodev/rte_crypto_asym.h | 2 ++
 2 files changed, 2 insertions(+), 1 deletion(-)

-- 
1.8.3.1


             reply	other threads:[~2019-04-12  7:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12  7:03 Ayuj Verma [this message]
2019-04-12  7:03 ` Ayuj Verma
2019-04-12  7:03 ` [dpdk-dev] [PATCH v1] lib/crypto: " Ayuj Verma
2019-04-12  7:03   ` Ayuj Verma
2019-04-18  3:58   ` Anoob Joseph
2019-04-18  3:58     ` Anoob Joseph
2019-04-22 12:52     ` Shally Verma
2019-04-22 12:52       ` Shally Verma
2019-04-23  5:42       ` Anoob Joseph
2019-04-23  5:42         ` Anoob Joseph
2019-04-23  6:26         ` Akhil Goyal
2019-04-23  6:26           ` Akhil Goyal
2019-04-12 15:17 ` [dpdk-dev] [PATCH v1] " Trahe, Fiona
2019-04-12 15:17   ` Trahe, Fiona
2019-04-16 16:15   ` Ayuj Verma
2019-04-16 16:15     ` Ayuj Verma
2019-04-16  7:40 Akhil Goyal
2019-04-16  7:40 ` Akhil Goyal
2019-04-17  9:57 Akhil Goyal
2019-04-17  9:57 ` Akhil Goyal
2019-04-17 11:24 ` Trahe, Fiona
2019-04-17 11:24   ` 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=1555052602-19155-1-git-send-email-ayverma@marvell.com \
    --to=ayverma@marvell.com \
    --cc=adesai@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=kkotamarthy@marvell.com \
    --cc=shallyv@marvell.com \
    --cc=ssahu@marvell.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).