Re: Linux 6.14-rc2

[Mohan Kumar D <mkumard@nvidia.com>]

On 10-02-2025 09:43, Guenter Roeck wrote:
> External email: Use caution opening links or attachments
>
>
> On Sun, Feb 09, 2025 at 01:00:27PM -0800, Linus Torvalds wrote:
>> It's Sunday afternoon, and I'm releasing the usual regularly scheduled
>> release candidate while the rest of the US is getting ready for the
>> biggest day in TV commercials interrupted by some kind of lawn bowling
>> tournament.
>>
>> With 6.14 being a fairly small release, rc2 follows suit. It's not the
>> smallest rc2 we've had in the 6.x series, but it's definitely on the
>> smaller side.
>>
>> Nothing particularly odd stands out. The diffstat is a bit unusual
>> just because one of the bigger areas of change was some s390 kvm
>> cleanups. So the fact that s390 accounts for about a third of the
>> overall patch is certainly not very common, but it's just a result of
>> some code movement and the fact that most of the rest of rc2 really is
>> just very small fixes.
>>
>> We have a similar pattern (on a much smaller scale) wrt selftests: the
>> tests show up in the diffstat, but it's due to trivial small fixes
>> that then triggered a whole new self test to be written.
>>
>> Anyway, it all looks fine, please give it a try,
>>
> Build results:
>          total: 161 pass: 159 fail: 2
> Failed builds:
>          i386:allyesconfig
>          i386:allmodconfig
> Qemu test results:
>          total: 544 pass: 544 fail: 0
> Unit test results:
>          pass: 487271 fail: 0
>
> The i386 build failure is still
>
> x86_64-linux-ld: drivers/dma/tegra210-adma.o: in function `tegra_adma_probe':
> tegra210-adma.c:(.text+0x1322): undefined reference to `__udivdi3'
>
> The failure is triggered by commit 68811c928f88 ("dmaengine: tegra210-adma:
> Support channel page"). A fix has been submitted a while ago. See [1].
> It hasn't been applied to linux-next. I don't know the status.
> Copying those involved for feedback.
>
> Guenter
Hi, I have pushed the series 
https://lore.kernel.org/lkml/d644a35e-7dfd-4eb0-a7c3-8dae96e09657@nvidia.com/ 
to fix this issue couple of days back, still waiting to get the change 
applied. Need someone to help here.
>
> ---
> [1] https://lore.kernel.org/lkml/20250201171441.407b91cb@kernel.org/T/