From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 91B77C4338F for ; Wed, 18 Aug 2021 11:42:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7488361058 for ; Wed, 18 Aug 2021 11:42:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235741AbhHRLmk (ORCPT ); Wed, 18 Aug 2021 07:42:40 -0400 Received: from frasgout.his.huawei.com ([185.176.79.56]:3660 "EHLO frasgout.his.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235718AbhHRLmh (ORCPT ); Wed, 18 Aug 2021 07:42:37 -0400 Received: from fraeml710-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GqQvf30y7z6H6nx; Wed, 18 Aug 2021 19:41:02 +0800 (CST) Received: from lhreml724-chm.china.huawei.com (10.201.108.75) by fraeml710-chm.china.huawei.com (10.206.15.59) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Wed, 18 Aug 2021 13:41:59 +0200 Received: from [10.202.227.179] (10.202.227.179) by lhreml724-chm.china.huawei.com (10.201.108.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Wed, 18 Aug 2021 12:41:58 +0100 Subject: Re: linux-next: build failure after merge of the scsi-mkp tree To: Bart Van Assche , Stephen Rothwell , "Martin K. Petersen" CC: Linux Kernel Mailing List , "Linux Next Mailing List" , "linux-scsi@vger.kernel.org" References: <20210817194710.1cb707ba@canb.auug.org.au> <41d95ecd-5657-8f32-cf1a-a6d249f91cd6@acm.org> From: John Garry Message-ID: <70e483d8-39ae-3ab3-1374-96b7d2b8374a@huawei.com> Date: Wed, 18 Aug 2021 12:41:57 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: <41d95ecd-5657-8f32-cf1a-a6d249f91cd6@acm.org> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.202.227.179] X-ClientProxiedBy: lhreml748-chm.china.huawei.com (10.201.108.198) To lhreml724-chm.china.huawei.com (10.201.108.75) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 18/08/2021 04:07, Bart Van Assche wrote: > On 8/17/21 2:51 AM, John Garry wrote: >> sorry... I only built x86 and arm64 allmodconfig. Let me check this. > Build testing for tree-wide changes is tricky. You may want to use a > build bot for such testing. From > https://01.org/lkp/documentation/0-day-test-service: > > Q: Which git tree and which mailing list will be tested? How can I > opt-in or opt-out from it? > > A: 0-Day monitors hundreds of git trees and tens of mailing lists. You > can obtain detailed tree and mailing list information from the source > code under the lkp-tests/repo directory. If you want to add or remove > your tree from the 0-Day test system, send an email to the LKML, > specifying your git tree URL. Thanks for the info! Quite useful. Unfortunately there is code which has internal build switches - like qla1280.c and DEBUG_QLA1280, which Martin mentioned - so harder to spot. I suppose that's the risk with internal build switches. Thanks again, John