[meta-intel] [PATCH v2 2/3] metee: add new recipe for version 2.1.0

[Usyskin, Alexander]

> -----Original Message-----
> From: Mittal, Anuj
> Sent: Wednesday, June 19, 2019 02:25
> To: Usyskin, Alexander <alexander.usyskin at intel.com>; meta-
> intel at yoctoproject.org
> Cc: Winkler, Tomas <tomas.winkler at intel.com>
> Subject: Re: [meta-intel] [PATCH v2 2/3] metee: add new recipe for version 2.1.0
> 
> On Tue, 2019-06-18 at 17:15 +0300, Alexander Usyskin wrote:
> > Intel(R) ME TEE Library is the cross-platform access
> > library for Intel(R) CSME HECI interface.
> > Sources at: https://github.com/intel/metee
> >
> > To be used by LMS service.
> >
> > Signed-off-by: Alexander Usyskin <alexander.usyskin at intel.com>
> > ---
> >  recipes-bsp/metee/metee_2.1.0.bb | 18 ++++++++++++++++++
> >  1 file changed, 18 insertions(+)
> >  create mode 100644 recipes-bsp/metee/metee_2.1.0.bb
> >
> > diff --git a/recipes-bsp/metee/metee_2.1.0.bb b/recipes-
> > bsp/metee/metee_2.1.0.bb
> > new file mode 100644
> > index 0000000..cb2e979
> > --- /dev/null
> > +++ b/recipes-bsp/metee/metee_2.1.0.bb
> > @@ -0,0 +1,18 @@
> > +SUMMARY = "Intel(R) METEE Library"
> > +DESCRIPTION = "MEETEE library provides a cross-platform simple \
> > + programing interface for accessing Intel HECI interfaces on devices
> > \
> > + found in BigCore and Atom based products."
> > +
> > +LICENSE = "Apache-2.0"
> > +LIC_FILES_CHKSUM =
> > "file://${S}/COPYING;md5=2ee41112a44fe7014dce33e26468ba93"
> 
> Will change this to remove ${S} while merging.
> 
> > +
> > +COMPATIBLE_HOST = '(i.86|x86_64).*-linux'
> > +
> > +inherit cmake
> > +
> > +SRC_URI = "git://github.com/intel/metee.git;protocol=git;tag=${PV}"
> 
> Using tag would cause bitbake to access network and run git ls-remote
> even when BB_NO_NETWORK is 1. We generally use SRCREV and point it to
> the commit ID. I will make this change and merge if there are no
> objections.
> 
I will post new version of the series with these changes.

I've received request to have these recipes in warrior branch after acceptance to master.
Is such backport acceptable and what is a procedure to do it?

Thanks
--
Sasha