Re: [OE-core] Patchwork and incoming patch testing

[Trevor Woerner]

On Wed 2017-01-18 @ 07:05:58 AM, Paul Eggleton wrote:
> This should give us a bit more visibility into 
> where patches are at in the process, although we are still working on a few 
> places where patch series status needs to be updated (e.g. when a patch goes 
> into testing).

Is the testing process for OE patches formalized?

I'm not referring to the Yocto Project's release testing.
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] ✗ patchtest: failure for bash 4.3.30 -> 4.4

[Patchwork]

== Series Details ==

Series: bash 4.3.30 -> 4.4
Revision: 1
URL   : https://patchwork.openembedded.org/series/4836/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Patchbash 4.3.30 -> 4.4
 Issue Shortlog does not follow expected format 
[test_shortlog_format] 
  Suggested fixCommit shortlog (first line of commit message) should follow 
the format ": "

* Issue Added patch file is missing Upstream-Status in the header 
[test_upstream_status_presence] 
  Suggested fixAdd Upstream-Status:  to the header of 
meta/recipes-extended/bash/bash/0001-patch-to-obtain-pkgconfig-sanity.patch 
(possible values: Pending, Submitted, Accepted, Backport, Denied, Inappropriate)

* Issue Series does not apply on top of target branch 
[test_series_merge_on_head] 
  Suggested fixRebase your series on top of targeted branch
  Targeted branch  master (currently at a7cb408dd7)



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH v2] elfutils 0.166->0.167

[Zheng, Ruoqin]

Ping



-Original Message-
From: Zheng, Ruoqin/郑 若钦 
Sent: Friday, December 23, 2016 10:16 AM
To: openembedded-core@lists.openembedded.org
Cc: Zheng, Ruoqin/郑 若钦 
Subject: [OE-core] [PATCH v2] elfutils 0.166->0.167

1) Upgrade elfutils from 0.166 to 0.167
2) Delete 5 patches below, since they are integrated upstream.

elfutils-0.166/0001-elf_getarsym-Silence-Werror-maybe-uninitialized-fals.patch
elfutils-0.166/0001-remove-the-unneed-checking.patch
elfutils-0.166/aarch64_uio.patch
elfutils-0.166/fixheadercheck.patch
elfutils-0.166/shadow.patch

3) Rename 4 patches below to make it compatible with new version
elfutils-0.166/hppa_backend.diff -> elfutils-0.167/hppa_backend.diff
elfutils-0.166/mips_backend.diff -> elfutils-0.167/mips_backend.diff
elfutils-0.166/m68k_backend.diff -> elfutils-0.167/m68k_backend.diff

elfutils-0.166/0001-build-Provide-alternatives-for-glibc-assumptions-hel.patch 
-> 
elfutils-0.167/0001-build-Provide-alternatives-for-glibc-assumptions-hel.patch

Signed-off-by: Zheng Ruoqin 
---
 ...m-Silence-Werror-maybe-uninitialized-fals.patch |  35 -
 .../0001-remove-the-unneed-checking.patch  |  38 --
 .../elfutils/elfutils-0.166/aarch64_uio.patch  |  47 --
 .../elfutils/elfutils-0.166/fixheadercheck.patch   |  23 -
 .../elfutils/elfutils-0.166/m68k_backend.diff  | 492 --
 .../elfutils/elfutils-0.166/shadow.patch   |  23 -
 ...ferences-between-mips-machine-identifiers.patch |   0
 ...de-alternatives-for-glibc-assumptions-hel.patch | 705 +
 .../0001-fix-a-stack-usage-warning.patch   |   0
 ...-support-for-mips64-abis-in-mips_retval.c.patch |   0
 .../0003-Add-mips-n64-relocation-format-hack.patch |   0
 .../arm_backend.diff   |   0
 .../elfcmp-fix-self-comparision.patch  |   0
 .../hppa_backend.diff  | 173 +++--
 .../kfreebsd_path.patch|   0
 .../elfutils/elfutils-0.167/m68k_backend.diff  |  27 +
 .../mips_backend.diff  | 168 ++---
 .../mips_readelf_w.patch   |   0
 .../testsuite-ignore-elflint.diff  |   0
 .../uclibc-support.patch   |   0
 .../{elfutils_0.166.bb => elfutils_0.167.bb}   |  12 +-
 21 files changed, 539 insertions(+), 1204 deletions(-)
 delete mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.166/0001-elf_getarsym-Silence-Werror-maybe-uninitialized-fals.patch
 delete mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.166/0001-remove-the-unneed-checking.patch
 delete mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.166/aarch64_uio.patch
 delete mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.166/fixheadercheck.patch
 delete mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.166/m68k_backend.diff
 delete mode 100644 meta/recipes-devtools/elfutils/elfutils-0.166/shadow.patch
 rename meta/recipes-devtools/elfutils/{elfutils-0.166 => 
elfutils-0.167}/0001-Ignore-differences-between-mips-machine-identifiers.patch 
(100%)
 rename meta/recipes-devtools/elfutils/{elfutils-0.166 => 
elfutils-0.167}/0001-build-Provide-alternatives-for-glibc-assumptions-hel.patch 
(51%)
 rename meta/recipes-devtools/elfutils/{elfutils-0.166 => 
elfutils-0.167}/0001-fix-a-stack-usage-warning.patch (100%)
 rename meta/recipes-devtools/elfutils/{elfutils-0.166 => 
elfutils-0.167}/0002-Add-support-for-mips64-abis-in-mips_retval.c.patch (100%)
 rename meta/recipes-devtools/elfutils/{elfutils-0.166 => 
elfutils-0.167}/0003-Add-mips-n64-relocation-format-hack.patch (100%)
 rename meta/recipes-devtools/elfutils/{elfutils-0.166 => 
elfutils-0.167}/arm_backend.diff (100%)
 rename meta/recipes-devtools/elfutils/{elfutils-0.166 => 
elfutils-0.167}/elfcmp-fix-self-comparision.patch (100%)
 rename meta/recipes-devtools/elfutils/{elfutils-0.166 => 
elfutils-0.167}/hppa_backend.diff (88%)
 rename meta/recipes-devtools/elfutils/{elfutils-0.166 => 
elfutils-0.167}/kfreebsd_path.patch (100%)
 create mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.167/m68k_backend.diff
 rename meta/recipes-devtools/elfutils/{elfutils-0.166 => 
elfutils-0.167}/mips_backend.diff (88%)
 rename meta/recipes-devtools/elfutils/{elfutils-0.166 => 
elfutils-0.167}/mips_readelf_w.patch (100%)
 rename meta/recipes-devtools/elfutils/{elfutils-0.166 => 
elfutils-0.167}/testsuite-ignore-elflint.diff (100%)
 rename meta/recipes-devtools/elfutils/{elfutils-0.166 => 
elfutils-0.167}/uclibc-support.patch (100%)
 rename meta/recipes-devtools/elfutils/{elfutils_0.166.bb => elfutils_0.167.bb} 
(85%)

diff --git 
a/meta/recipes-devtools/elfutils/elfutils-0.166/0001-elf_getarsym-Silence-Werror-maybe-uninitialized-fals.patch
 
b/meta/recipes-devtools/elfutils/elfutils-0.166/0001-elf_getarsym-Silence-Werror-maybe-uninitialized-fals.patch
deleted file mode 100644
index 

[OE-core] [PATCH] bash 4.3.30 -> 4.4

[Zheng Ruoqin]

1) Upgrade bash from 4.3.30 to 4.4
2) Delete 1 patche below, since they are integrated upstream.
   fix-run-intl.patch
3) Modify 2 patches below to make it compatible with new version
   fix-run-coproc-run-heredoc-run-execscript-run-test-f.patch
   test-output.patch
4) Add 1 patche below to solve pkgconfig sanity error
   0001-patch-to-obtain-pkgconfig-sanity.patch

Signed-off-by: Zheng Ruoqin 
---
 .../0001-patch-to-obtain-pkgconfig-sanity.patch|  26 
 ...roc-run-heredoc-run-execscript-run-test-f.patch | 137 ++---
 meta/recipes-extended/bash/bash/fix-run-intl.patch | 110 -
 meta/recipes-extended/bash/bash/test-output.patch  |  20 ++-
 meta/recipes-extended/bash/bash_4.3.30.bb  |  71 ---
 meta/recipes-extended/bash/bash_4.4.bb |  38 ++
 6 files changed, 90 insertions(+), 312 deletions(-)
 create mode 100644 
meta/recipes-extended/bash/bash/0001-patch-to-obtain-pkgconfig-sanity.patch
 delete mode 100644 meta/recipes-extended/bash/bash/fix-run-intl.patch
 delete mode 100644 meta/recipes-extended/bash/bash_4.3.30.bb
 create mode 100644 meta/recipes-extended/bash/bash_4.4.bb

diff --git 
a/meta/recipes-extended/bash/bash/0001-patch-to-obtain-pkgconfig-sanity.patch 
b/meta/recipes-extended/bash/bash/0001-patch-to-obtain-pkgconfig-sanity.patch
new file mode 100644
index 000..031eb90
--- /dev/null
+++ 
b/meta/recipes-extended/bash/bash/0001-patch-to-obtain-pkgconfig-sanity.patch
@@ -0,0 +1,26 @@
+Subject: [PATCH] patch to obtain pkgconfig sanity
+
+Drop the paths from the pkgconfig file bash.pc.in which will cause pkgconfig 
sanity error below:
+ERROR: QA Issue: bash.pc failed sanity test (tmpdir) in path 
/yocto/work001/fnst/zrq/community/poky/build/tmp/work/i586-poky-linux/bash
/4.4-r0/sysroot-destdir/usr/lib/pkgconfig [pkgconfig]
+
+Signed-off-by: Zheng Ruoqin 
+---
+ support/bash.pc.in | 2 --
+ 1 file changed, 2 deletions(-)
+
+diff --git a/support/bash.pc.in b/support/bash.pc.in
+index 6009659..871fa9f 100644
+--- a/support/bash.pc.in
 b/support/bash.pc.in
+@@ -12,8 +12,6 @@ LOCAL_CFLAGS = @LOCAL_CFLAGS@
+ LOCAL_DEFS = @LOCAL_DEFS@
+ CCFLAGS = ${LOCAL_DEFS} ${LOCAL_CFLAGS}
+ 
+-CC = @CC@
+-SHOBJ_CC = @SHOBJ_CC@
+ SHOBJ_CFLAGS = @SHOBJ_CFLAGS@
+ SHOBJ_LD = @SHOBJ_LD@
+ SHOBJ_LDFLAGS = @SHOBJ_LDFLAGS@
+-- 
+2.7.4
+
diff --git 
a/meta/recipes-extended/bash/bash/fix-run-coproc-run-heredoc-run-execscript-run-test-f.patch
 
b/meta/recipes-extended/bash/bash/fix-run-coproc-run-heredoc-run-execscript-run-test-f.patch
index 7f099ae..d6beaff 100644
--- 
a/meta/recipes-extended/bash/bash/fix-run-coproc-run-heredoc-run-execscript-run-test-f.patch
+++ 
b/meta/recipes-extended/bash/bash/fix-run-coproc-run-heredoc-run-execscript-run-test-f.patch
@@ -20,150 +20,35 @@ the test suite should not be run as root
 Upstream-Status: Pending
 
 Signed-off-by: Hongxu Jia 
+Signed-off-by: Zheng Ruoqin 
 ---
- tests/coproc.right   |  5 +
- tests/coproc.tests   | 30 +-
- tests/heredoc.right  |  5 ++---
- tests/heredoc3.sub   |  3 ++-
- tests/run-execscript |  3 ++-
- tests/run-test   |  3 ++-
- 6 files changed, 34 insertions(+), 15 deletions(-)
+ tests/run-execscript | 3 ++-
+ tests/run-test   | 3 ++-
+ 2 files changed, 4 insertions(+), 2 deletions(-)
 
-diff --git a/tests/coproc.right b/tests/coproc.right
-index 6d9deaa..94b001c 100644
 a/tests/coproc.right
-+++ b/tests/coproc.right
-@@ -1,11 +1,8 @@
--84575
- 63 60
- a b c
--84577
- 63 60
- flop
--./coproc.tests: line 22: 84577 Terminated  coproc REFLECT { cat 
-; }
--84579
-+coproc.tests: REFLECT: status 143
- 63 60
- FOO
- 63 60
-diff --git a/tests/coproc.tests b/tests/coproc.tests
-index 8be3563..d347eb7 100644
 a/tests/coproc.tests
-+++ b/tests/coproc.tests
-@@ -1,6 +1,13 @@
-+: ${TMPDIR:=/tmp}
-+TMPOUT=${TMPDIR}/coproc-wait-$BASHPID
-+
- coproc { echo a b c; sleep 2; }
- 
--echo $COPROC_PID
-+case $COPROC_PID in
-+[0-9]*)   ;;
-+*)echo COPROC_PID not integer ;;
-+esac
-+
- echo ${COPROC[@]}
- 
- read LINE <&${COPROC[0]}
-@@ -10,7 +17,11 @@ wait $COPROC_PID
- 
- coproc REFLECT { cat - ; }
- 
--echo $REFLECT_PID
-+case $REFLECT_PID in
-+[0-9]*)   ;;
-+*)echo REFLECT_PID not integer ;;
-+esac
-+
- echo ${REFLECT[@]}
- 
- echo flop >&${REFLECT[1]}
-@@ -18,12 +29,21 @@ read LINE <&${REFLECT[0]}
- 
- echo $LINE
- 
--kill $REFLECT_PID
--wait $REFLECT_PID
-+{ sleep 1; kill $REFLECT_PID; } &
-+wait $REFLECT_PID >$TMPOUT 2>&1 || echo "coproc.tests: REFLECT: status $?"
-+grep 'Terminated.*coproc.*REFLECT' < $TMPOUT >/dev/null 2>&1 || {
-+  echo "coproc.tests: wait for REFLECT failed" >&2
-+}
-+rm -f $TMPOUT
-+exec 2>&1
- 
- coproc xcase -n -u
- 
--echo $COPROC_PID
-+case $COPROC_PID in
-+[0-9]*)   ;;
-+*)echo COPROC_PID not integer ;;
-+esac
-+
- echo ${COPROC[@]}
- 
- echo foo >&${COPROC[1]}
-diff --git 

Re: [OE-core] [PATCH V3 0/4] Persistent /var/log support

[ChenQi]

Hi Ross,

Could you please help review this patch series?
Is there something I need to change?

Best Regards,
Chen Qi

On 12/14/2016 05:08 PM, Chen Qi wrote:

Changes since V2:
Use boolean value consistently. Update the comments to fit the use of boolean 
value.

