In message: [linux-yocto] [linux-yocto std&preemp-rt kernel v6.6]: nxp-s32g:
pinctrl: s32cc: use devm_kzalloc() to alloc pinctrl_desc struct to avoid random
value
on 09/07/2024 Zhantao Tang wrote:
> Hi Bruce,
>
> There is a patch for v6.6 kernel to fix one pinctrl issue.
> Would you please help
merged.
Bruce
In message: [linux-yocto][linux-yocto
v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc &
v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH] irq: imx: irqsteer: Unset
data->domain->dev
on 05/07/2024 Xulin Sun wrote:
> The irq_domain::dev is used for power management purposes relat
In message: [linux-yocto][linux-yocto v6.1][PATCH 0/1] Backport patch to fix
CVE-2024-38541
on 04/07/2024 Xiangyu Chen via lists.yoctoproject.org wrote:
> From: Xiangyu Chen
>
> Hi Bruce,
>
> Recently, the CVE-2024-38541's source up to 9.8-critical[1], upstream already
> fixed it,
> but the o
Hi Bruce,
There is a patch for v6.6 kernel to fix one pinctrl issue.
Would you please help to merge it to the following branches?
v6.6/standard/nxp-sdk-6.6/nxp-s32g
v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-s32g
Thanks,
Zhantao
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all mess
For S32G, the num_custom_params for pinctrl desc struct should be 0,
because there is no driver-specific custom parameters at all.
But if this member is not set to 0 explicitly, the value may be a
unexpected random value, which may cause the following boot failure:
[ cut here ]--
