[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <41d95ecd-5657-8f32-cf1a-a6d249f91cd6@acm.org>
Date: Tue, 17 Aug 2021 20:07:07 -0700
From: Bart Van Assche <bvanassche@....org>
To: John Garry <john.garry@...wei.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
"Martin K. Petersen" <martin.petersen@...cle.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the scsi-mkp tree
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.
Bart.
Powered by blists - more mailing lists