From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Joe Slater <jslater@windriver.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-selinux][PATCH 1/1] audit: Fixed swig host contamination issue
Date: Thu, 01 Aug 2013 18:06:33 +0100 [thread overview]
Message-ID: <39299095.V2I0ppqtmc@helios> (raw)
In-Reply-To: <1375374204-5632-1-git-send-email-jslater@windriver.com>
Hi Joe,
On Thursday 01 August 2013 09:23:24 Joe Slater wrote:
> From: Anders Hedlund <anders.hedlund@windriver.com>
>
> CQID: 428272
>
> The audit build uses swig to generate a python wrapper.
> Unfortunately, the swig info file references host include
> directories. Some of these were previously noticed and
> eliminated, but the one fixed here was not.
>
> Signed-off-by: Anders Hedlund <anders.hedlund@windriver.com>
> Signed-off-by: Joe Slater <jslater@windriver.com>
These meta-selinux patches should go to the yocto@yoctoproject.org mailing
list, as specified in the MAINTAINERS file in meta-selinux.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-08-01 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 16:23 [meta-selinux][PATCH 1/1] audit: Fixed swig host contamination issue Joe Slater
2013-08-01 17:06 ` Paul Eggleton [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=39299095.V2I0ppqtmc@helios \
--to=paul.eggleton@linux.intel.com \
--cc=jslater@windriver.com \
--cc=openembedded-devel@lists.openembedded.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