From: Patrick Ohly <patrick.ohly@intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 0/1] Add recipe whitelisting class
Date: Fri, 28 Aug 2015 10:28:40 +0200 [thread overview]
Message-ID: <1440750520.3006.81.camel@intel.com> (raw)
In-Reply-To: <cover.1440678731.git.paul.eggleton@linux.intel.com>
On Thu, 2015-08-27 at 13:36 +0100, Paul Eggleton wrote:
> Changes since the RFC version:
> * Check BPN in addition to PN for matching, to make it easier in the
> multilib case
> * Use PNWHITELIST_LAYERS to specify which layers to apply whitelisting to,
> and consider an empty whitelist value to be no recipes whitelisted (so
> you can set up empty whitelists for layers not yet in your
> configuration if you wish to do so). This also makes setting
> PNWHITELIST without an override practical.
> * Touch up the comments
I've tried various configuration variations and it works fine now, so +1
from me.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2015-08-28 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 12:36 [PATCH v2 0/1] Add recipe whitelisting class Paul Eggleton
2015-08-27 12:36 ` [PATCH v2 1/1] classes/whitelist: add class to allow whitelisting recipes from a layer Paul Eggleton
2015-08-28 6:07 ` Khem Raj
2015-08-28 8:34 ` Paul Eggleton
2015-08-28 13:09 ` Paul Eggleton
2015-08-28 15:11 ` Khem Raj
2015-08-28 13:55 ` Otavio Salvador
2015-08-28 14:00 ` Paul Eggleton
2015-08-28 14:09 ` Otavio Salvador
2015-08-28 14:19 ` Paul Eggleton
2015-08-28 17:32 ` Otavio Salvador
2015-08-28 8:28 ` Patrick Ohly [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=1440750520.3006.81.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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