linux-kernel - Re: linux-next: build failure after merge of the i2c-host tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ffac4324-66f3-4621-9300-a09ca8045bab@vivo.com>
Date: Fri, 4 Jul 2025 10:50:23 +0800
From: Qianfeng Rong <rongqianfeng@...o.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Andi Shyti <andi.shyti@...nel.org>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the i2c-host tree

Hi Stephen Rothwell，

在 2025/7/4 10:36, Stephen Rothwell 写道:
> Hi Qianfeng,
>
> On Fri, 4 Jul 2025 10:16:08 +0800 Qianfeng Rong <rongqianfeng@...o.com> wrote:
>> I'm sorry, I made a mistake,  can anyone help to roll back this patch?
>> But I want to ask if it's because I didn't compile with W=1 and
>> didn't find this compilation error locally？ Anyway, I will learn
>> from this lesson and be more careful in subsequent submissions.
> I just did an arm multi_v7_defconfig build.  Building this file depends
> on CONFIG_I2C_ST which in turn depend on ARCH_STI || COMPILE_TEST.  I
> don't use W=1.
Thank you for your feedback. I did report this problem when I compiled
locally with 'make allyesconfig'.
This was caused by my carelessness and insufficient compilation locally.
I wonder if anyone can roll back this patch in time, or I can send a
'min_t(int, ...' version to fix this compilation error immediately.

Best regards,
Qianfeng