On 25.08.2017 21:59, Martin Jansa wrote:
> Does the patch cause any harm when used on newer kernel?
Based on my limited testing on our devices running kernel 4.11.0, no.
>
> If so shouldn't the patch be fixed to work correctly even with newer
> kernel?
>
> Or what's the main reason to remove it
This reverts commit 9f32d9405ed5430e9e55de2f1562baac963e807c.
This patch is still needed since OLDEST_KERNEL is set to 3.2.0
Signed-off-by: Jose Alarcon
---
...ics-need-to-fake-new-touches-on-TRIPLETAP.patch | 72 ++
meta/recipes-graphics/wayland/libinput_1.8.1.bb| 1 +
Signed-off-by: Jose Alarcon
---
meta/classes/rootfs-postcommands.bbclass | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/classes/rootfs-postcommands.bbclass
b/meta/classes/rootfs-postcommands.bbclass
index e7999d4..fb36bad 100644
--- a/meta/classes/rootfs-postcommands.bbclass
+++ b/meta/
The do_rootfs log contains a number of unsatisfied package
recommendations. At the moment those are only visible when
reviewing the rootfs log.
This patch adds an extra check to surface any unsatisfied
recommendation as WARNINGS to the build output when
"debug-tweaks" is enabled.
Signed-off-by:
On 25.08.2017 15:29, Richard Purdie wrote:
> On Fri, 2017-08-25 at 09:43 +0300, Jose Alarcon wrote:
>> The do_rootfs log contains a number of unsatisfied package
>> recommendations. At the moment those are only visible when
>> reviewing the rootfs log.
>>
>> This class adds an extra check to surf
Sorry, I failed to read the whole thread (inbox filters).
I sent the revert this morning.
As I said, we have been running our devices with this patch in and kernels
newer than 4.1 and we have not observed any issues with the touchpad. But of
course that is quite limited testing.
Thanks,
--
Jo
Issues in meta-qt5 caused by security_flags.inc were fixed in this
round, for next round I'll test fixed 5.9.0 upgrade and then final
5.9.2 upgrade.
Thanks for fixes for QA issues, few more are included in next round.
Hopefully we'll get back to clean state before Rocko is released.
This buil
oe-core commit 51b3ee298635b11d5784caaa0ac1c8f4034c25a5
[gnome-themes-standard: Fix packages so dev-pkgs image generation
works] disabled generation of the -dev pkg. Since a libtool archive
file was no longer being picked up by the -dev pkg the build will fail
with a QA issue (if ERROR_QA includes
On Sat, Aug 26, 2017 at 1:59 PM, Martin Jansa
wrote:
> Issues in meta-qt5 caused by security_flags.inc were fixed in this round, for
> next round I'll test fixed 5.9.0 upgrade and then final 5.9.2 upgrade.
>
>
> Thanks for fixes for QA issues, few more are included in next round.
>
>
> Hopefully
Currently a task could remove a dependency needed by another task leading
to build failures, often due to missing dependencies (e.g. dynamic libraries
not being found). This was often seen for all-arch recipes in package_write_rpm.
When removing a dependency, first check that no other task active
On Mon, 2017-08-14 at 11:33 +0300, Jussi Kukkonen wrote:
> I'm seeing lots of this failure in my last build:
>
> | DEBUG: PKGWRITEDIR: /mnt/extra-ssd/tmp/work/all-poky-linux/adwaita-
> icon-theme/3.24.0-r0/deploy-rpms/noarch
> | DEBUG: SITE files ['endian-little', 'bit-32', 'common-linux',
> 'comm
Hi Bruce,
We are seeing a few teething issues which seem kernel related on the
autobuilder. The x86 lsb build saw this traceback in the logs:
Aug 24 15:49:10 qemux86 kernel: [8.965015] []
do_wp_page+0x10b/0x670
Aug 24 15:49:10 qemux86 kernel: [8.965015] [] ?
kmap_atomic_prot+0x3c/0xd0
There is no COMPATIBLE_HOST in the recipe neither it makes sense for
this to be machine specific.
Possibly, initramfs-framework's based modules may be machine specific
but if there is the case they can just RDEPENDS on
initramfs-framework-base and provide the specific module as another
recipe.
Si
13 matches
Mail list logo
