From: Srujana Challa <schalla@marvell.com>
To: David Miller <davem@davemloft.net>
Cc: "herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"Suheil Chandran" <schandran@marvell.com>,
Narayana Prasad Raju Athreya <pathreya@marvell.com>,
Sunil Kovvuri Goutham <sgoutham@marvell.com>
Subject: RE: [PATCH 2/4] drivers: crypto: add support for OCTEONTX2 CPT engine
Date: Mon, 27 Jul 2020 14:12:46 +0000 [thread overview]
Message-ID: <BYAPR18MB2821DDBE4F651E423791C422A0720@BYAPR18MB2821.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20200724.201457.2120372254880301593.davem@davemloft.net>
> -----Original Message-----
> From: linux-crypto-owner@vger.kernel.org <linux-crypto-
> owner@vger.kernel.org> On Behalf Of David Miller
> Sent: Saturday, July 25, 2020 8:45 AM
> To: Srujana Challa <schalla@marvell.com>
> Cc: herbert@gondor.apana.org.au; netdev@vger.kernel.org; linux-
> crypto@vger.kernel.org; Suheil Chandran <schandran@marvell.com>; Narayana
> Prasad Raju Athreya <pathreya@marvell.com>; Sunil Kovvuri Goutham
> <sgoutham@marvell.com>
> Subject: Re: [PATCH 2/4] drivers: crypto: add support for OCTEONTX2 CPT engine
>
> From: Srujana Challa <schalla@marvell.com>
> Date: Fri, 24 Jul 2020 18:38:02 +0530
>
> > diff --git a/drivers/crypto/marvell/octeontx2/otx2_cpt_common.h
> b/drivers/crypto/marvell/octeontx2/otx2_cpt_common.h
> > new file mode 100644
> > index 0000000..00cd534
> > --- /dev/null
> > +++ b/drivers/crypto/marvell/octeontx2/otx2_cpt_common.h
> > @@ -0,0 +1,53 @@
> > +/* SPDX-License-Identifier: GPL-2.0-only
> > + * Copyright (C) 2020 Marvell.
> > + */
> > +
> > +#ifndef __OTX2_CPT_COMMON_H
> > +#define __OTX2_CPT_COMMON_H
> > +
> > +#include <linux/pci.h>
> > +#include <linux/types.h>
> > +#include <linux/module.h>
> > +#include <linux/delay.h>
> > +#include <linux/crypto.h>
> > +#include "otx2_cpt_hw_types.h"
> > +#include "rvu.h"
>
> How can this build? "rvu.h" is in the "af/" subdirectory.
On our test setup, the build is always successful, as we are adding "af/" subdirectory in ccflags list ([PATCH 4/4] crypto: marvell: enable OcteonTX2 cpt options for build).
next prev parent reply other threads:[~2020-07-27 14:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 13:08 [PATCH 0/4] Add Support for Marvell OcteonTX2 Cryptographic Srujana Challa
2020-07-24 13:08 ` [PATCH 1/4] octeontx2-af: add support to manage the CPT unit Srujana Challa
2020-07-24 13:08 ` [PATCH 2/4] drivers: crypto: add support for OCTEONTX2 CPT engine Srujana Challa
2020-07-25 3:14 ` David Miller
2020-07-27 14:12 ` Srujana Challa [this message]
2020-07-27 19:48 ` David Miller
2020-07-28 7:17 ` Srujana Challa
2020-07-24 13:08 ` [PATCH 3/4] drivers: crypto: add the Virtual Function driver for OcteonTX2 CPT Srujana Challa
2020-07-24 13:08 ` [PATCH 4/4] crypto: marvell: enable OcteonTX2 cpt options for build Srujana Challa
2020-07-24 20:42 ` kernel test robot
2020-07-24 23:54 ` kernel test robot
2020-07-26 3:55 ` [PATCH 0/4] Add Support for Marvell OcteonTX2 Cryptographic sundeep subbaraya
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=BYAPR18MB2821DDBE4F651E423791C422A0720@BYAPR18MB2821.namprd18.prod.outlook.com \
--to=schalla@marvell.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pathreya@marvell.com \
--cc=schandran@marvell.com \
--cc=sgoutham@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).