The following changes since commit d62f18c39bc0ed3b0f5ac8465b393c15f2143ecf:

   targetloader.py: drop test for ClassType (2016-12-12 15:16:39 +)

are available in the git repository at:

   git://git.openembedded.org/openembedded-core-contrib 
ChenQi/persistent-var-log
   
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=ChenQi/persistent-var-log

Chen Qi (4):
   bitbake.conf: add VOLATILE_LOG_DIR variable
   base-files: respect VOLATILE_LOG_DIR
   initscripts: support persistent /var/log
   package.bbclass: support persistent /var/log

  meta/classes/package.bbclass   |  2 +-
  meta/conf/bitbake.conf |  4 ++
  meta/files/fs-perms-persistent-log.txt | 69 ++
  meta/recipes-core/base-files/base-files_3.0.14.bb  |  4 +-
  .../initscripts/initscripts-1.0/volatiles  |  1 -
  meta/recipes-core/initscripts/initscripts_1.0.bb   |  3 +
  6 files changed, 79 insertions(+), 4 deletions(-)
  create mode 100644 meta/files/fs-perms-persistent-log.txt



--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [yocto] [Openembedded-architecture] Patchwork and incoming patch testing

[Jose Lamego]

On 01/18/2017 08:52 AM, Leonardo Sandoval wrote:
> + Jose Lamego
> 
> 
> Jose is doing recent work on the patchwork UI, perhaps there are already
> bugs for the items you are asking.
> 
> 
> On 01/18/2017 02:40 AM, Jussi Kukkonen wrote:
>> This looks great, thanks.
>>
>> On 17 January 2017 at 20:05, Paul Eggleton
>> >
>> wrote:
>>
>> In any event we are now finally in the
>> position where our patchwork instance can be relied upon to
>> collect emails,
>> and the UI is much improved. This should give us a bit more
>> visibility into
>> where patches are at in the process, although we are still working
>> on a few
>> places where patch series status needs to be updated (e.g. when a
>> patch goes
>> into testing).
>>
>>
>> What's the plan for these status updates -- is the idea that you go to
>> patchwork UI to see the state of a specific patch set?
>> Or maybe a reply to either patch sender or even the ML?
>>
There is a request to enable email notifications to submitter for patch
status changes in the future:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7684

The idea is that users should have the option to use what they prefer:
either the email notifications, or the patchwork web interface.

>> On top of patchwork we have built a simple smoke-testing framework
>> called
>> "patchtest" [5] along with a suite of corresponding tests for OE
>> [6]. These
>> tests are fairly simplistic at this point but check the basics
>> such as whether
>> a patch has been properly signed off, etc. We should soon start
>> seeing replies
>> sent to the mailing list and to submitters with results if there
>> are any
>> failures, saving us from noticing and pointing out some of the
>> more obvious
>> classes of mistakes.
>>
>>
>>  Is there a reason for patchwork only showing "success" or "failure"
>> in the web ui, instead of linking to test results at least in in the
>> failure case?
> 
> Jussi, that is a good idea. Right now we need to click into the series,
> then into the patches and then one can see the patch test results,
> obviously, not the best way.
> 
>>
>>
>>
>>  - Jussi
>>
>>
-- 
Jose Lamego | OTC Embedded Platforms & Tools | GDC





signature.asc
Description: OpenPGP digital signature
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] FW: [PATCH][krogoth] libxtst: 1.2.2 -> 1.2.3

[akuster808]

On 01/10/2017 10:45 PM, Sona Sarmadi wrote:

Hi Armin,

I hope it is ok to upgrade libXtst, please let me know if you want to keep the 
same version and apply the patch instead of upgrade.

this is reasonable request. once its in Morty, I will pull it into krogoth.
thanks for sending the request.

- armin


  The upgrade have only following changes:

https://cgit.freedesktop.org/xorg/lib/libXtst/
Age Commit message  Author  Files   Lines
2016-10-04  libXtst 1.2.3HEADlibXtst-1.2.3masterMatthieu Herrb  1   
-1/+1
2016-09-25  Out of boundary access and endless loop in libXtst  Tobias 
Stoeckmann   1   -4/+39
2013-11-23  Remove fallback for _XEatDataWords, require libX11 1.6 for it   
Michael Joost   2   -18/+1
2013-05-31  libXtst 1.2.2libXtst-1.2.2

This does not affect master. According to Mitre this affects libXtst before 
1.2.3:

Multiple integer overflows in X.org libXtst before 1.2.3 allow remote X servers 
to trigger out-of-bounds memory access operations by leveraging the lack of 
range checks.

Cheers
//Sona


-Original Message-
From: openembedded-core-boun...@lists.openembedded.org
[mailto:openembedded-core-boun...@lists.openembedded.org] On
Behalf Of Sona Sarmadi
Sent: den 10 januari 2017 12:11
To: openembedded-core@lists.openembedded.org
Subject: [OE-core] [PATCH][krogoth] libxtst: 1.2.2 -> 1.2.3

Upgrade libxtst from 1.2.2 to 1.2.3 to address:
Out of Bounds Write Denial of Service Vulnerability, CVE-2016-7951

References:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7951
https://cgit.freedesktop.org/xorg/lib/libXtst/commit/?id=9556ad67af312
9ec4a7a4f4b54a0d59701beeae3

Signed-off-by: Sona Sarmadi 
---
  meta/recipes-graphics/xorg-lib/{libxtst_1.2.2.bb => libxtst_1.2.3.bb} | 4
++--
  1 file changed, 2 insertions(+), 2 deletions(-)  rename meta/recipes-
graphics/xorg-lib/{libxtst_1.2.2.bb => libxtst_1.2.3.bb} (78%)

diff --git a/meta/recipes-graphics/xorg-lib/libxtst_1.2.2.bb
b/meta/recipes-graphics/xorg-lib/libxtst_1.2.3.bb
similarity index 78%
rename from meta/recipes-graphics/xorg-lib/libxtst_1.2.2.bb
rename to meta/recipes-graphics/xorg-lib/libxtst_1.2.3.bb
index 1b0bcf3..31ea439 100644
--- a/meta/recipes-graphics/xorg-lib/libxtst_1.2.2.bb
+++ b/meta/recipes-graphics/xorg-lib/libxtst_1.2.3.bb
@@ -16,5 +16,5 @@ PE = "1"

  XORG_PN = "libXtst"

-SRC_URI[md5sum] = "25c6b366ac3dc7a12c5d79816ce96a59"
-SRC_URI[sha256sum] =
"ef0a7ffd577e5f1a25b1663b375679529663a1880151beaa73e9186c83
09f6d9"
+SRC_URI[md5sum] = "ef8c2c1d16a00bd95b9fdcef63b8a2ca"
+SRC_URI[sha256sum] =
"4655498a1b8e844e3d6f21f3b2c4e2b571effb5fd83199d428a6ba7ea4b
f5204"
--
1.9.1

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [oe-core][PATCH 1/1] build-compare: derive PV from SRCPV

[Joe Slater]

Currently, PV is "git" and contains no version information.

Signed-off-by: Joe Slater 
---
 .../build-compare/build-compare_git.bb |1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/build-compare/build-compare_git.bb 
b/meta/recipes-devtools/build-compare/build-compare_git.bb
index fa9c6b4..e432143 100644
--- a/meta/recipes-devtools/build-compare/build-compare_git.bb
+++ b/meta/recipes-devtools/build-compare/build-compare_git.bb
@@ -18,6 +18,7 @@ SRC_URI = "git://github.com/openSUSE/build-compare.git \
"
 
 SRCREV = "c5352c054c6ef15735da31b76d6d88620f4aff0a"
+PV = "git+${SRCPV}"
 
 S = "${WORKDIR}/git"
 
-- 
1.7.9.5

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 2/2 V2] glibc: Upgrade to 2.25 snapshot

[Khem Raj]

On Wed, Jan 18, 2017 at 5:54 AM, Burton, Ross  wrote:
>
> On 12 January 2017 at 20:20, Khem Raj  wrote:
>>
>>  .../glibc/{glibc_2.24.bb => glibc_2.25.bb} |  23 ++--
>
>
> I was wondering what the actual version was as this isn't 2.25 yet.  The
> libraries are actually libc-2.24.90.so, so I think the recipe version should
> reflect that, if only for clarity when 2.25 is actually released.

in practice it should not matter. Thats the case will all gnu tools we
have been doing this
kind of intermediate updates for binutils and gcc as well.
>
> Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH][Morty] binutils-2.27.inc: Fix alignment frags for aarch64

[Manjukumar Harthikote Matha]

> -Original Message-
> From: akuster808 [mailto:akuster...@gmail.com]
> Sent: Wednesday, January 18, 2017 8:09 AM
> To: Nathan Rossi
> Cc: openembedded-core@lists.openembedded.org; Manjukumar Harthikote Matha;
> Mike Looijmans
> Subject: Re: [OE-core] [PATCH][Morty] binutils-2.27.inc: Fix alignment frags 
> for
> aarch64
>
>
>
> On 01/18/2017 04:08 AM, Nathan Rossi wrote:
> > On 18 January 2017 at 19:37, Mike Looijmans  wrote:
> >> Could someone at least please say "yes" or "no"?
> >>
> >> I now have three projects waiting for this patch to be included in
> >> morty. If it's not going to happen, I'll have to add a bbappend to
> >> these layers to fix it.
> >>
> >> On 16-01-17 18:49, Manjukumar Harthikote Matha wrote:
> >>> Ping, this has been applied to master
> > Armin, you mentioned on IRC ~1 week ago that you had merged it to your
> > staging branch? Any updates?
> > Also I had a look and could not find the change in
> > http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akuster/morty-next?
> > Maybe I am looking in the wrong place though for your staging tree?
> I forgot to press go. Its there now.
>
Hi Armin

Thanks, appreciate it.

Thanks
Manju

> - armin
> >
> > Thanks,
> > Nathan



This email and any attachments are intended for the sole use of the named 
recipient(s) and contain(s) confidential information that may be proprietary, 
privileged or copyrighted under applicable law. If you are not the intended 
recipient, do not read, copy, or forward this email message or any attachments. 
Delete this email message and any attachments immediately.

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [Openembedded-architecture] Layer index enhancements

[Paul Eggleton]

On Wed, 18 Jan 2017 23:02:00 Paul Eggleton wrote:
> * We now pick up layer dependencies (and recommends) specified in the
> layer.conf, but only if they match the layer name - we don't handle
> collection names yet, so this won't currently work where the collection
> name doesn't match the layer name (e.g. oe-core, meta-oe...).

I was wrong about this - the collection name is collected and used in the 
dependency resolution. New layers / branches should have this information 
populated, however we haven't collected collection names for all of the 
existing layers. I have just gone in and checked meta-oe and oe-core are set 
up for master, morty, krogoth & jethro.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 1/3] image-container.bbclass: Add the "container" IMAGE_FSTYPES

[Randy Witt]

The "container" fstype does very little other than pick tar.bz2 as the
actual image type and disable installation of ROOTFS_BOOTSTRAP_INSTALL.

[YOCTO #9502]

Signed-off-by: Randy Witt 
---
 meta/classes/image-container.bbclass | 3 +++
 meta/classes/image.bbclass   | 3 +++
 meta/classes/image_types.bbclass | 1 +
 3 files changed, 7 insertions(+)
 create mode 100644 meta/classes/image-container.bbclass

diff --git a/meta/classes/image-container.bbclass 
b/meta/classes/image-container.bbclass
new file mode 100644
index 000..a10ee32
--- /dev/null
+++ b/meta/classes/image-container.bbclass
@@ -0,0 +1,3 @@
+ROOTFS_BOOTSTRAP_INSTALL = ""
+IMAGE_TYPES_MASKED += "container"
+IMAGE_TYPEDEP_container = "tar.bz2"
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index 04fd5f9..b2c2a28 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -144,6 +144,9 @@ inherit ${IMAGE_TYPE_live}
 IMAGE_TYPE_vm = '${@bb.utils.contains_any("IMAGE_FSTYPES", ["vmdk", "vdi", 
"qcow2", "hdddirect"], "image-vm", "", d)}'
 inherit ${IMAGE_TYPE_vm}
 
+IMAGE_TYPE_container = '${@bb.utils.contains("IMAGE_FSTYPES", "container", 
"image-container", "", d)}'
+inherit ${IMAGE_TYPE_container}
+
 def build_uboot(d):
 if 'u-boot' in (d.getVar('IMAGE_FSTYPES') or ''):
 return "image_types_uboot"
diff --git a/meta/classes/image_types.bbclass b/meta/classes/image_types.bbclass
index 7748dee..727a87e 100644
--- a/meta/classes/image_types.bbclass
+++ b/meta/classes/image_types.bbclass
@@ -328,6 +328,7 @@ IMAGE_TYPES = " \
 hdddirect \
 elf \
 wic wic.gz wic.bz2 wic.lzma \
+container \
 "
 
 # Compression is a special case of conversion. The old variable
-- 
2.9.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 0/3] Add initial container IMAGE_FSTYPES support

[Randy Witt]

The following changes since commit 63f899a950daf1018999455bafa7a2be8b22f164:

  bitbake: toaster: bin/toaster whitelist TOASTER_DIR (2017-01-17 13:18:47 
+)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib rewitt/contwip
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rewitt/contwip

Randy Witt (3):
  image-container.bbclass: Add the "container" IMAGE_FSTYPES
  image-container.bbclass: Error if not using linux-dummy
  selftest/containerimage.py: Add container IMAGE_FSTYPES test

 .../container-image/container-image-testpkg.bb |  8 +++
 .../container-image/container-test-image.bb|  8 +++
 meta/classes/image-container.bbclass   | 21 
 meta/classes/image.bbclass |  3 ++
 meta/classes/image_types.bbclass   |  1 +
 meta/lib/oeqa/selftest/containerimage.py   | 57 ++
 6 files changed, 98 insertions(+)
 create mode 100644 
meta-selftest/recipes-test/container-image/container-image-testpkg.bb
 create mode 100644 
meta-selftest/recipes-test/container-image/container-test-image.bb
 create mode 100644 meta/classes/image-container.bbclass
 create mode 100644 meta/lib/oeqa/selftest/containerimage.py

-- 
2.9.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 3/3] selftest/containerimage.py: Add container IMAGE_FSTYPES test

[Randy Witt]

This test checks to make sure only the files expected exist in a
container image. Currently only ROOTFS_BOOTSTRAP_INSTALL, gets added to
all images without the user specifying it.

But this test should help if a developer in the future ever silently
adds more than just ROOTFS_BOOTSTRAP_INSTALL, and that the developer can
make sure it also gets removed from a container image.

