From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Qianfeng Rong <rongqianfeng@vivo.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the i2c-host tree
Date: Fri, 4 Jul 2025 12:36:01 +1000 [thread overview]
Message-ID: <20250704123601.52101f49@canb.auug.org.au> (raw)
In-Reply-To: <bd7bf583-5c75-4e73-9672-657749a72b1a@vivo.com>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
Hi Qianfeng,
On Fri, 4 Jul 2025 10:16:08 +0800 Qianfeng Rong <rongqianfeng@vivo.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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-07-04 2:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 2:02 linux-next: build failure after merge of the i2c-host tree Stephen Rothwell
2025-07-04 2:16 ` Qianfeng Rong
2025-07-04 2:36 ` Stephen Rothwell [this message]
2025-07-04 2:50 ` Qianfeng Rong
-- strict thread matches above, loose matches on Subject: below --
2025-05-06 9:11 Stephen Rothwell
2025-05-06 11:47 ` Andi Shyti
2024-05-22 0:41 Stephen Rothwell
2024-05-22 5:33 ` Heiner Kallweit
2024-05-28 0:52 ` Stephen Rothwell
2024-05-28 1:01 ` Stephen Rothwell
2024-03-11 23:41 Stephen Rothwell
2024-03-12 10:44 ` Andi Shyti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250704123601.52101f49@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andi.shyti@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rongqianfeng@vivo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox