From: Denys Dmytriyenko <denis@denix.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-architecture@lists.openembedded.org,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/6] cryptodev: 1.8 -> 1.9
Date: Tue, 18 Jul 2017 14:54:41 -0400 [thread overview]
Message-ID: <20170718185441.GR26405@denix.org> (raw)
In-Reply-To: <CAMKF1spYtmTfAw8aaayFkKbU1eJA2cdgqQX7qAH_VBuMu0FX5g@mail.gmail.com>
On Sat, Jul 15, 2017 at 06:13:55AM -0700, Khem Raj wrote:
> On Thu, Jul 13, 2017 at 3:03 AM, Robert Yang <liezhi.yang@windriver.com> wrote:
> >
> >
> > On 07/13/2017 05:50 PM, Burton, Ross wrote:
> >>
> >>
> >> On 13 July 2017 at 03:51, Robert Yang <liezhi.yang@windriver.com
> >> <mailto:liezhi.yang@windriver.com>> wrote:
> >>
> >> BTW, I sent a meta-gplv2 patch to poky@yoctoproject.org
> >> <mailto:poky@yoctoproject.org> two days ago, but
> >> I didn't find it in poky@yoctoproject.org
> >> <mailto:poky@yoctoproject.org>,
> >> Ross, did you see it, please ?
> >> Maybe I should send it again.
> >>
> >>
> >> The list is yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>.
> >> Please
> >> resend to the list.
> >
> >
> > Sorry, I had sent it to yocto@lists.yoctoproject.org which is from README,
> > but
> > I didn't get it in my mailing list, and I resent it to
> > yocto@yoctoproject.org
> > just now, I got it, should we update README, please ?
>
> now meta-intel stepped ahead by applying the patch where as OE-Core
> does not (yet)
> have this patch applied. meta-intel should have waited for this patch
> to land in master.
Should this kind of behavior be addressed by BSP Guidelines and the Yocto
Project Compatible 2.0 requirements?
Also, which BSPs are enabled on the OE-Core autobuilder by default?
--
Denys
next prev parent reply other threads:[~2017-07-18 18:54 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 [this message]
2017-07-20 15:14 ` Burton, Ross
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=20170718185441.GR26405@denix.org \
--to=denis@denix.org \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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