[YOCTO #9502]

Signed-off-by: Randy Witt 
---
 .../container-image/container-image-testpkg.bb |  8 +++
 .../container-image/container-test-image.bb|  8 +++
 meta/lib/oeqa/selftest/containerimage.py   | 57 ++
 3 files changed, 73 insertions(+)
 create mode 100644 
meta-selftest/recipes-test/container-image/container-image-testpkg.bb
 create mode 100644 
meta-selftest/recipes-test/container-image/container-test-image.bb
 create mode 100644 meta/lib/oeqa/selftest/containerimage.py

diff --git 
a/meta-selftest/recipes-test/container-image/container-image-testpkg.bb 
b/meta-selftest/recipes-test/container-image/container-image-testpkg.bb
new file mode 100644
index 000..42014dd
--- /dev/null
+++ b/meta-selftest/recipes-test/container-image/container-image-testpkg.bb
@@ -0,0 +1,8 @@
+LICENSE = "MIT"
+
+INHIBIT_DEFAULT_DEPS = "1"
+
+do_install_append() {
+   install -d ${D}${base_bindir}
+touch ${D}${base_bindir}/theapp
+}
diff --git a/meta-selftest/recipes-test/container-image/container-test-image.bb 
b/meta-selftest/recipes-test/container-image/container-test-image.bb
new file mode 100644
index 000..d5f939c
--- /dev/null
+++ b/meta-selftest/recipes-test/container-image/container-test-image.bb
@@ -0,0 +1,8 @@
+IMAGE_INSTALL += "container-image-testpkg"
+
+LICENSE = "MIT"
+
+IMAGE_FSTYPES = "container"
+IMAGE_LINGUAS = ""
+
+inherit core-image
diff --git a/meta/lib/oeqa/selftest/containerimage.py 
b/meta/lib/oeqa/selftest/containerimage.py
new file mode 100644
index 000..54e792a
--- /dev/null
+++ b/meta/lib/oeqa/selftest/containerimage.py
@@ -0,0 +1,57 @@
+import os
+
+from oeqa.selftest.base import oeSelfTest
+from oeqa.utils.commands import bitbake, runCmd
+
+# This test builds an image with using the "container" IMAGE_FSTYPE, and
+# ensures that then files in the image are only the ones expected.
+#
+# The only package added to the image is container_image_testpkg, which
+# contains one file. However, due to some other things not cleaning up during
+# rootfs creation, there is some kruft. Ideally bugs will be filed and the
+# kruft removed, but for now we whitelist some known set.
+#
+# Also for performance reason we're only checking the kruft when using ipk.
+# When using deb, and rpm it is a bit different and we could test all
+# of them, but this test is more to catch if other packages get added by
+# default other than what is in ROOTFS_BOOTSTRAP_INSTALL.
+#
+class ContainerImageTests(oeSelfTest):
+
+# Verify that when specifying a IMAGE_TYPEDEP_ of the form "foo.bar" that
+# the conversion type bar gets added as a dep as well
+def test_expected_files(self):
+
+expected_files = [
+'./',
+'./bin/',
+'./bin/theapp',
+'./etc/',
+'./etc/default/',
+'./etc/default/postinst',
+'./etc/ld.so.cache',
+'./etc/timestamp',
+'./etc/version',
+'./run/',
+'./var/',
+'./var/cache/',
+'./var/cache/ldconfig/',
+'./var/cache/ldconfig/aux-cache',
+'./var/cache/opkg/',
+'./var/lib/',
+'./var/lib/opkg/'
+]
+
+self.write_config('PREFERRED_PROVIDER_virtual/kernel = "linux-dummy"')
+self.append_config('MACHINE = "qemux86"')
+self.append_config('IMAGE_FSTYPES = "container"')
+self.append_config('PACKAGE_CLASSES = "package_ipk"')
+
+# Build the image of course
+bitbake('container-test-image')
+
+image = os.path.join(self.builddir, 
"tmp/deploy/images/qemux86/container-test-image-qemux86.tar.bz2")
+
+# Ensure the files in the image are what we expect
+result = runCmd("tar tf {} | sort".format(image), shell=True)
+self.assertEqual(result.output.split('\n'), expected_files)
-- 
2.9.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 2/3] image-container.bbclass: Error if not using linux-dummy

[Randy Witt]

In the typical case of a container, the user doesn't particularly care
about the kernel version used. Since using linux-dummy prevents building
a kernel in the most common case, alert the user if they choose a
container image, but don't also specify linux-dummy.

In the cases the user actually does want to build against particular
kernel headers, etc, they can override by setting
IMAGE_CONTAINER_NO_DUMMY = "1".

[YOCTO #9502]

Signed-off-by: Randy Witt 
---
 meta/classes/image-container.bbclass | 18 ++
 1 file changed, 18 insertions(+)

diff --git a/meta/classes/image-container.bbclass 
b/meta/classes/image-container.bbclass
index a10ee32..f002858 100644
--- a/meta/classes/image-container.bbclass
+++ b/meta/classes/image-container.bbclass
@@ -1,3 +1,21 @@
 ROOTFS_BOOTSTRAP_INSTALL = ""
 IMAGE_TYPES_MASKED += "container"
 IMAGE_TYPEDEP_container = "tar.bz2"
+
+python __anonymous() {
+if "container" in d.getVar("IMAGE_FSTYPES") and \
+   d.getVar("IMAGE_CONTAINER_NO_DUMMY") != "1" and \
+   "linux-dummy" not in d.getVar("PREFERRED_PROVIDER_virtual/kernel"):
+msg = '"container" is in IMAGE_FSTYPES, but ' \
+  'PREFERRED_PROVIDER_virtual/kernel is not "linux-dummy". ' \
+  'Unless a particular kernel is needed, using linux-dummy will ' \
+  'prevent a kernel from being built, which can reduce ' \
+  'build times. If you don\'t want to use "linux-dummy", set ' \
+  '"IMAGE_CONTAINER_NO_DUMMY" to "1".'
+
+# Raising skip recipe was Paul's clever idea. It causes the error to
+# only be shown for the recipes actually requested to build, rather
+# than bb.fatal which would appear for all recipes inheriting the
+# class.
+raise bb.parse.SkipRecipe(msg)
+}
-- 
2.9.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH][morty] libxtst: 1.2.2 -> 1.2.3

[akuster808]

merged to my staging.


thanks


On 01/12/2017 03:34 AM, Sona Sarmadi wrote:

On 01/10/2017 03:10 AM, Sona Sarmadi wrote:

Upgrade libxtst from 1.2.2 to 1.2.3 to address:

What else changed in this update?
- armin

Hi Armin,

I believe the only changes between 1.2.2 and 1.2.3 is one commit
" Remove fallback for _XEatDataWords, require libX11 1.6 for it" see below:

https://cgit.freedesktop.org/xorg/lib/libXtst/
Age Commit message  Author  Files   Lines
2016-10-04  libXtst 1.2.3   HEADlibXtst-1.2.3master Matthieu Herrb  1   
-1/+1
2016-09-25  Out of boundary access and endless loop in libXtst  Tobias 
Stoeckmann   1   -4/+39
2013-11-23  Remove fallback for _XEatDataWords, require libX11 1.6 for it   
Michael Joost   2   -18/+1
2013-05-31  libXtst 1.2.2libXtst-1.2.2

//Sona





--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [morty][PATCH v2] attr/ea-acl: pass --disable-gettext when USE_NLS=no

[akuster808]

On 01/17/2017 09:26 AM, Denys Dmytriyenko wrote:

Ping

in staging

On Tue, Jan 10, 2017 at 07:21:28PM -0500, Denys Dmytriyenko wrote:

From: Denys Dmytriyenko 

Fixes following error in configure:
   FATAL ERROR: msgfmt does not seem to be installed.
   attr cannot be built without a working gettext installation.

Signed-off-by: Denys Dmytriyenko 
Signed-off-by: Ross Burton 

(From OE-Core rev: d044fad8a0ac5d57deb88b25106f3a39cb7c1636)

Signed-off-by: Denys Dmytriyenko 
---
v2 - morty still requires expand option to d.getVar()

  meta/recipes-support/attr/ea-acl.inc | 1 +
  1 file changed, 1 insertion(+)

diff --git a/meta/recipes-support/attr/ea-acl.inc 
b/meta/recipes-support/attr/ea-acl.inc
index 370e16f..4d6ad20 100644
--- a/meta/recipes-support/attr/ea-acl.inc
+++ b/meta/recipes-support/attr/ea-acl.inc
@@ -10,6 +10,7 @@ inherit autotools-brokensep gettext
  EXTRA_AUTORECONF += "--exclude=autoheader"
  EXTRA_OECONF = "INSTALL_USER=root INSTALL_GROUP=root"
  EXTRA_OECONF_append_class-native = " --enable-gettext=no"
+EXTRA_OECONF_append_class-target = "${@['', ' --disable-gettext 
'][(d.getVar('USE_NLS', True) == 'no')]}"
  
  EXTRA_OEMAKE = "PKG_LIB_DIR=${base_libdir} PKG_DEVLIB_DIR=${libdir}"
  
--

2.7.4

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [morty][PATCH] linux-dtb: strip DTB extension properly in postinst/postrm

[akuster808]

On 01/17/2017 09:26 AM, Denys Dmytriyenko wrote:

Ping

in staging
- armin


On Tue, Jan 10, 2017 at 06:11:39PM -0500, Denys Dmytriyenko wrote:

From: Denys Dmytriyenko 

The use of awk -F "." in do_install/do_deploy to strip filename extension
was deprecated long time ago in 72980d5bb465f0640ed451d1ebb9c5d2a210ad0c.

Make a similar change in postinst/postrm to properly use basename command.

Otherwise DTB files that contain dots in the name result in broken symlinks
that point to non-existent truncated files.

Signed-off-by: Denys Dmytriyenko 
Signed-off-by: Ross Burton 

(From OE-Core rev: 40c2addf0f0ee16b1c1334cf00f1490ffeaac475)

Signed-off-by: Denys Dmytriyenko 
---
  meta/recipes-kernel/linux/linux-dtb.inc | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-dtb.inc 
