From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 18D87449EA0; Tue, 20 Jan 2026 17:55:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768931754; cv=none; b=HPsgU6Ppg8Uh46cWUuk7fomVL7LnSCIZKhQYRIIux9IxItSnk7VGNhvSpTRba7InLOrWm6o16+vYP6ve3V53WXPie1G8HEu2skB9Muqu0WM8+WnZCog+/4pyyxJNq1uGTi9wjDhNfKlehNtYk2ne/02m8VrxaYpzeAfHZeGG+XU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768931754; c=relaxed/simple; bh=YdlHdpPvefXlQJs8q/aV3FbVwI7IGilgSt53A6aDmkI=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=TYn9iPEyZP5Jr8K9DjukhFilYAsxUQhYIjLs4rKdikQMNNIIZKJHhebP/xaczollaFd0SfkB6YtdaC622f9YZSCSuFrNIsEJZHLRUNLkfs8Z88wzGIcr8Az51Xmd7dCPrKuQLK+5RcLqmyR30b3zt2AqPZhsW8+as7jWH/beWkI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=bIJUQCEB; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="bIJUQCEB" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 50556C16AAE; Tue, 20 Jan 2026 17:55:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1768931753; bh=YdlHdpPvefXlQJs8q/aV3FbVwI7IGilgSt53A6aDmkI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=bIJUQCEBJCzX0meiRg0BArNr0wQH/PkDIgcKRlqN5FVUgdbGXbScY/M2Kl6t7xJkI FM3SOHLxeuNjfGuWw/93uJPDyqOS2xHIx0sZ94KvnpWmzlF3GrECyt+KM3kpnG9Nym n454XfYhRhtcJ2YaFbDCfvmvdSws0NqUZjO3XsD1ap0vB9i27jGIyir4cY61vAho3Z oiN+n92s81id5kCK4C7qt3jj0eGgstHImWAKUnJPj6FovBZF9Tj/j2jw2i70aojtMK P1FIWPyBkjgWTzwDWkzHa3T1ZeIFNdYxtY+A3NzxcSMRqXQfYJkiknp57mI+GktcoX +aVmU9QohPv6A== Date: Tue, 20 Jan 2026 10:55:48 -0700 From: Nathan Chancellor To: Guillaume Tucker Cc: Miguel Ojeda , David Gow , Onur =?iso-8859-1?Q?=D6zkan?= , Arnd Bergmann , linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org, linux-kbuild@vger.kernel.org, automated-testing@lists.yoctoproject.org, workflows@vger.kernel.org, llvm@lists.linux.dev Subject: Re: [PATCH v3 0/2] scripts: introduce containerized builds Message-ID: <20260120175548.GA2749368@ax162> References: <20260119213516.GA1051134@ax162> <4d4ec41f-1203-4cef-8f49-402440f3e983@gtucker.io> Precedence: bulk X-Mailing-List: workflows@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4d4ec41f-1203-4cef-8f49-402440f3e983@gtucker.io> On Tue, Jan 20, 2026 at 10:46:15AM +0100, Guillaume Tucker wrote: > Well the tuxmake LLVM image is mentioned in the first example: > > scripts/container -i tuxmake/korg-clang -- make LLVM=1 defconfig > scripts/container -i tuxmake/korg-clang -- make LLVM=1 -j$(nproc) > > So that should just work out of the box. Or did you mean to add > something else to the docs? I was just envisioning a blurb like "Additionally, TuxMake has prebuilt containers for various architectures: https://hub.docker.com/u/tuxmake" or something like that at the end of the paragraph before "To build just ``bzImage`` using Clang::" in the documentation. > But yes, the topic of available container images will be something to > expand upon once the tool starts getting used. If things go well > with this initial version then we can try and move forward with > hosting first-party images as per the other discussion thread: > > https://lore.kernel.org/all/cc737636-2a43-4a97-975e-4725733f7ee4@gtucker.io/ Yeah hopefully usage of this tool will spur some movement on that discussion thread. Cheers, Nathan