On mån, 2018-04-16 at 08:03 -0700, Armin Kuster wrote: > I understand some of these changes a harsh. This set of changes allow > this layer to pass the > yocto-check-layer. This is one of many options to address passing. >
Hi Armin, Thanks for doing this. The series is good, and I merged it with some minor changes, see below. I also fixed the LAYERSERIES_COMPAT issue in meta-cgl-common so you won't have to resend that series. Regards, --Adrian > Armin Kuster (5): > meta-cgl-fsl-ppc: drop layer supporting old kernel This patch didn't apply without your patches from the LAYERSERIES_COMPAT series which wasn't correct. I was going to drop the layer anyways, so I did it in a separate commit to simplify things. > Corosync: remove recipe its in meta-networking. > makedumpfile: remove as its in meta-oe > iscsi-initiator-utils: drop bbappends > meta-cge-common: Add README Fixed typo in subject. > > meta-cgl-common/README | 138 > ++++++++++++++++++ > .../corosync/build-cleanup-configure-ac.patch | 57 -------- > .../corosync/corosync/corosync-docs.patch | 37 ----- > .../corosync/corosync/corosync-notifyd.service | 13 -- > .../recipes-cgl/corosync/corosync/corosync.init | 160 --------- > ------------ > .../recipes-cgl/corosync/corosync/corosync.service | 26 ---- > .../corosync/corosync/fix-define-semun-union.patch | 20 --- > .../corosync/corosync/groff-desc-path.patch | 12 -- > .../recipes-cgl/corosync/corosync/notifyd.init | 120 --------- > ------- > .../recipes-cgl/corosync/corosync/volatiles | 1 - > .../recipes-cgl/corosync/corosync_1.4.8.bb | 88 --------- > --- > .../files/alias-powerpc-powerpc32.patch | 18 --- > .../recipes-cgl/makedumpfile/makedumpfile_1.5.8.bb | 20 --- > .../iscsi-initiator-utils_%.bbappend | 1 - > meta-cgl-fsl-ppc/conf/layer.conf | 14 -- > ...p-inherit-auth-capable-on-INIT-collisions.patch | 41 ------ > ...erpc-Fix-64-bit-builds-with-binutils-2.24.patch | 80 ----------- > .../linux/linux-qoriq-cgl-prt_3.12.bb | 36 ----- > 18 files changed, 138 insertions(+), 744 deletions(-) > create mode 100644 meta-cgl-common/README > delete mode 100644 meta-cgl-common/recipes- > cgl/corosync/corosync/build-cleanup-configure-ac.patch > delete mode 100644 meta-cgl-common/recipes- > cgl/corosync/corosync/corosync-docs.patch > delete mode 100644 meta-cgl-common/recipes- > cgl/corosync/corosync/corosync-notifyd.service > delete mode 100644 meta-cgl-common/recipes- > cgl/corosync/corosync/corosync.init > delete mode 100644 meta-cgl-common/recipes- > cgl/corosync/corosync/corosync.service > delete mode 100644 meta-cgl-common/recipes- > cgl/corosync/corosync/fix-define-semun-union.patch > delete mode 100644 meta-cgl-common/recipes- > cgl/corosync/corosync/groff-desc-path.patch > delete mode 100644 meta-cgl-common/recipes- > cgl/corosync/corosync/notifyd.init > delete mode 100644 meta-cgl-common/recipes- > cgl/corosync/corosync/volatiles > delete mode 100644 meta-cgl-common/recipes- > cgl/corosync/corosync_1.4.8.bb > delete mode 100644 meta-cgl-common/recipes- > cgl/makedumpfile/files/alias-powerpc-powerpc32.patch > delete mode 100644 meta-cgl-common/recipes- > cgl/makedumpfile/makedumpfile_1.5.8.bb > delete mode 100644 meta-cgl-common/recipes-extended/iscsi-initiator- > utils/iscsi-initiator-utils_%.bbappend > delete mode 100644 meta-cgl-fsl-ppc/conf/layer.conf > delete mode 100644 meta-cgl-fsl-ppc/recipes-kernel/linux/files/Fix- > CVE-2014-5077-sctp-inherit-auth-capable-on-INIT-collisions.patch > delete mode 100644 meta-cgl-fsl-ppc/recipes- > kernel/linux/files/powerpc-Fix-64-bit-builds-with-binutils-2.24.patch > delete mode 100644 meta-cgl-fsl-ppc/recipes-kernel/linux/linux- > qoriq-cgl-prt_3.12.bb > > -- > 2.7.4 > This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks. -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