b/meta/recipes-kernel/linux/linux-dtb.inc
index 8528d64..2f378a1 100644
--- a/meta/recipes-kernel/linux/linux-dtb.inc
+++ b/meta/recipes-kernel/linux/linux-dtb.inc
@@ -68,7 +68,7 @@ pkg_postinst_kernel-devicetree () {
for type in ${KERNEL_IMAGETYPE_FOR_MAKE}; do
symlink_name=${type}"-"${KERNEL_IMAGE_SYMLINK_NAME}
DTB_EXT=${DTB##*.}
-   DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print 
$1}'`
+   DTB_BASE_NAME=`basename ${DTB} ."${DTB_EXT}"`
DTB_SYMLINK_NAME=`echo ${symlink_name} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
update-alternatives --install 
/${KERNEL_IMAGEDEST}/${DTB_BASE_NAME}.${DTB_EXT} ${DTB_BASE_NAME}.${DTB_EXT} 
/boot/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT} ${KERNEL_PRIORITY} || true
done
@@ -81,7 +81,7 @@ pkg_postrm_kernel-devicetree () {
for type in ${KERNEL_IMAGETYPE_FOR_MAKE}; do
symlink_name=${type}"-"${KERNEL_IMAGE_SYMLINK_NAME}
DTB_EXT=${DTB##*.}
-   DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print 
$1}'`
+   DTB_BASE_NAME=`basename ${DTB} ."${DTB_EXT}"`
DTB_SYMLINK_NAME=`echo ${symlink_name} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
update-alternatives --remove 
${DTB_BASE_NAME}.${DTB_EXT} /boot/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT} 
${KERNEL_PRIORITY} || true
done
--
2.7.4

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH][Morty] binutils-2.27.inc: Fix alignment frags for aarch64

[akuster808]

On 01/18/2017 04:08 AM, Nathan Rossi wrote:

On 18 January 2017 at 19:37, Mike Looijmans  wrote:

Could someone at least please say "yes" or "no"?

I now have three projects waiting for this patch to be included in morty. If
it's not going to happen, I'll have to add a bbappend to these layers to fix
it.

On 16-01-17 18:49, Manjukumar Harthikote Matha wrote:

Ping, this has been applied to master

Armin, you mentioned on IRC ~1 week ago that you had merged it to your
staging branch? Any updates?
Also I had a look and could not find the change in
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akuster/morty-next?
Maybe I am looking in the wrong place though for your staging tree?

I forgot to press go. Its there now.

- armin


Thanks,
Nathan


--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [yocto] [Openembedded-architecture] Patchwork and incoming patch testing

[Jose Lamego]

On 01/18/2017 08:52 AM, Leonardo Sandoval wrote:
> + Jose Lamego
> 
> 
> Jose is doing recent work on the patchwork UI, perhaps there are already
> bugs for the items you are asking.
> 
> 
> On 01/18/2017 02:40 AM, Jussi Kukkonen wrote:
>> This looks great, thanks.
>>
>> On 17 January 2017 at 20:05, Paul Eggleton
>> >
>> wrote:
>>
>> In any event we are now finally in the
>> position where our patchwork instance can be relied upon to
>> collect emails,
>> and the UI is much improved. This should give us a bit more
>> visibility into
>> where patches are at in the process, although we are still working
>> on a few
>> places where patch series status needs to be updated (e.g. when a
>> patch goes
>> into testing).
>>
>>
>> What's the plan for these status updates -- is the idea that you go to
>> patchwork UI to see the state of a specific patch set?
>> Or maybe a reply to either patch sender or even the ML?
>>
There is a request to enable email notifications to submitter for patch
status changes in the future:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7684

The idea is that users should have the option to use what they prefer:
either the email notifications, or the patchwork web interface.

>> On top of patchwork we have built a simple smoke-testing framework
>> called
>> "patchtest" [5] along with a suite of corresponding tests for OE
>> [6]. These
>> tests are fairly simplistic at this point but check the basics
>> such as whether
>> a patch has been properly signed off, etc. We should soon start
>> seeing replies
>> sent to the mailing list and to submitters with results if there
>> are any
>> failures, saving us from noticing and pointing out some of the
>> more obvious
>> classes of mistakes.
>>
>>
>>  Is there a reason for patchwork only showing "success" or "failure"
>> in the web ui, instead of linking to test results at least in in the
>> failure case?
> 
> Jussi, that is a good idea. Right now we need to click into the series,
> then into the patches and then one can see the patch test results,
> obviously, not the best way.
> 
>>
>>
>>
>>  - Jussi
>>
>>
-- 
Jose Lamego | OTC Embedded Platforms & Tools | GDC



signature.asc
Description: OpenPGP digital signature
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [yocto] [Openembedded-architecture] Patchwork and incoming patch testing

[Leonardo Sandoval]

+ Jose Lamego


Jose is doing recent work on the patchwork UI, perhaps there are already 
bugs for the items you are asking.



On 01/18/2017 02:40 AM, Jussi Kukkonen wrote:

This looks great, thanks.

On 17 January 2017 at 20:05, Paul Eggleton 
> 
wrote:


In any event we are now finally in the
position where our patchwork instance can be relied upon to
collect emails,
and the UI is much improved. This should give us a bit more
visibility into
where patches are at in the process, although we are still working
on a few
places where patch series status needs to be updated (e.g. when a
patch goes
into testing).


What's the plan for these status updates -- is the idea that you go to 
patchwork UI to see the state of a specific patch set?

Or maybe a reply to either patch sender or even the ML?

On top of patchwork we have built a simple smoke-testing framework
called
"patchtest" [5] along with a suite of corresponding tests for OE
[6]. These
tests are fairly simplistic at this point but check the basics
such as whether
a patch has been properly signed off, etc. We should soon start
seeing replies
sent to the mailing list and to submitters with results if there
are any
failures, saving us from noticing and pointing out some of the
more obvious
classes of mistakes.


 Is there a reason for patchwork only showing "success" or "failure" 
in the web ui, instead of linking to test results at least in in the 
failure case?


Jussi, that is a good idea. Right now we need to click into the series, 
then into the patches and then one can see the patch test results, 
obviously, not the best way.






 - Jussi





-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 03/14] linux-yocto-rt/4.9: add -rt specific patches

[Bruce Ashfield]

The 4.9-rt kernel has been released, and this commit integrates
the 286 patches in that series.

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb   | 4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.9.bb  | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
index 2f1c6523147c..d505f924bdc7 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
@@ -11,8 +11,8 @@ python () {
 raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
-SRCREV_meta ?= "c56f2da94e4773ea25eebfd14200164ef21730a3"
+SRCREV_machine ?= "1eb33152d655c73193cec17c4de04499e52b2faa"
+SRCREV_meta ?= "7ca94971d258304e3e3068f7b7ebe425fe5a77d1"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.9.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.9;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
index 62df631f3539..bf23d3efe29f 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
@@ -10,7 +10,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
-SRCREV_meta ?= "c56f2da94e4773ea25eebfd14200164ef21730a3"
+SRCREV_meta ?= "7ca94971d258304e3e3068f7b7ebe425fe5a77d1"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.9.bb
index d84400a323eb..ded3c6c00e64 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.9.bb
@@ -19,7 +19,7 @@ SRCREV_machine_qemux86 ?= 
"617635e43afee1aaf98a8f8300596f7a112513c0"
 SRCREV_machine_qemux86-64 ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
 SRCREV_machine_qemumips64 ?= "3183d61d4d00d8b7faf10d11b3da8cf3db432e6f"
 SRCREV_machine ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
-SRCREV_meta ?= "c56f2da94e4773ea25eebfd14200164ef21730a3"
+SRCREV_meta ?= "7ca94971d258304e3e3068f7b7ebe425fe5a77d1"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.9.git;name=machine;branch=${KBRANCH}; 
\

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.9;destsuffix=${KMETA}"
-- 
2.5.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 09/14] linux-yocto/4.4: update to v4.4.41

[Bruce Ashfield]

Integrating the korg -stable release. Changes are as follows:

   cdd86b972265 Linux 4.4.41
   9f11a0ab6a96 net: mvpp2: fix dma unmapping of TX buffers for fragments
   d85727365859 sg_write()/bsg_write() is not fit to be called under KERNEL_DS
   7fb5a936457d kconfig/nconf: Fix hang when editing symbol with a long prompt
   e321f384d8a5 target/user: Fix use-after-free of tcmu_cmds if they are expired
   e5de1c724c06 powerpc: Convert cmp to cmpd in idle enter sequence
   cadaba838f1b powerpc/ps3: Fix system hang with GCC 5 builds
   8a2bcaae1bc7 nfs_write_end(): fix handling of short copies
   b66e3126569e libceph: verify authorize reply on connect
   edfe6a79f905 PCI: Check for PME in targeted sleep state
   8db00756afbd Input: drv260x - fix input device's parent assignment
   44685f03dd56 media: solo6x10: fix lockup by avoiding delayed register write
   952a9f5af9f8 IB/cma: Fix a race condition in iboe_addr_get_sgid()
   b7f73ada92a3 IB/multicast: Check ib_find_pkey() return value
   7b1369215616 IPoIB: Avoid reading an uninitialized member variable
   0de381ca35b5 IB/mad: Fix an array index check
   e945df4c6bc2 fgraph: Handle a case where a tracer ignores set_graph_notrace
   88e41441ccd4 platform/x86: asus-nb-wmi.c: Add X45U quirk
   2ef502e860f1 ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from 
using short jumps to it
   19aa9c14989e kvm: nVMX: Allow L1 to intercept software exceptions (#BP and 
#OF)
   129e4323df37 KVM: PPC: Book3S HV: Don't lose hardware R/C bit updates in 
H_PROTECT
   ddf5718adfb8 KVM: PPC: Book3S HV: Save/restore XER in checkpointed register 
state
   1c8841c9b7d2 md/raid5: limit request size according to implementation limits
   d78006d2345f sc16is7xx: Drop bogus use of IRQF_ONESHOT
   b988320dab53 s390/vmlogrdr: fix IUCV buffer allocation
   656c9abd574b firmware: fix usermode helper fallback loading
   429a533a3d9a ARC: mm: arc700: Don't assume 2 colours for aliasing VIPT dcache
   dbb67e1d585d scsi: avoid a permanent stop of the scsi device's request queue
   565ae61d8995 scsi: zfcp: fix rport unblock race with LUN recovery
   3b3739dfa69c scsi: zfcp: do not trace pure benign residual HBA responses at 
default level
   1cc0f9488b91 scsi: zfcp: fix use-after-"free" in FC ingress path after TMF
   bccd78746f88 scsi: megaraid_sas: Do not set MPI2_TYPE_CUDA for JBOD FP path 
for FW which does not support JBOD sequence map
   49ea06561154 scsi: megaraid_sas: For SRIOV enabled firmware, ensure VF 
driver waits for 30secs before reset
   edf1169bbbaa vt: fix Scroll Lock LED trigger name
   f4f02a856a92 block: protect iterate_bdevs() against concurrent close
   abb78811e242 mei: request async autosuspend at the end of enumeration
   1f9c91a37542 drivers/gpu/drm/ast: Fix infinite loop if read fails
   970dc8cdec9c drm/gma500: Add compat ioctl
   0e0b70f581fc drm/radeon: add additional pci revision to dpm workaround
   62a272498dbe drm/radeon: Hide the HW cursor while it's out of bounds
   deac395e0ba8 drm/radeon: Also call cursor_move_locked when the cursor size 
changes
   cb8d63d885e9 drm/nouveau/i2c/gk110b,gm10x: use the correct implementation
   adea4a7b0f2b drm/nouveau/fifo/gf100-: protect channel preempt with subdev 
mutex
   d32d4b3d7c9f drm/nouveau/ltc: protect clearing of comptags with mutex
   3a2990e67b05 drm/nouveau/bios: require checksum to match for fast acpi 
shadow method
   a163451c80b0 drm/nouveau/kms: lvds panel strap moved again on maxwell
   69e236e70ead ACPI / video: Add force_native quirk for HP Pavilion dv6
   2c2375e40d28 ACPI / video: Add force_native quirk for Dell XPS 17 L702X
   01b6089b5622 staging: comedi: ni_mio_common: fix E series ni_ai_insn_read() 
data
   5283a7bedbcb staging: comedi: ni_mio_common: fix M Series ni_ai_insn_read() 
data mask
   e692edec93c1 thermal: hwmon: Properly report critical temperature in sysfs
   9d9541d44a26 clk: bcm2835: Avoid overwriting the div info when disabling a 
pll_div clk
   e01b04be3eb0 timekeeping_Force_unsigned_clocksource_to_nanoseconds_conversion
   96ea1b9ea099 regulator: stw481x-vmmc: fix ages old enable error
   842ec27cd3f2 mmc: sdhci: Fix recovery from tuning timeout
   dae7cb414834 ath9k: Really fix LED polarity for some Mini PCI AR9220 MB92 
cards.
   b63929e8e130 cfg80211/mac80211: fix BSS leaks when abandoning assoc attempts
   05f4183ab5a4 rtlwifi: Fix enter/exit power_save
   f5d90f434c9a ssb: Fix error routine when fallback SPROM fails
   a3edc7b2e537 Linux 4.4.40
   7a2b4ee54b3f ppp: defer netns reference release for ppp channel
   37de955c11b5 driver core: fix race between creating/querying glue dir and 
its cleanup
   f85a337b4066 xfs: set AGI buffer type in xlog_recover_clear_agi_bucket
   fdb17ddd0a49 arm/xen: Use alloc_percpu rather than __alloc_percpu
   9397e79c4b2d xen/gntdev: Use VM_MIXEDMAP instead of VM_IO to avoid NUMA 
balancing
   00a0de085d60 tpm xen: Remove bogus tpm_chip_unregister
   f93777c91544 kernel/debug/debug_core.c: more properly delay for secondary 
CPUs
   

[OE-core] [PATCH 13/14] kern-tools: kconf_check: flag CONFIG options with invalid spaces

[Bruce Ashfield]

Options with spacs around = signs will be droped/ignored by the
kernel.

The audit phase can detect this and warn the user:

% kconf_check --report -o .kernel-meta/cfg/ \
  linux-qemux86-standard-build/.config `pwd` $cfgs

 [errors (3): .kernel-meta/cfg/fragment_errors.txt
   There are errors withing the config fragments.

% cat .kernel-meta/cfg/fragment_errors.txt
   Warning: Ignoring "CONFIG_PARAVIRTT_CLOCK =y" -- spaces around equals 
are invalid
   Warning: Ignoring "CONFIG_PARAVIRTTT_CLOCK = y" -- spaces around equals 
are invalid
   Warning: Ignoring "CONFIG_PARAVIR_CLOCK= y" -- spaces around equals 
are invalid

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb 
b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index 030c2d42d873..edf5cd93c0b4 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = 
"file://git/tools/kgit;beginline=5;endline=9;md5=a6c2fa8aef1b
 
 DEPENDS = "git-native"
 
-SRCREV = "be79004cb2535e79271822b3d74eda5ba12233d2"
+SRCREV = "bf2942f7559d114e96f7c7f1287bf7e5120632a"
 PR = "r12"
 PV = "0.2+git${SRCPV}"
 
-- 
2.5.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 11/14] kern-tools: scc: Fix process_file error check

[Bruce Ashfield]

Commit 626ceac135fa66277c2fa53197be33cc9d4d7614 broke the error
check in process_file by adding in three lines that stomp on $? which
print the output file when verbose is set.

Move output file on verbose print to an elif after the error check.

Signed-off-by: George McCollister 

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb 
b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index 8af01559dfb1..030c2d42d873 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = 
"file://git/tools/kgit;beginline=5;endline=9;md5=a6c2fa8aef1b
 
 DEPENDS = "git-native"
 
-SRCREV = "85564e69555b713c2759d58ec5ade54424d051d8"
+SRCREV = "be79004cb2535e79271822b3d74eda5ba12233d2"
 PR = "r12"
 PV = "0.2+git${SRCPV}"
 
-- 
2.5.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 14/14] linux-yocto/4.9: merge 4.9.3 and ethernet config changes

[Bruce Ashfield]

Merging the following meta-data changes:

 03a2d3f7f999 Add support for NVMe storage devices
 27a79fa51d44 Modularize PCI/PCIe ethernet drivers
 53d2a7d9c9f8 Modularize USB network drivers

And the 4.9.3 -stable update, which has the following shortlog:

   584fd7872c1b Linux 4.9.3
   3999c535da7a usb: gadget: composite: always set ep->mult to a sensible value
   7ff469ceba26 Revert "usb: gadget: composite: always set ep->mult to a 
sensible value"
   ec3d5c521af8 Revert "rtlwifi: Fix enter/exit power_save"
   cf365b117388 tick/broadcast: Prevent NULL pointer dereference
   34db201f0de7 clocksource/dummy_timer: Move hotplug callback after the real 
timers
   1b9c2556809a xfs: fix max_retries _show and _store functions
   91192ae41e6f xfs: fix crash and data corruption due to removal of busy COW 
extents
   b96e4e87d2b0 xfs: use the actual AG length when reserving blocks
   d9c7c9fa600a xfs: fix double-cleanup when CUI recovery fails
   aa38f370b25a xfs: use GPF_NOFS when allocating btree cursors
   3c382dda47e4 xfs: ignore leaf attr ichdr.count in verifier during log replay
   c00203386d50 xfs: don't cap maximum dedupe request length
   f8b20705a383 xfs: don't allow di_size with high bit set
   12815dd15c48 xfs: error out if trying to add attrs and anextents > 0
   cd4bf1d416ef xfs: don't crash if reading a directory results in an 
unexpected hole
   b88398de1833 xfs: complain if we don't get nextents bmap records
   4bb31bccea38 xfs: check for bogus values in btree block headers
   b85f32481d93 xfs: forbid AG btrees with level == 0
   4081d4a79a95 xfs: handle cow fork in xfs_bmap_trace_exlist
   a585e1c4ec93 xfs: pass state not whichfork to trace_xfs_extlist
   bdbfd4ee6bc7 xfs: Move AGI buffer type setting to xfs_read_agi
   06ac11df915d xfs: pass post-eof speculative prealloc blocks to bmapi
   553937d3cce8 xfs: use new extent lookup helpers xfs_file_iomap_begin_delay
   3d6e3b12bb4e xfs: clean up cow fork reservation and tag inodes correctly
   4a323331d8c9 xfs: use new extent lookup helpers in __xfs_reflink_reserve_cow
   cf168f2ff8ba xfs: track preallocation separately in 
xfs_bmapi_reserve_delalloc()
   cf4fb510473b xfs: remove prev argument to xfs_bmapi_reserve_delalloc
   390325766033 xfs: always succeed when deduping zero bytes
   2b7dae91a134 xfs: factor rmap btree size into the indlen calculations
   49dc19915d3b xfs: new inode extent list lookup helpers
   b49ef758f600 xfs: fix unbalanced inode reclaim flush locking
   63fa793e757d xfs: check minimum block size for CRC filesystems
   f380ee72a7a4 xfs: provide helper for counting extents from if_bytes
   3978c5bb0043 xfs: don't BUG() on mixed direct and mapped I/O
   2f092422e1ce xfs: don't skip cow forks w/ delalloc blocks in cowblocks scan
   a11f90ca5f30 xfs: check return value of _trans_reserve_quota_nblks
   ae8b6cb40cb2 xfs: don't call xfs_sb_quota_from_disk twice
   56d22b912542 tpm_tis: Check return values from get_burstcount.
   4ffac6f06dfa drm/i915/gen9: fix the WM memory bandwidth WA for Y tiling cases
   f482823e99f0 drm/i915/gen9: unconditionally apply the memory bandwidth WA
   2bdb638de2fc drm/i915: disable PSR by default on HSW/BDW
   9ab30a6529b5 drm/radeon: Always store CRTC relative radeon_crtc->cursor_x/y 
values
   5417f59cb996 s390/pci: fix dma address calculation in map_sg
   dae9151a88f7 s390/topology: always use s390 specific 
sched_domain_topology_level
   b3539f813578 powerpc/pci/rpadlpar: Fix device reference leaks
   1aaa777ec009 PCI: Enable access to non-standard VPD for Chelsio devices 
(cxgb3)
   c444cc34534b PCI: Support INTx masking on ConnectX-4 with firmware x.14.1100+
   e2822904ace5 PCI: Convert Mellanox broken INTx quirks to be for listed 
devices only
   890661544739 PCI: Convert broken INTx masking quirks from HEADER to FINAL
   04b97a6be2ed PCI: Add Mellanox device IDs
   090cce6f6f88 PCI: rockchip: Correct the use of FTS mask
   6e4bcf8539af PCI: rockchip: Fix negotiated lanes calculation
   257349bedca3 staging: media: davinci_vpfe: unlock on error in vpfe_reqbufs()
   a299abd23081 f2fs: hide a maybe-uninitialized warning
   725ba1a3ebc4 f2fs: remove percpu_count due to performance regression
   5cc85ef4ffe6 md: fix refcount problem on mddev when stopping array.
   60a931c20d1a md: MD_RECOVERY_NEEDED is set for mddev->recovery
   d33a490770e5 crypto: arm64/aes-ce - fix for big endian
   eb64cbc5665d crypto: arm64/aes-xts-ce: fix for big endian
   c3edfe038a75 crypto: arm64/sha1-ce - fix for big endian
   39b7e1c2fdda crypto: arm64/aes-neon - fix for big endian
   d018dc9540f7 crypto: arm64/aes-ccm-ce: fix for big endian
   e6ce55f7be90 crypto: arm/aes-ce - fix for big endian
   a7c9666735f4 crypto: arm64/ghash-ce - fix for big endian
   cdeaed7dda7b crypto: arm64/sha2-ce - fix for big endian
   a05aa258b237 s390/crypto: unlock on error in prng_tdes_read()
   5d7d362abc40 mm, compaction: fix NR_ISOLATED_* stats for pfn based migration
   dc1b6d0aed97 mm: khugepaged: fix radix tree node leak in shmem 

[OE-core] [PATCH 12/14] linux-yocto/4.8: update to -rt10

[Bruce Ashfield]

Paul Gortmaker has updated 4.8 to the latest -rt release. This
integrates those changes to standard/preempt-rt/*. As usual the
branches are kept fast forward, and a clean copy of the patches
can be found on standard/preempt-rt/rebase.

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb   | 4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.8.bb  | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb
index 702d41bac15f..c0ff503676ad 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb
@@ -11,8 +11,8 @@ python () {
 raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "8fddffd5588e14ad3bb5297dbc5b9c4a1047238c"
-SRCREV_meta ?= "7b320e0a54be4b2d9bbaf4eb6165532e3954ad3e"
+SRCREV_machine ?= "9c4f52cb2bafd9657c51cef2166db2b73a95aaa9"
+SRCREV_meta ?= "3edb4de355873d32da9307a011adea2542bd05a7"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.8.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.8;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb
index 89b601696728..11b0dc9ea4b0 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb
@@ -10,7 +10,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "b62f29ac5c15d6333a13811db030d704b35ace8f"
-SRCREV_meta ?= "7b320e0a54be4b2d9bbaf4eb6165532e3954ad3e"
+SRCREV_meta ?= "3edb4de355873d32da9307a011adea2542bd05a7"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.8.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.8.bb
index a81128a0b950..0ebd071463de 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.8.bb
@@ -19,7 +19,7 @@ SRCREV_machine_qemux86 ?= 
"9bcb4ea3fa107f1a8790c8c3408eb250e8d1d66e"
 SRCREV_machine_qemux86-64 ?= "9bcb4ea3fa107f1a8790c8c3408eb250e8d1d66e"
 SRCREV_machine_qemumips64 ?= "b90b544d7a5b004b635cf337b29e15294cb17553"
 SRCREV_machine ?= "9bcb4ea3fa107f1a8790c8c3408eb250e8d1d66e"
-SRCREV_meta ?= "7b320e0a54be4b2d9bbaf4eb6165532e3954ad3e"
+SRCREV_meta ?= "3edb4de355873d32da9307a011adea2542bd05a7"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.8.git;name=machine;branch=${KBRANCH}; 
\

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.8;destsuffix=${KMETA}"
-- 
2.5.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 10/14] linux-yocto/4.1: update to v4.1.37

[Bruce Ashfield]

Integrating the -stable release. Changes are as follows:

   35327468a79d Linux 4.1.37
   c27edfb64bbf scsi: megaraid_sas: fix macro MEGASAS_IS_LOGICAL to avoid 
regression
   016d02981cce tipc: check minimum bearer MTU
   efcf38bd4020 net: ping: check minimum size on ICMP header length
   e29fdf045048 packet: fix race condition in packet_set_ring
   fab96d54 net: add recursion limit to GRO
   7abf32087c1d Bluetooth: Fix potential NULL dereference in RFCOMM bind 
callback
   74cd81c810b9 ptrace: being capable wrt a process requires mapped uids/gids
   8165fc3eb28c scsi: arcmsr: Buffer overflow in arcmsr_iop_message_xfer()
   1171afc4a34e mnt: Add a per mount namespace limit on the number of mounts
   62fa696b7b43 posix_acl: Clear SGID bit when setting file permissions
   de42b9559d0c fs: Avoid premature clearing of capabilities
   cb8e1eef351b fs: Give dentry to inode_change_ok() instead of inode
   2ee3ceeccd34 nfsd: Disable NFSv2 timestamp workaround for NFSv3+
   820bc4582ab9 fuse: Propagate dentry down to inode_change_ok()
   89bc54c54027 xfs: Propagate dentry down to inode_change_ok()
   1b364dc9edba xattr: Option to disable meta-data block cache
   9a66bc6ee0f9 tcp: fix use after free in tcp_xmit_retransmit_queue()
   ebdb88b8e465 x86/kexec: add -fno-PIE
   672612a21845 scripts/has-stack-protector: add -fno-PIE
   e06ded86d961 x86/init: Fix cr4_init_shadow() on CR4-less machines
   eec746939372 ARM: 8617/1: dma: fix dma_max_pfn()
   58024f829d0b mm,ksm: fix endless looping in allocating memory when ksm enable
   d427d645ccf9 can: dev: fix deadlock reported after bus-off
   791a92897274 cpuset: handle race between CPU hotplug and cpuset_hotplug_work
   6b82b0601ac2 mtd: nand: davinci: Reinitialize the HW ECC engine in 4bit hwctl
   e537a0977f3e drm/msm: fix use of copy_from_user() while holding spinlock
   b56eb9cdc5f1 bus: arm-ccn: Fix PMU handling of MN
   7298a8bf4c63 bus: arm-ccn: Provide required event arguments

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.1.bb  | 20 ++--
 3 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb
index 70658832a92e..dc9a8dcd3246 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb
@@ -11,13 +11,13 @@ python () {
 raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "f3ffbf4880a5103504a4e11c9427b0bdbf222939"
-SRCREV_meta ?= "44719fa8f73fd7c444044ad3c04f5fc66f57b993"
+SRCREV_machine ?= "109fa96e6ae89b0585e78186b374b57b9f37fcbb"
+SRCREV_meta ?= "4de9b8f96c8dca0c55a496792a2ad4d2776e6657"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.1.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.1;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "4.1.36"
+LINUX_VERSION ?= "4.1.37"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb
index 80be144e4ee4..ed5a70b43c8d 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb
@@ -4,13 +4,13 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "4.1.36"
+LINUX_VERSION ?= "4.1.37"
 
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "fec49247816d7045aa8abe0047bcd4737af9a853"
-SRCREV_meta ?= "44719fa8f73fd7c444044ad3c04f5fc66f57b993"
+SRCREV_machine ?= "61d2bedf25deac15c19413ee1b057067657d97d3"
+SRCREV_meta ?= "4de9b8f96c8dca0c55a496792a2ad4d2776e6657"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.1.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.1.bb
index b55487782776..19f321721c35 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.1.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.1.bb
@@ -11,20 +11,20 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "c8ab8bf2bdff3b355710065725f4e272bf0a5a5d"
-SRCREV_machine_qemuarm64 ?= "fec49247816d7045aa8abe0047bcd4737af9a853"
-SRCREV_machine_qemumips ?= "475a0182d9e940351a3fecaecb31e55effad45ad"
-SRCREV_machine_qemuppc ?= "88a3e5a3a8f693d25b09b64cd2be5df783933f74"
-SRCREV_machine_qemux86 ?= "fec49247816d7045aa8abe0047bcd4737af9a853"
-SRCREV_machine_qemux86-64 ?= "fec49247816d7045aa8abe0047bcd4737af9a853"
-SRCREV_machine_qemumips64 ?= "9ffd7155a07e7cfed2229b3a78d2278f3b56f13d"
-SRCREV_machine ?= "fec49247816d7045aa8abe0047bcd4737af9a853"
-SRCREV_meta ?= 

[OE-core] [PATCH 08/14] linux-yocto/4.8: -stable update to v4.8.17

[Bruce Ashfield]

Updating to the korg 4.8.17 -stable release. Changes are as follows:

   3d8f8d06abb3 Linux 4.8.17
   adf363fd5ab9 drm/i915: skip the first 4k of stolen memory on everything >= 
gen8
   000e612673da drm/i915: Initialize dev_priv->atomic_cdclk_freq at init time
   22aba475d97b drm/i915: Fix cdclk vs. dev_cdclk mess when not recomputing 
things
   294bb3402c76 drm/i915/dsi: Do not clear DPOUNIT_CLOCK_GATE_DISABLE from 
vlv_init_display_clock_gating
   6a412ff3df87 drm/i915/dsi: Fix chv_exec_gpio disabling the GPIOs it is 
setting
   4803ec2a74c4 net: mvpp2: fix dma unmapping of TX buffers for fragments
   48f26edb689c sg_write()/bsg_write() is not fit to be called under KERNEL_DS
   d787c6b32c3f kconfig/nconf: Fix hang when editing symbol with a long prompt
   e141d1a21e31 target/user: Fix use-after-free of tcmu_cmds if they are expired
   29f3d1127c4b libnvdimm, pfn: fix align attribute
   3a4e4281b5cd powerpc/ps3: Fix system hang with GCC 5 builds
   e451d674bac5 powerpc/64e: Convert cmpi to cmpwi in head_64.S
   0349fbebd984 SUNRPC: fix refcounting problems with auth_gss messages.
   c513ade4ca56 pNFS: Fix a deadlock between read resends and layoutreturn
   abb2903f1ac2 pNFS: Clear NFS_LAYOUT_RETURN_REQUESTED when invalidating the 
layout stateid
   f061c76c1d56 pNFS: Don't clear the layout stateid if a layout return is 
outstanding
   7de1b81c27fd pNFS: On error, do not send LAYOUTGET until the LAYOUTRETURN 
has completed
   8f5ff877bf19 nfs_write_end(): fix handling of short copies
   1678adac85da libceph: verify authorize reply on connect
   1f93d1a77b17 PCI: Check for PME in targeted sleep state
   c75bc2bde102 i40iw: Use correct src address in memcpy to rdma stats counters
   7d0a6cf3e8c9 Input: drv260x - fix input device's parent assignment
   b7843712cbd2 v4l: tvp5150: Add missing break in set control handler
   4963b1910090 media: solo6x10: fix lockup by avoiding delayed register write
   88bfde25e60f s5p-mfc: fix failure path of s5p_mfc_alloc_memdev()
   c3fe33d185e0 mn88473: fix chip id check on probe
   84b2f664409c mn88472: fix chip id check on probe
   15d1d226eab4 IB/cma: Fix a race condition in iboe_addr_get_sgid()
   7b3721aff59b IB/rxe: Fix a memory leak in rxe_qp_cleanup()
   2a0aa77a54fb IB/multicast: Check ib_find_pkey() return value
   37d4adba02d3 IPoIB: Avoid reading an uninitialized member variable
   f079fc11f28e IB/mad: Fix an array index check
   e661b5d4b94f fgraph: Handle a case where a tracer ignores set_graph_notrace
   b2758da04d73 platform/x86: asus-nb-wmi.c: Add X45U quirk
   f61152e3bbf0 ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from 
using short jumps to it
   8569aadeed3f vsock/virtio: fix src/dst cid format
   576ea9e5e92e fsnotify: Fix possible use-after-free in inode iteration on 
umount
   43983ce75e61 kvm: nVMX: Allow L1 to intercept software exceptions (#BP and 
#OF)
   9a5cf8c4b112 KVM: PPC: Book3S HV: Don't lose hardware R/C bit updates in 
H_PROTECT
   b751eb6e9d99 KVM: PPC: Book3S HV: Save/restore XER in checkpointed register 
state
   0773e9248ae3 scsi: aacraid: remove wildcard for series 9 controllers
   b202064f0b3f md/raid5: limit request size according to implementation limits
   47090341ec97 sc16is7xx: Drop bogus use of IRQF_ONESHOT
   c33e1abd2e31 arm64: KVM: pmu: Reset PMSELR_EL0.SEL to a sane value before 
entering the guest
   d3d61bb37afb s390/kexec: use node 0 when re-adding crash kernel memory
   9652b62af49d s390/vmlogrdr: fix IUCV buffer allocation
   f356ab038e78 firmware: fix usermode helper fallback loading
   5c98bf834d6f ARC: mm: arc700: Don't assume 2 colours for aliasing VIPT dcache
   cc328ce59a4a scsi: avoid a permanent stop of the scsi device's request queue
   6d675dffd425 scsi: zfcp: fix rport unblock race with LUN recovery
   057fe03d627e scsi: zfcp: do not trace pure benign residual HBA responses at 
default level
   5cebfea8080c scsi: zfcp: fix use-after-"free" in FC ingress path after TMF
   de8a06c673ac iscsi-target: Return error if unable to add network portal
   9c3928be0dba scsi: megaraid_sas: Do not set MPI2_TYPE_CUDA for JBOD FP path 
for FW which does not support JBOD sequence map
   dbd4e6c60b4f scsi: megaraid_sas: For SRIOV enabled firmware, ensure VF 
driver waits for 30secs before reset
   3863ab6d710d stm class: Fix device leak in open error path
   698ac693dbb4 vt: fix Scroll Lock LED trigger name
   6d8bb567102c block: protect iterate_bdevs() against concurrent close
   2695afd5e9c2 mei: me: add lewisburg device ids
   7be0a5f39d64 mei: request async autosuspend at the end of enumeration
   dfc3c8a0fa1b drivers/gpu/drm/ast: Fix infinite loop if read fails
   0f95e4a58ecd drm/amdgpu: fix init save/restore list in gfx_v8.0
   8bfa4f5e6395 drm/gma500: Add compat ioctl
   10b598df92d9 drm/radeon/si: load the proper firmware on 0x87 oland boards
   cdb7ecff drm/radeon: add additional pci revision to dpm workaround
   1f884ec818a6 drm/radeon: Hide the HW cursor while it's out of bounds
   6fb94229b2f6 

[OE-core] [PATCH 02/14] kernel: introduce linux-yocto v4.9 recipes

[Bruce Ashfield]

Introducing the 4.9 kernel recipes. 4.9 will be a LTSI kernel, so we
introduce these recipes with the intent that they'll replace 4.1 as
the LTSI kernel, and other older kernels (i.e 4.4/4.8)  once 4.9
shown to be stable.

linux-yocto-tiny and linux-yocto-rt are also part of this commit, but
are placeholders while we wait for their content to be available. They
will build, but provide nothing above the standard kernel at the
moment.

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb   | 38 
 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb | 25 +
 meta/recipes-kernel/linux/linux-yocto_4.9.bb  | 44 +++
 3 files changed, 107 insertions(+)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_4.9.bb

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
new file mode 100644
index ..2f1c6523147c
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
@@ -0,0 +1,38 @@
+KBRANCH ?= "standard/preempt-rt/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# Skip processing of this recipe if it is not explicitly specified as the
+# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
+# to build multiple virtual/kernel providers, e.g. as dependency of
+# core-image-rt-sdk, core-image-rt.
+python () {
+if d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
+raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
+}
+
+SRCREV_machine ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
+SRCREV_meta ?= "c56f2da94e4773ea25eebfd14200164ef21730a3"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.9.git;branch=${KBRANCH};name=machine \
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.9;destsuffix=${KMETA}"
+
+LINUX_VERSION ?= "4.9"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+LINUX_KERNEL_TYPE = "preempt-rt"
+
+COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
+
+# Functionality flags
+KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
+KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
+KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
+KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
new file mode 100644
index ..62df631f3539
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
@@ -0,0 +1,25 @@
+KBRANCH ?= "standard/tiny/common-pc"
+LINUX_KERNEL_TYPE = "tiny"
+KCONFIG_MODE = "--allnoconfig"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+LINUX_VERSION ?= "4.9"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+SRCREV_machine ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
+SRCREV_meta ?= "c56f2da94e4773ea25eebfd14200164ef21730a3"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.9.git;branch=${KBRANCH};name=machine \
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.9;destsuffix=${KMETA}"
+
+COMPATIBLE_MACHINE = "(qemux86$)"
+
+# Functionality flags
+KERNEL_FEATURES = ""
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.9.bb
new file mode 100644
index ..d84400a323eb
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto_4.9.bb
@@ -0,0 +1,44 @@
+KBRANCH ?= "standard/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# board specific branches
+KBRANCH_qemuarm  ?= "standard/arm-versatile-926ejs"
+KBRANCH_qemuarm64 ?= "standard/qemuarm64"
+KBRANCH_qemumips ?= "standard/mti-malta32"
+KBRANCH_qemuppc  ?= "standard/qemuppc"
+KBRANCH_qemux86  ?= "standard/base"
+KBRANCH_qemux86-64 ?= "standard/base"
+KBRANCH_qemumips64 ?= "standard/mti-malta64"
+
+SRCREV_machine_qemuarm ?= "0fda844a4c8da3d987b8173128c2b14948133b2e"
+SRCREV_machine_qemuarm64 ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
+SRCREV_machine_qemumips ?= "22f2f6de114cf1fc58e068d1aff220d633aeaddf"
+SRCREV_machine_qemuppc ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
+SRCREV_machine_qemux86 ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
+SRCREV_machine_qemux86-64 ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
+SRCREV_machine_qemumips64 ?= "3183d61d4d00d8b7faf10d11b3da8cf3db432e6f"
+SRCREV_machine ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
+SRCREV_meta ?= "c56f2da94e4773ea25eebfd14200164ef21730a3"
+
+SRC_URI = 

[OE-core] [PATCH 07/14] linux-yocto/4.9: -stable update to v4.9.2

[Bruce Ashfield]

The shortlog of changes follows:

   6f2fabab8d63 Linux 4.9.2
   8ed8791885aa drm/i915: Fix setting of boost freq tunable
   18a00ac6d7f1 drm/i915: skip the first 4k of stolen memory on everything >= 
gen8
   639641105443 drm/i915: Initialize dev_priv->atomic_cdclk_freq at init time
   159e2ea9ed49 drm/i915: Fix cdclk vs. dev_cdclk mess when not recomputing 
things
   d816da6f5766 drm/i915/dsi: Do not clear DPOUNIT_CLOCK_GATE_DISABLE from 
vlv_init_display_clock_gating
   6cb4179f97cf drm/i915/dsi: Fix chv_exec_gpio disabling the GPIOs it is 
setting
   2037b1b46cdb net: mvpp2: fix dma unmapping of TX buffers for fragments
   3f3a6bbe6f9f sg_write()/bsg_write() is not fit to be called under KERNEL_DS
   d024532a97db kconfig/nconf: Fix hang when editing symbol with a long prompt
   173fd37a3d21 target/user: Fix use-after-free of tcmu_cmds if they are expired
   630a2ef354bb libnvdimm, pfn: fix align attribute
   6838ac125324 of, numa: Return NUMA_NO_NODE from disable of_node_to_nid() if 
nid not possible.
   d5cf5ae25c95 powerpc/boot: Request no dynamic linker for boot wrapper
   efcb3d9442ff powerpc/ps3: Fix system hang with GCC 5 builds
   4b23132d6cf5 powerpc/64e: Convert cmpi to cmpwi in head_64.S
   369b330c9d82 SUNRPC: fix refcounting problems with auth_gss messages.
   ba15defe1807 pNFS: Fix a deadlock between read resends and layoutreturn
   e523ce8c99f9 pNFS: Clear NFS_LAYOUT_RETURN_REQUESTED when invalidating the 
layout stateid
   f32659df6e15 pNFS: Don't clear the layout stateid if a layout return is 
outstanding
   24b049fa0cd9 pNFS: On error, do not send LAYOUTGET until the LAYOUTRETURN 
has completed
   b775b86a5fe8 nfs_write_end(): fix handling of short copies
   fc6cb9c303e2 libceph: verify authorize reply on connect
   d8c34b0cc0be PCI: Check for PME in targeted sleep state
   7cc603e9a828 i40iw: Use correct src address in memcpy to rdma stats counters
   6195cd1a9628 bad_inode: add missing i_op initializers
   afd2a1994ea4 Input: drv260x - fix input device's parent assignment
   e5d92c0c84f3 v4l: tvp5150: Add missing break in set control handler
   7f89c1373637 media: solo6x10: fix lockup by avoiding delayed register write
   3fbe140e9d36 s5p-mfc: fix failure path of s5p_mfc_alloc_memdev()
   9fd64b830259 mn88473: fix chip id check on probe
   eb9afff9513d mn88472: fix chip id check on probe
   9aff8b170fe0 IB/cma: Fix a race condition in iboe_addr_get_sgid()
   476ed812c42d IB/rxe: Fix a memory leak in rxe_qp_cleanup()
   5984423bf7eb IB/multicast: Check ib_find_pkey() return value
   4187dfa67fa9 IPoIB: Avoid reading an uninitialized member variable
   382072e09f19 IB/mad: Fix an array index check
   239b40eb6189 fgraph: Handle a case where a tracer ignores set_graph_notrace
   a035dc674dd4 x86/smpboot: Make logical package management more robust
   3168762e8ad3 platform/x86: asus-nb-wmi.c: Add X45U quirk
   21be088c36c6 ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from 
using short jumps to it
   e80ceb2da52e vsock/virtio: fix src/dst cid format
   d06485e0fcf5 fsnotify: Fix possible use-after-free in inode iteration on 
umount
   3f618a0b872f kvm: nVMX: Allow L1 to intercept software exceptions (#BP and 
#OF)
   94107133ae81 KVM: PPC: Book3S HV: Don't lose hardware R/C bit updates in 
H_PROTECT
   75b1053c2b8c KVM: PPC: Book3S HV: Save/restore XER in checkpointed register 
state
   483eeca2cf38 scsi: aacraid: remove wildcard for series 9 controllers
   8beb252f2be2 md/raid5: limit request size according to implementation limits
   a0357979d620 sc16is7xx: Drop bogus use of IRQF_ONESHOT
   7d5ec9eb3eea latent_entropy: fix ARM build error on earlier gcc
   959e95305f13 arm64: KVM: pmu: Reset PMSELR_EL0.SEL to a sane value before 
entering the guest
   111e0ccaf979 s390/kexec: use node 0 when re-adding crash kernel memory
   53bbee3348d8 s390/vmlogrdr: fix IUCV buffer allocation
   b3854cefe3d2 firmware: fix usermode helper fallback loading
   ce7ec3d7526c ARC: mm: arc700: Don't assume 2 colours for aliasing VIPT dcache
   9d33a3995667 scsi: avoid a permanent stop of the scsi device's request queue
   2a940b853ef6 scsi: zfcp: fix rport unblock race with LUN recovery
   744807cb251f scsi: zfcp: do not trace pure benign residual HBA responses at 
default level
   2ce34d9da427 scsi: zfcp: fix use-after-"free" in FC ingress path after TMF
   8032a30081c1 iscsi-target: Return error if unable to add network portal
   113783ec1cdb scsi: megaraid_sas: Do not set MPI2_TYPE_CUDA for JBOD FP path 
for FW which does not support JBOD sequence map
   6089f8712dcb scsi: megaraid_sas: For SRIOV enabled firmware, ensure VF 
driver waits for 30secs before reset
   2d2914349286 stm class: Fix device leak in open error path
   fbb28e76454f vt: fix Scroll Lock LED trigger name
   11aa5c10102a block: protect iterate_bdevs() against concurrent close
   09c154920e77 mei: me: add lewisburg device ids
   0814c3ede27a mei: request async autosuspend at the end of enumeration
   66469319c01a 

[OE-core] [PATCH 04/14] kernel-yocto: tiny features aka Link Time Optimization

[Bruce Ashfield]

Integrating the following patches for the 4.4/4.8 and 4.9
kernel to enable LTO for linux-yocto-tiny configurations
(i.e. poky-tiny).

b9735c0b4235 intel-quark: Remove support for serial-all
ce02da2e7833 features/usb/serial: Add new usb serial feature
f5b00d3a7e68 soc/x1000: Remove 'default policy' features
ca2dc186ff32 soc/x1000: Remove unnecessary features
90061752cbb5 soc/x1000: Remove bsp/common-pc/*
00b26ed213c4 meta/intel-common: Have intel-quark-tiny use 
common-drivers-32-essential
7ce24a2c497b meta/intel-common: Add intel-common-drivers-32-essential feature
ef711e0ab70e meta: Add lto-debug feature
1ca570817bf3 meta: Add lto-disable feature
45e5c2e9118e meta: Add lto (Link-Time Optimization) enablement feature

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.4.bb  | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.8.bb  | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.9.bb  | 2 +-
 9 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
index 4487c06bf396..20ea0dc9b2ca 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
@@ -12,7 +12,7 @@ python () {
 }
 
 SRCREV_machine ?= "61d7bf47fe27b7dfd9a73b0a6de2d78a29af8b74"
-SRCREV_meta ?= "b846fc6436aa5d4c747d620e83dfda969854d10c"
+SRCREV_meta ?= "7da5624a915368bb93814379e7e1c3bbefae4cae"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.4.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb
index 6079225cbc04..ce83410d0a1d 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb
@@ -12,7 +12,7 @@ python () {
 }
 
 SRCREV_machine ?= "3bafd55e39da7fd7c5d483fdee5b72450df3caf0"
-SRCREV_meta ?= "926c93ae07de2173b4f764d1da6996597a6d2b73"
+SRCREV_meta ?= "9ca50a7edc6bba11f0f9ce1eec3e6004f3043820"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.8.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.8;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
index d505f924bdc7..e41c87487076 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
@@ -12,7 +12,7 @@ python () {
 }
 
 SRCREV_machine ?= "1eb33152d655c73193cec17c4de04499e52b2faa"
-SRCREV_meta ?= "7ca94971d258304e3e3068f7b7ebe425fe5a77d1"
+SRCREV_meta ?= "68e8915786f48996e699272ba33626a44978a14e"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.9.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.9;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
index dfd947cf75ce..4fc499c9d892 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
@@ -10,7 +10,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "35482df5d5ba0807eb8a7c40b554bd657e3f9987"
-SRCREV_meta ?= "b846fc6436aa5d4c747d620e83dfda969854d10c"
+SRCREV_meta ?= "7da5624a915368bb93814379e7e1c3bbefae4cae"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb
index 15b03579d4a3..721e5c4c2094 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb
@@ -10,7 +10,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "e274a507b23c23bf0dd6502d0c38fae731c11511"
-SRCREV_meta ?= "926c93ae07de2173b4f764d1da6996597a6d2b73"
+SRCREV_meta ?= "9ca50a7edc6bba11f0f9ce1eec3e6004f3043820"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
index bf23d3efe29f..613db1164156 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
@@ -10,7 +10,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
-SRCREV_meta ?= 

[OE-core] [PATCH 05/14] linux-yocto/4.4/4.8/4.9: netfilter: iptables: enable NAT tables

[Bruce Ashfield]

This changes adds 'nat' table in iptables. The netfilter side
is already configured for NAT but iptables config was missing.

Further, CONFIG_IP_NF_TARGET* configured below depend on
CONFIG_IP_NF_NAT but remain disabled unless CONFIG_IP_NF_NAT
is explicitly enabled.

CONFIG_IP_NF_TARGET_MASQUERADE is needed by Connman to
support tethering.

Signed-off-by: Mikko Ylinen 
Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.4.bb  | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.8.bb  | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.9.bb  | 2 +-
 9 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
index 20ea0dc9b2ca..53a9b5736dda 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
@@ -12,7 +12,7 @@ python () {
 }
 
 SRCREV_machine ?= "61d7bf47fe27b7dfd9a73b0a6de2d78a29af8b74"
-SRCREV_meta ?= "7da5624a915368bb93814379e7e1c3bbefae4cae"
+SRCREV_meta ?= "4c31a115453dad875dda85786c4c34572d6c64a2"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.4.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb
index ce83410d0a1d..5991f2b165b5 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb
@@ -12,7 +12,7 @@ python () {
 }
 
 SRCREV_machine ?= "3bafd55e39da7fd7c5d483fdee5b72450df3caf0"
-SRCREV_meta ?= "9ca50a7edc6bba11f0f9ce1eec3e6004f3043820"
+SRCREV_meta ?= "0da38d7c70b06ba69dcc6fa305ecf4edc2669598"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.8.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.8;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
index e41c87487076..1dd3b38362ac 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
@@ -12,7 +12,7 @@ python () {
 }
 
 SRCREV_machine ?= "1eb33152d655c73193cec17c4de04499e52b2faa"
-SRCREV_meta ?= "68e8915786f48996e699272ba33626a44978a14e"
+SRCREV_meta ?= "0cf14593694d33518aabd4846d50adeeb7f559ed"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.9.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.9;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
index 4fc499c9d892..36e88e34787b 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
@@ -10,7 +10,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "35482df5d5ba0807eb8a7c40b554bd657e3f9987"
-SRCREV_meta ?= "7da5624a915368bb93814379e7e1c3bbefae4cae"
+SRCREV_meta ?= "4c31a115453dad875dda85786c4c34572d6c64a2"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb
index 721e5c4c2094..d2f6c7e71ac7 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb
@@ -10,7 +10,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "e274a507b23c23bf0dd6502d0c38fae731c11511"
-SRCREV_meta ?= "9ca50a7edc6bba11f0f9ce1eec3e6004f3043820"
+SRCREV_meta ?= "0da38d7c70b06ba69dcc6fa305ecf4edc2669598"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
index 613db1164156..f4b03a72cb3d 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
@@ -10,7 +10,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
-SRCREV_meta ?= "68e8915786f48996e699272ba33626a44978a14e"
+SRCREV_meta ?= "0cf14593694d33518aabd4846d50adeeb7f559ed"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.4.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.4.bb
index 77b1b8091219..8142a361f498 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.4.bb
+++ 

[OE-core] [PATCH 06/14] kernel-yocto: firewire and audio configuration updates

[Bruce Ashfield]

Integrating firewire and audio configuration updates from Jussi:

Add support for IEEE-1394 (Firewire)

Adds support for IEEE-1394 aka Firewire bus and some commonly used
devices.

Signed-off-by: Jussi Laako 

Update audio support

Updates audio support to work with modern audio hardware while
dropping some legacy parts.

Signed-off-by: Jussi Laako 

Signed-off-by: Jussi Laako 
Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.9.bb  | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
index 1dd3b38362ac..647030b9c5a0 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
@@ -12,7 +12,7 @@ python () {
 }
 
 SRCREV_machine ?= "1eb33152d655c73193cec17c4de04499e52b2faa"
-SRCREV_meta ?= "0cf14593694d33518aabd4846d50adeeb7f559ed"
+SRCREV_meta ?= "62afd8f4635269a59baf47d6fb894d73edfa9449"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.9.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.9;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
index f4b03a72cb3d..99c12a6b6284 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
@@ -10,7 +10,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
-SRCREV_meta ?= "0cf14593694d33518aabd4846d50adeeb7f559ed"
+SRCREV_meta ?= "62afd8f4635269a59baf47d6fb894d73edfa9449"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.9.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.9.bb
index 256d3dbea0f1..2765b3711f77 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.9.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.9.bb
@@ -19,7 +19,7 @@ SRCREV_machine_qemux86 ?= 
"617635e43afee1aaf98a8f8300596f7a112513c0"
 SRCREV_machine_qemux86-64 ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
 SRCREV_machine_qemumips64 ?= "3183d61d4d00d8b7faf10d11b3da8cf3db432e6f"
 SRCREV_machine ?= "617635e43afee1aaf98a8f8300596f7a112513c0"
-SRCREV_meta ?= "0cf14593694d33518aabd4846d50adeeb7f559ed"
+SRCREV_meta ?= "62afd8f4635269a59baf47d6fb894d73edfa9449"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.9.git;name=machine;branch=${KBRANCH}; 
\

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.9;destsuffix=${KMETA}"
-- 
2.5.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 01/14] linux-libc-headers: introduce 4.9 headers

[Bruce Ashfield]

Bumping the linux-libc-headers to the 4.9 kernel variant. Since 4.9
will be a LTSI kernel, and there will be an associated linux-yocto
it is worth moving to these headers sooner rather than later.

This commit also drops the 4.8 headers and sets 4.9 to be the default.

Signed-off-by: Bruce Ashfield 
---
 meta/conf/distro/include/tcmode-default.inc | 2 +-
 .../{linux-libc-headers_4.8.bb => linux-libc-headers_4.9.bb}| 6 ++
 2 files changed, 3 insertions(+), 5 deletions(-)
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_4.8.bb => 
linux-libc-headers_4.9.bb} (64%)

diff --git a/meta/conf/distro/include/tcmode-default.inc 
b/meta/conf/distro/include/tcmode-default.inc
index 7fceb58ee6d1..8d5e9d645c17 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -28,7 +28,7 @@ BINUVERSION ?= "2.27%"
 GDBVERSION ?= "7.12%"
 GLIBCVERSION ?= "2.24"
 UCLIBCVERSION ?= "1.0%"
-LINUXLIBCVERSION ?= "4.8%"
+LINUXLIBCVERSION ?= "4.9%"
 
 PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
 PREFERRED_VERSION_gcc-cross-${TARGET_ARCH} ?= "${GCCVERSION}"
diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.8.bb 
b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.9.bb
similarity index 64%
rename from meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.8.bb
rename to meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.9.bb
index 77e0870d326f..0a44018f880b 100644
--- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.8.bb
+++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.9.bb
@@ -1,12 +1,10 @@
 require linux-libc-headers.inc
 
-PV = "4.8"
-
 SRC_URI_append_libc-musl = "\
 file://0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch \
 file://0002-libc-compat.h-prevent-redefinition-of-struct-ethhdr.patch \
 file://0003-remove-inclusion-of-sysinfo.h-in-kernel.h.patch \
"
 
-SRC_URI[md5sum] = "c1af0afbd3df35c1ccdc7a5118cd2d07"
-SRC_URI[sha256sum] = 
"3e9150065f193d3d94bcf46a1fe9f033c7ef7122ab71d75a7fb5a2f0c9a7e11a"
+SRC_URI[md5sum] = "0a68ef3615c64bd5ee54a3320e46667d"
+SRC_URI[sha256sum] = 
"029098dcffab74875e086ae970e3828456838da6e0ba22ce3f64ef764f3d7f1a"
-- 
2.5.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 00/14] kernel-yocto: consolidated pull request

[Bruce Ashfield]

People have been asking about 4.9 and related changes, so I'm resending
my consolidated queue to make the patches visible and available for
merging.

These are 4.9, 4.9-rt, libc-headers, -stable updates, meta data tweaks
and fixes/enhancements for the kern tools.

Cheers,

Bruce

The following changes since commit 63f899a950daf1018999455bafa7a2be8b22f164:

  bitbake: toaster: bin/toaster whitelist TOASTER_DIR (2017-01-17 13:18:47 
+)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (14):
  linux-libc-headers: introduce 4.9 headers
  kernel: introduce linux-yocto v4.9 recipes
  linux-yocto-rt/4.9: add -rt specific patches
  kernel-yocto: tiny features aka Link Time Optimization
  linux-yocto/4.4/4.8/4.9: netfilter: iptables: enable NAT tables
  kernel-yocto: firewire and audio configuration updates
  linux-yocto/4.9: -stable update to v4.9.2
  linux-yocto/4.8: -stable update to v4.8.17
  linux-yocto/4.4: update to v4.4.41
  linux-yocto/4.1: update to v4.1.37
  kern-tools: scc: Fix process_file error check
  linux-yocto/4.8: update to -rt10
  kern-tools: kconf_check: flag CONFIG options with invalid spaces
  linux-yocto/4.9: merge 4.9.3 and ethernet config changes

 meta/conf/distro/include/tcmode-default.inc|  2 +-
 .../kern-tools/kern-tools-native_git.bb|  2 +-
 ...bc-headers_4.8.bb => linux-libc-headers_4.9.bb} |  6 +--
 meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb|  6 +--
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb|  6 +--
 meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb|  6 +--
 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb| 38 +++
 meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb  |  6 +--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb  |  6 +--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb  |  6 +--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb  | 25 
 meta/recipes-kernel/linux/linux-yocto_4.1.bb   | 20 +-
 meta/recipes-kernel/linux/linux-yocto_4.4.bb   | 20 +-
 meta/recipes-kernel/linux/linux-yocto_4.8.bb   | 20 +-
 meta/recipes-kernel/linux/linux-yocto_4.9.bb   | 44 ++
 15 files changed, 159 insertions(+), 54 deletions(-)
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_4.8.bb => 
linux-libc-headers_4.9.bb} (64%)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_4.9.bb

-- 
2.5.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 2/2 V2] glibc: Upgrade to 2.25 snapshot

[Burton, Ross]

On 12 January 2017 at 20:20, Khem Raj  wrote:

>  .../glibc/{glibc_2.24.bb => glibc_2.25.bb} |  23 ++--
>

I was wondering what the actual version was as this isn't 2.25 yet.  The
libraries are actually libc-2.24.90.so, so I think the recipe version
should reflect that, if only for clarity when 2.25 is actually released.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH][Morty] binutils-2.27.inc: Fix alignment frags for aarch64

[Nathan Rossi]

On 18 January 2017 at 19:37, Mike Looijmans  wrote:
> Could someone at least please say "yes" or "no"?
>
> I now have three projects waiting for this patch to be included in morty. If
> it's not going to happen, I'll have to add a bbappend to these layers to fix
> it.
>
> On 16-01-17 18:49, Manjukumar Harthikote Matha wrote:
>>
>> Ping, this has been applied to master

Armin, you mentioned on IRC ~1 week ago that you had merged it to your
staging branch? Any updates?

Also I had a look and could not find the change in
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akuster/morty-next?
Maybe I am looking in the wrong place though for your staging tree?

Thanks,
Nathan
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 00/56] Consolidated pul

[Burton, Ross]

On 18 January 2017 at 10:15, Nicolas Dechesne 
wrote:

> > Khem Raj (1):
> >   gstreamer1.0-plugins-bad: Backport patches for improving live
> playback
> >
>
> I was under the impression that this one would be dropped.. at least
> based on last emails. maybe it was discussed separately.. did you
> conclude that we need these patches?


Personally I'm easy either way.  It's not a giant patch and can be removed
when the upgrade happens.  Then again it's churn that interested parties
can equally hold in their own distro layer.

CCing Khem for his opinion.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH][Morty] binutils-2.27.inc: Fix alignment frags for aarch64

[Mike Looijmans]

Could someone at least please say "yes" or "no"?

I now have three projects waiting for this patch to be included in morty. If 
it's not going to happen, I'll have to add a bbappend to these layers to fix it.


On 16-01-17 18:49, Manjukumar Harthikote Matha wrote:

Ping, this has been applied to master

Thanks
Manju





Kind regards,

Mike Looijmans
System Expert

TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail





-Original Message-

From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Tuesday, November 22, 2016 2:03 PM
To: Manjukumar Harthikote Matha
Cc: Patches and discussions about the oe-core layer
Subject: Re: [OE-core] [PATCH][Morty] binutils-2.27.inc: Fix alignment frags for
aarch64

This is ok for master


On Nov 22, 2016 1:31 PM, "Manjukumar Matha" mailto:manjukumar.harthikote-ma...@xilinx.com> > wrote:


  There was bug with alignment frags for aarch64 in binutils. This is
  fixed in master of binutils. This patch backports the fix to binutils
  2.27 version.

  Signed-off-by: Manjukumar Matha mailto:manjukumar.harthikote-ma...@xilinx.com> >
  Signed-off-by: Nathan Rossi  >
  ---
   meta/recipes-devtools/binutils/binutils-2.27.inc   |   1 +
   ...eration-of-alignment-frags-in-code-sectio.patch | 139
+
   2 files changed, 140 insertions(+)
   create mode 100644 meta/recipes-devtools/binutils/binutils/0017-Fix-the-
generation-of-alignment-frags-in-code-sectio.patch

  diff --git a/meta/recipes-devtools/binutils/binutils-2.27.inc 
b/meta/recipes-
devtools/binutils/binutils-2.27.inc
  index fc81721..90518bf 100644
  --- a/meta/recipes-devtools/binutils/binutils-2.27.inc
  +++ b/meta/recipes-devtools/binutils/binutils-2.27.inc
  @@ -37,6 +37,7 @@ SRC_URI = "\
file://0015-binutils-mips-gas-pic-relax-linkonce.diff \

file://0015-Refine-.cfi_sections-check-to-only-consider-compact-.patch
\

file://0016-Fix-seg-fault-in-ARM-linker-when-trying-to-parse-a-b.patch \
  + 
file://0017-Fix-the-generation-of-alignment-frags-in-code-sectio.patch
\
   "
   S  = "${WORKDIR}/git"

  diff --git 
a/meta/recipes-devtools/binutils/binutils/0017-Fix-the-generation-
of-alignment-frags-in-code-sectio.patch b/meta/recipes-
devtools/binutils/binutils/0017-Fix-the-generation-of-alignment-frags-in-code-
sectio.patch
  new file mode 100644
  index 000..f8b46be
  --- /dev/null
  +++ b/meta/recipes-devtools/binutils/binutils/0017-Fix-the-generation-of-
alignment-frags-in-code-sectio.patch
  @@ -0,0 +1,139 @@
  +From 4a4286465b5d6c28968bc2b29ae08daca7f219a3 Mon Sep 17
00:00:00 2001
  +From: Nick Clifton  >
  +Date: Fri, 18 Nov 2016 11:42:48 -0800
  +Subject: [PATCH] Fix the generation of alignment frags in code sections 
for
AArch64.
  +
  +PR gas/20364
  +* config/tc-aarch64.c (s_ltorg): Change the mapping state after
  +aligning the frag.
  +(aarch64_init): Treat rs_align frags in code sections as
  +containing code, not data.
  +* testsuite/gas/aarch64/pr20364.s: New test.
  +* testsuite/gas/aarch64/pr20364.d: New test driver.
  +
  +Backporting the patch from binutils mainline
  +https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;h=7ea12e5c3ad54da440c08f32da09534e63e515ca

  +
  +Upstream-Status: Backport
  +
  +Signed-off-by: Manjukumar Matha mailto:manjukumar.harthikote-ma...@xilinx.com> >
  +---
  + gas/ChangeLog   | 10 ++
  + gas/config/tc-aarch64.c | 10 +++---
  + gas/testsuite/gas/aarch64/pr20364.d | 13 +
  + gas/testsuite/gas/aarch64/pr20364.s | 28

  + 4 files changed, 58 insertions(+), 3 deletions(-)
  + create mode 100644 gas/testsuite/gas/aarch64/pr20364.d
  + create mode 100644 gas/testsuite/gas/aarch64/pr20364.s
  +
  +diff --git a/gas/ChangeLog b/gas/ChangeLog
  +index a39895a..fad06dc 100644
  +--- a/gas/ChangeLog
   b/gas/ChangeLog
  +@@ -1,3 +1,13 @@
  ++2016-08-05  Nick Clifton   >
  ++
  ++  PR gas/20364
  ++  * config/tc-aarch64.c (s_ltorg): Change the mapping state after
  ++  aligning the frag.
  ++  (aarch64_init): Treat rs_align frags in code sections as
  ++  containing code, not data.
  ++  * testsuite/gas/aarch64/pr20364.s: New test.
  ++  * testsuite/gas/aarch64/pr20364.d: New test driver.
  ++
  + 2016-08-03  

Re: [OE-core] [PATCH 00/56] Consolidated pul

[Nicolas Dechesne]

On Wed, Jan 18, 2017 at 11:08 AM, Ross Burton  wrote:
> Khem Raj (1):
>   gstreamer1.0-plugins-bad: Backport patches for improving live playback
>

I was under the impression that this one would be dropped.. at least
based on last emails. maybe it was discussed separately.. did you
conclude that we need these patches?
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 00/56] Consolidated pul

[Ross Burton]

Hi,

A consolidated pull with meta-poky and bitbake commits at the beginning, then
oe-core.

Green on the autobuilder apart from three failures in checkuri: two transient
and one genuine: ed's upstream tarball has disappeared.

Ross

The following changes since commit 63f899a950daf1018999455bafa7a2be8b22f164:

  bitbake: toaster: bin/toaster whitelist TOASTER_DIR (2017-01-17 13:18:47 
+)

are available in the git repository at:

  ssh://g...@git.yoctoproject.org/poky-contrib ross/mut

for you to fetch changes up to 3409effd461f148eba2d51f6819e73f8bdcca777:

  oeqa/selftest/devtool: rewrite modify testcase (2017-01-18 10:04:30 +)


Andre McCurdy (1):
  gstreamer1.0-plugins-good: fix qtdemux_parse_svq3_stsd_data() memory leak

Andreas Müller (1):
  waf.bbclass: handle PACKAGECONFIG

André Draszik (2):
  python3-pygobject: enable cairo only when a display is available
  time: BBCLASSEXTEND to native and nativesdk

Benjamin Esquivel (1):
  poky: add fedora-25 to the SANITY_TESTED_DISTROS

Chen Qi (1):
  byacc: upgrade to 20161202

David Vincent (1):
  extrausers: Use static ids when available

Edwin Plauchu (4):
  swig: upgrade to 3.0.11
  python3-setuptools: upgrade to 31.1.1
  python3-pip: fixed dependecy with python3-enum
  python3-docutils: upgrade to 0.13.1

Fabio Berton (1):
  openssl: Use linux-aarch64 target for aarch64

Jose Perez Carranza (1):
  oeqa/selftest/tinfoil: add test IDs to tinfoil test cases

Joshua Lock (1):
  poky: Switch to post release name/version

Khem Raj (1):
  gstreamer1.0-plugins-bad: Backport patches for improving live playback

Maciej Borzecki (1):
  wic: partitionedfs: account for non-table partitions when checking if 
logical parititon is needed

Mariano Lopez (3):
  lib/oe/package_manager.py: Fix extract for ipk and deb
  oeqa/utils/qemurunner.py: Add missing sys module
  oeqa/utils/qemurunner.py: Be sure to stop qemu-system

Markus Lehtonen (10):
  oeqa.utils.metadata: re-organise host distro information
  oeqa.utils.metadata: re-organise distro information
  oeqa.utils.metadata: drop 'unknown' git data elements
  oeqa.utils.metadata: fix retrieval of git branch and revision
  oeqa.utils.metadata: rename 'revision' to 'commit'
  oeqa.utils.metadata: add commit count information
  oeqa.utils.metadata: have layer name as an attribute in xml
  oeqa.utils.metadata: add bitbake revision information
  oeqa.utils.metadata: allow storing any bitbake config variables
  oeqa.utils.metadata: include BB_NUMBER_THREADS and PARALLEL_MAKE

Maxin B. John (4):
  libproxy: update to version 0.4.14
  mdadm: upgrade to version 4.0
  netbase: upgrade to version 5.4
  harfbuzz: upgrade to 1.4.1

Nathan Lynch (5):
  lttng-ust: don't exclude manual pages from build
  lttng-ust: upgrade to 2.9.0
  lttng-modules: upgrade to 2.9.0
  lttng-tools: upgrade to 2.9.3
  babeltrace: upgrade to 1.5.1

Nathan Rossi (3):
  kernel-fitimage.bbclass: Allow unset load/entry addresses for ramdisks
  kernel-fitimage.bbclass: Don't assume KERNEL_IMAGETYPE == fitImage
  kernel-fitimage.bbclass: Check value of UBOOT_SIGN_ENABLE

Ola Redell (1):
  kernel-module-split: Append KERNEL_VERSION string to kernel module name

Patrick Ohly (6):
  rm_work.bbclass: allow preserving additional content
  build.py: add preceedtask() API
  runqueue.py: revised completion scheduler
  rm_work_and_downloads.bbclass: more aggressively minimize disk usage
  rm_work.bbclass: clean up sooner
  gcc-source.inc: cleanly disable do_rm_work

Richard Purdie (1):
  event/ast: Add RecipeTaskPreProcess event before task finalisation

Robert Yang (3):
  qemuboot.bbclass: use IMGDEPLOYDIR
  scripts/runqemu: fix checking for .cpio.gz
  runqemu-export-rootfs: fix inconsistent var names

Ross Burton (4):
  perf: use PACKAGECONFIG instead of hand-rolled logic
  perf: add PACKAGECONFIG for systemtap
  gstreamer1.0: make libunwind detection deterministic
  oeqa/selftest/devtool: rewrite modify testcase

 bitbake/lib/bb/build.py|  16 +
 bitbake/lib/bb/event.py|   7 +
 bitbake/lib/bb/parse/ast.py|   1 +
 bitbake/lib/bb/runqueue.py | 125 ++-
 meta-poky/conf/distro/poky.conf|   5 +-
 meta/classes/extrausers.bbclass|   4 +
 meta/classes/kernel-fitimage.bbclass   |  23 +-
 meta/classes/kernel-module-split.bbclass   |   9 +-
 meta/classes/qemuboot.bbclass  |   5 +-
 meta/classes/rm_work.bbclass   |  41 +-
 meta/classes/rm_work_and_downloads.bbclass |  33 +
 meta/classes/testimage.bbclass |   2 +
 meta/classes/useradd-staticids.bbclass

[OE-core] Layer index enhancements

[Paul Eggleton]

Hi all,

We've done some work recently on the OE layer index [1] and I thought it might 
be useful to give a summary of what's been implemented:

* Upgraded to Django 1.8. This was a bunch of work without much visible 
impact, however it does mean we are now on an LTS version of Django which is 
much easier to maintain and will receive security updates until some time in 
2018.

* Added the ability to search for recipes inheriting a specific class - just 
add inherits:classname to the search text. For example [2] - you can even 
search for recipes inheriting several classes [3] (i.e. all specified classes 
must be inherited in order to match). Note: any other search words are 
interpreted as part of a string that must be present - we haven't switched to 
doing keyword-based searching.

* Distros provided by each layer are now collected. I still have to sort out 
an issue with the collection so most of them aren't showing up in the index 
yet, but the capability exists.

* Update records - each time we do an update (every three hours) or when a 
manual update is triggered by Michael, we record the output against the layer 
plus a separate overall record for the update showing the output for all 
layers (if you log in this is available from Tools -> Updates, but anyone can 
access it at [4]). The latter also lets us see how long updates are taking. If 
you look over the recent update logs you can see we still have to fix up some 
issues with the data (e.g. because of branches and repos going away, missing 
dependencies or other metadata issues, etc.). Hopefully making this more 
visible will help us to tidy these up.

* The layer submission/editing page now lets you select a git web interface, 
so if you're submitting a layer that's hosted on a server providing a cgit, 
gitweb or gitlab web interface that isn't one of the common servers we know 
about (e.g. git.openembedded.org, github, etc.) then you won't have to figure 
out the syntax for the file/tree URLs, you just select the type and it'll set 
those fields automatically.

* Fixed a bug that caused recipes to show up twice in the search results if 
the searched string appeared in both the name and description. Exact matches 
on name now show up first in the search results as well.

* Fixed a recently introduced bug in the OE-Classic search that resulted in 
Internal Server errors when searching by name

* We now pick up layer dependencies (and recommends) specified in the 
layer.conf, but only if they match the layer name - we don't handle collection 
names yet, so this won't currently work where the collection name doesn't 
match the layer name (e.g. oe-core, meta-oe...).

* Counts for recipes, machines, classes, appends, and distros are now shown on 
each tab on the layer detail page

Thanks to Michael Halstead, Liam Howlett and Mark Hatle for helping me with 
these.

Cheers,
Paul


[1] https://layers.openembedded.org/

[2] 
http://layers.openembedded.org/layerindex/branch/master/recipes/?q=inherits%3Acmake

[3]
http://layers.openembedded.org/layerindex/branch/master/recipes/?q=inherits%3Acmake+inherits%3Apkgconfig

[4] https://layers.openembedded.org/layerindex/updates/


-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2 0/6] runqemu: fix for slirp, network device and hostfwd

[Robert Yang]

Hi Ross,

Sorry, my fault, something was wrong with qemuppc.conf, it should not
set "-device virtio-net-pci,netdev=net0,mac=@MAC@" since it is already
in QB_NETWORK_DEVICE.

Fixed in the repo:

  git://git.openembedded.org/openembedded-core-contrib rbt/runqemu

http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/runqemu

Robert Yang (6):
  scripts/runqemu: fix checking for .cpio.gz
  qemuboot.bbclass: use IMGDEPLOYDIR
  runqemu-export-rootfs: fix inconsistent var names
  runqemu: support mutiple qemus running when nfs
  runqemu: fixes for slirp, network device and hostfwd
  qemuboot.bbclass: add blank lines in comments

// Robert

On 01/17/2017 09:14 PM, Burton, Ross wrote:

Hi Robert,

I merged these into my staging branch but then the autobuilder failed in an
interesting way:

https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/1053/steps/Running%20Sanity%20Tests/logs/stdio

Would that be related to your series, or is it a coincidence?

Ross

On 11 January 2017 at 01:47, Robert Yang > wrote:

ping.

// Robert


On 12/21/2016 02:24 PM, Robert Yang wrote:

Hi Ross,

I rebased in the repo:

 git://git.openembedded.org/openembedded-core-contrib
 rbt/runqemu


http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/runqemu



Robert Yang (6):
  scripts/runqemu: fix checking for .cpio.gz
  qemuboot.bbclass: use IMGDEPLOYDIR
  runqemu-export-rootfs: fix inconsistent var names
  runqemu: support mutiple qemus running when nfs
  runqemu: fixes for slirp, network device and hostfwd
  qemuboot.bbclass: add blank lines in comments


// Robert

On 12/06/2016 04:55 PM, Robert Yang wrote:

* V2
  - Add QB_NETWORK_DEVICE to set network device for both slirp and 
tap,
the idea is from Randy and Nathan.
  - Use different mac sections for slirp and tap to fix conflicts 
when
running both of them on the same host.

* V1
  - Initial version

The following changes since commit
11063a01d4511b2688ea7ba2d7359e4e07328c66:

  ruby: upgrade to 2.3.1 (2016-11-30 15:47:17 +)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib
 rbt/runqemu


http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/runqemu




Robert Yang (6):
  scripts/runqemu: fix checking for .cpio.gz
  qemuboot.bbclass: use IMGDEPLOYDIR
  runqemu-export-rootfs: fix inconsistent var names
  runqemu: support mutiple qemus running when nfs
  runqemu: fixes for slirp, network device and hostfwd
  qemuboot.bbclass: add blank lines in comments

 meta/classes/qemuboot.bbclass  |  34 ++--
 meta/conf/machine/include/qemuboot-x86.inc |   1 -
 meta/conf/machine/qemuarm64.conf   |   1 -
 scripts/runqemu| 133
++---
 scripts/runqemu-export-rootfs  |  21 ++---
 5 files changed, 140 insertions(+), 50 deletions(-)



--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [Openembedded-architecture] Patchwork and incoming patch testing

[Jussi Kukkonen]

This looks great, thanks.

On 17 January 2017 at 20:05, Paul Eggleton 
wrote:

> In any event we are now finally in the
> position where our patchwork instance can be relied upon to collect emails,
> and the UI is much improved. This should give us a bit more visibility into
> where patches are at in the process, although we are still working on a few
> places where patch series status needs to be updated (e.g. when a patch
> goes
> into testing).


What's the plan for these status updates -- is the idea that you go to
patchwork UI to see the state of a specific patch set?
Or maybe a reply to either patch sender or even the ML?

On top of patchwork we have built a simple smoke-testing framework called
> "patchtest" [5] along with a suite of corresponding tests for OE [6]. These
> tests are fairly simplistic at this point but check the basics such as
> whether
> a patch has been properly signed off, etc. We should soon start seeing
> replies
> sent to the mailing list and to submitters with results if there are any
> failures, saving us from noticing and pointing out some of the more obvious
> classes of mistakes.


 Is there a reason for patchwork only showing "success" or "failure" in the
web ui, instead of linking to test results at least in in the failure case?



 - Jussi
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core