[linux-yocto] [PATCH 2/2] vmstat: make vmstat_updater deferrable again and shut down on idle

From: Christoph Lameter Backport: commit 0eb77e9880321915322d42913c3b53241739c8aa upstream. Currently the vmstat updater is not deferrable as a result of commit ba4877b9ca51 ("vmstat: do not use deferrable delayed work for vmstat_update"). This in turn can cause multiple

[linux-yocto] [PATCH 0/2] Backport on linux-yocto-4.4 bxt-rebase branch

Backport on linux-yocto-4.4. These patches are approved & available on upstream kernel. These patches have been rebased on bxt-rebase branch. Christoph Lameter (1): vmstat: make vmstat_updater deferrable again and shut down on idle Paul E. McKenney (1): rcu: Make expedited RCU-sched grace

[linux-yocto] [PATCH 1/2] rcu: Make expedited RCU-sched grace period immediately detect idle

From: "Paul E. McKenney" Backport: commit 28728dd310d48834cd486dac3cac9ae96b9deb96 upstream. Currently, sync_sched_exp_handler() will force a reschedule unless this CPU has already checked in or unless a reschedule has already been called for. This is clearly

Re: [yocto] [PATCH] Makefile: remove static linking in Linux build

On 8/26/16 3:45 PM, Jianxun Zhang wrote: > The removed static linking was for a desire to make rmc run > on systems where c libraries are not provided. > > But it is nothing wrong to dynamically link rmc with libraries. > We also don't have to hardcode the way of linking in Makefile > since

Re: [linux-yocto] [PATCH 1/3] drivers/misc: Axxia MTC Driver Memory Initialization Check

I have a proposed patch, but will get the original developer to run her unit test before I submit. As for the infinite loop, that's handled, I think, by the call to time_before(). Is that not the case? The updated section will be as follows. The loop will only run for, at most, 1000 msecs.

[linux-yocto] [PATCH] Makefile: remove static linking in Linux build

The removed static linking was for a desire to make rmc run on systems where c libraries are not provided. But it is nothing wrong to dynamically link rmc with libraries. We also don't have to hardcode the way of linking in Makefile since people can specify it in RMC_CFLAGS passed to make

[yocto] [PATCH] [yocto-autobuilder] RunOeSelftest.py: changed to new oe-selftest syntax

oe-selftest is changing syntax with YOCTO #8938. This patch modifies required commands to avoid breaking oe-seltest autobuilder. Should be integrated together with the syntax changing patch. [YOCTO #8938] --- lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py | 4 ++-- 1 file

[yocto] Yocto Project Status WW35

Current Dev Position: YP 2.2 M3 Next Deadline: YP 2.2 M3 which will be Aug 29th (5:00pm GMT) SWAT team rotation: Anibal -> Tracy https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: * The M3 deadline and feature freeze for 2.2 is on Monday. The patch queue is

Re: [yocto] [meta-swupd][PATCH] swupd-client_git.bb: Make pinned pubkey configurable

On Tue, 2016-08-23 at 10:35 +0300, Dmitry Rozhkov wrote: > SWUPD server may move to a new location where a different pubkey > needs to be used and the hardcoded one won't work. > > This makes pinned pubkey configurable. This change sounds good but fails to build here. swupd-client do_install

Re: [yocto] Git/yocto newbie question re: submodules and multiple layers

On Thu, Aug 25, 2016 at 04:24:34PM -0500, Michael Habibi wrote: > Hi, I am well-versed with Git but I haven't really ever had to use > submodules. I am trying to create a git repository on our server that > will host our yocto distribution. Our distribution will include the > yocto repo, plus

[yocto] Re(vival?): Missing files in rootfs when adding links /bin ->/usr/bin and /lib -> /usr/lib in recipe base-files

> When changing package base-files, so that the /bin directory is soft linked > to /usr/bin and the /lib directory is soft linked to /usr/lib, the > > resulting image/rootfs directory structure is missing a lot of files, most of > which are unrelated to any of the directories mentioned >

Re: [yocto] Git/yocto newbie question re: submodules and multiple layers

* Michael Habibi [160825 23:26]: > The difficulty I have is thus: > my_git_repo/ <--- what my platform developers will 'git clone' > my_git_repo/yocto_git/... <-- yocto framework > my_git_repo/yocto_git/meta-openembedded <-- another git repo nested > inside yocto repo >