From: Bruce Richardson <bruce.richardson@intel.com>
To: hemant.agrawal@nxp.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] build: clean up building kernel modules using meson
Date: Wed, 4 Apr 2018 16:57:18 +0100 [thread overview]
Message-ID: <20180404155717.GA40576@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20180404155332.87143-1-bruce.richardson@intel.com>
On Wed, Apr 04, 2018 at 04:53:32PM +0100, Bruce Richardson wrote:
> The meson.build files for building the kernel modules directory could
> be improved now that it is extracted from the EAL. For example, no
> global processing is necessary inside the kernel folder, just need to
> subdir to the appropriate bsd or linux folder to do the actual work.
>
> To avoid potential race conditions with the BSD module builds when
> the kernel build system is creating the dev_if.h and other files,
> we serialize the kernel module builds (all 2 of them!) by setting
> up each module to depend on all the previous.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com>
>
> ---
> v2: serialize the BSD module builds to try and resolve the
> warnings seen about bus_if.h/dev_if.h/etc. in some cases.
> Issue reported by Hemant.
> ---
Hi Hemant,
I haven't been able to reproduce reliably the issue you reported, but the
above fixes what I *think* to be the issue causing the error print. If you
get a chance, can you do a quick re-test and see if it re-occurs for you.
If not, I'll apply this version - otherwise I might just apply V1, since
the error itself appears harmless, as you say.
/Bruce
next prev parent reply other threads:[~2018-04-04 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 17:38 [dpdk-dev] [PATCH] " Bruce Richardson
2018-02-22 18:04 ` Hemant Agrawal
[not found] ` <20180404155332.87143-1-bruce.richardson@intel.com>
2018-04-04 15:57 ` Bruce Richardson [this message]
2018-04-04 16:47 ` [dpdk-dev] [PATCH v2] " Hemant Agrawal
2018-04-04 18:27 ` Bruce Richardson
2018-04-04 16:04 ` Bruce Richardson
2018-04-04 20:00 ` Bruce Richardson
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=20180404155717.GA40576@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.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).