From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Jain, Deepak K" <deepak.k.jain@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] crypto/qat: fix compile of qat on freebsd
Date: Wed, 21 Sep 2016 18:17:23 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C9FB946@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8973C9FB8BE@IRSMSX108.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of De Lara Guarch,
> Pablo
> Sent: Wednesday, September 21, 2016 10:37 AM
> To: Jain, Deepak K; dev@dpdk.org
> Cc: Gonzalez Monroy, Sergio; stable@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] crypto/qat: fix compile of qat on freebsd
>
>
>
> > -----Original Message-----
> > From: Jain, Deepak K
> > Sent: Wednesday, September 21, 2016 4:23 AM
> > To: dev@dpdk.org
> > Cc: Gonzalez Monroy, Sergio; De Lara Guarch, Pablo; Jain, Deepak K
> > Subject: [PATCH] crypto/qat: fix compile of qat on freebsd
> >
> > Using sys/types.h instead of linux/types.h
> > so as to compile QAT_PMD on freebsd.
> >
> > Fixes: 1703e94ac5ce ("qat: add driver for QuickAssist devices")
> >
> > Signed-off-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
>
> This should get merged in the stable subtree as well.
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2016-09-21 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1474456966-113365-1-git-send-email-deepak.k.jain@intel.com>
2016-09-21 17:37 ` De Lara Guarch, Pablo
2016-09-21 18:17 ` De Lara Guarch, Pablo [this message]
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=E115CCD9D858EF4F90C690B0DCB4D8973C9FB946@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=stable@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).