patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: roy.fan.zhang@intel.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] crypto/scheduler: fix include of local headers
Date: Tue, 28 Mar 2017 12:04:49 +0100	[thread overview]
Message-ID: <20170328110448.GA22460@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <20170328105816.22502-1-bruce.richardson@intel.com>

On Tue, Mar 28, 2017 at 11:58:16AM +0100, Bruce Richardson wrote:
> When a C file for a library/driver is including the public header files for
> that library, those need to be included as local includes using quotes
> rather than angle-brackets. Without doing so, parallel builds can fail, as
> the compiler will only look for those headers in the global include folder
> rather than locally, and the build system does not enforce that the headers
> for a lib are installed before the rest of the lib is compiled.
> 
> Fixes: 097ab0bac017 ("crypto/scheduler: add API")
> Fixes: 503e9c5afb38 ("crypto/scheduler: register as vdev driver")
> Fixes: 31439ee72b2c ("crypto/scheduler: add API implementations")
> 
> CC: stable@dpdk.org
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
>  drivers/crypto/scheduler/rte_cryptodev_scheduler.c | 2 +-
>  drivers/crypto/scheduler/rte_cryptodev_scheduler.h | 2 +-
>  drivers/crypto/scheduler/scheduler_pmd.c           | 2 +-
>  drivers/crypto/scheduler/scheduler_pmd_private.h   | 2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)
> 
Two follow-up points:

* Even though this is a crypto patch, I think it should go in main tree
  as builds are broken right now if you turn on the PMD and use a large
  -j setting. (i.e. it's broken for me!! :-) )
* Is there a reason why this PMD is disabled by default? It doesn't
  appear to have any external dependencies and if we turn it on by
  default we should be able to catch issues like this a lot quicker.

Regards,
/Bruce

  reply	other threads:[~2017-03-28 11:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 10:58 Bruce Richardson
2017-03-28 11:04 ` Bruce Richardson [this message]
2017-03-28 12:04   ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon

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=20170328110448.GA22460@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=roy.fan.zhang@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).