On 2018-03-05 4:01 AM, Liwei Song wrote:
For linux-yocto-4.12
merged to standard/base -> BSPs.
Bruce
Thanks,
Liwei.
On 03/05/2018 04:53 PM, Liwei Song wrote:
From: Rodrigo Vivi
commit eb371933cf4d3495d0899880b2e0e252ce9db517 upstream.
Coffee Lake CPU on Kaby Lake PCH is possible.
It do
merged.
Bruce
On 2018-03-03 9:03 PM, Victor Kamensky wrote:
Need to enable CONFIG_KERNEL_DEBUG in systemtap feature, otherwise
CONFIG_DEBUG_INFO set by systemtap.cfg does not have any effect since
it depends on CONFIG_KERNEL_DEBUG and is set off in resulting config.
So systemtap cannot find DWA
On 2018-03-01 9:17 PM, Liwei Song wrote:
Hi Bruce,
These are two upstream patches to fix kmemleak(patch1) and build
warning(patch2) for yocto-4.12 kernel.
merged.
Bruce
Thanks,
Liwei.
Mikulas Patocka (1):
brd: remove unused brd_mutex
Shu Wang (1):
audit: fix memleak in auditd_send
This is now merged.
Given the description, I merged it to 4.12, 4.14 and 4.15. If
the 4.14/4.15 merge is invalid, let me know so I can revert.
Bruce
On 2018-02-28 8:44 PM, Dengke Du wrote:
From: "Kexin(Casey) Chen"
Forward port linux-yocto-4.8's patch to fix the build warning.
http://
On 03/05/2018 10:51 AM, Bruce Ashfield wrote:
> On 2018-03-04 7:34 PM, Armin Kuster wrote:
>> This series includes the lsb runqemu kvm boot issue [ Yocto #12570 ],
>> Spectre v1 and misc bug fixes 4.4 backports.
>>
>> The following changes since commit
>> 1368b7448d693cedb384f6e0b9a0237adb1b8259:
On 2018-03-04 7:34 PM, Armin Kuster wrote:
This series includes the lsb runqemu kvm boot issue [ Yocto #12570 ],
Spectre v1 and misc bug fixes 4.4 backports.
The following changes since commit 1368b7448d693cedb384f6e0b9a0237adb1b8259:
kaiser: x86: Fix NMI handling (2018-02-22 12:18:09 -0800)
For linux-yocto-4.12
Thanks,
Liwei.
On 03/05/2018 04:53 PM, Liwei Song wrote:
> From: Rodrigo Vivi
>
> commit eb371933cf4d3495d0899880b2e0e252ce9db517 upstream.
>
> Coffee Lake CPU on Kaby Lake PCH is possible.
> It does exist, and it does work.
>
> The only missed case was this warning here
From: Rodrigo Vivi
commit eb371933cf4d3495d0899880b2e0e252ce9db517 upstream.
Coffee Lake CPU on Kaby Lake PCH is possible.
It does exist, and it does work.
The only missed case was this warning here noticed
by Wendy who could get one system with this configuration
and reported the issue for us:
Backport an upstream patch,
fix the following kernel warnning on CoffeeLake + KabyLake PCH board:
[3.689176] WARN_ON(!((dev_priv)->info.platform == INTEL_SKYLAKE) &&
!((dev_priv)->info.platform == INTEL_KABYLAKE))
[3.689191] [ cut here ]
[3.690301] WARNING: CPU