From: "Burton, Ross" <ross.burton@intel.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/6] cryptodev: 1.8 -> 1.9
Date: Thu, 20 Jul 2017 16:14:42 +0100 [thread overview]
Message-ID: <CAJTo0Lb13utF3cwjXS70Q2ZwC4mRBsAGZWj+Z5HeZJTycpmVew@mail.gmail.com> (raw)
In-Reply-To: <20170718185441.GR26405@denix.org>
[-- Attachment #1: Type: text/plain, Size: 265 bytes --]
On 18 July 2017 at 19:54, Denys Dmytriyenko <denis@denix.org> wrote:
> Should this kind of behavior be addressed by BSP Guidelines and the Yocto
> Project Compatible 2.0 requirements?
>
Not sure what it would say other than "don't jump the gun"...
Ross
[-- Attachment #2: Type: text/html, Size: 683 bytes --]
next prev parent reply other threads:[~2017-07-20 15:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 10:15 [PATCH 0/6] Packages Upgrade Robert Yang
2017-07-12 10:15 ` [PATCH 1/6] automake: 1.15 -> 1.15.1 Robert Yang
2017-07-12 10:15 ` [PATCH 2/6] cryptodev: 1.8 -> 1.9 Robert Yang
2017-07-12 12:32 ` Burton, Ross
2017-07-12 13:36 ` Robert Yang
2017-07-12 13:39 ` Burton, Ross
2017-07-13 2:51 ` Robert Yang
2017-07-13 9:50 ` Burton, Ross
2017-07-13 10:03 ` Robert Yang
2017-07-15 13:13 ` Khem Raj
2017-07-18 18:54 ` Denys Dmytriyenko
2017-07-20 15:14 ` Burton, Ross [this message]
2017-07-18 8:45 ` Paul Eggleton
2017-07-18 8:48 ` Robert Yang
2017-07-12 10:15 ` [PATCH 3/6] debianutils: 4.8.1 -> 4.8.1.1 Robert Yang
2017-07-12 10:15 ` [PATCH 4/6] git: 2.11.1 -> 2.13.2 Robert Yang
2017-07-12 15:38 ` Leonardo Sandoval
2017-07-13 2:55 ` Robert Yang
2017-07-13 12:50 ` Jose Lamego
2017-07-12 10:15 ` [PATCH 5/6] gnu-efi: 3.0.5 -> 3.0.6 Robert Yang
2017-07-12 10:15 ` [PATCH 6/6] libbsd: 0.8.3 -> 0.8.5 Robert Yang
2017-07-13 9:40 ` Burton, Ross
2017-07-13 9:45 ` Burton, Ross
2017-07-13 11:10 ` Robert Yang
2017-07-13 13:32 ` Khem Raj
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=CAJTo0Lb13utF3cwjXS70Q2ZwC4mRBsAGZWj+Z5HeZJTycpmVew@mail.gmail.com \
--to=ross.burton@intel.com \
--cc=denis@denix.org \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.