From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) (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 3F9CE212560 for ; Wed, 8 Oct 2025 20:37:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=156.67.10.101 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1759955878; cv=none; b=Lq+q5cV93ByMmKDEvfIaApfiaVWoebEXHvZqssCHBcFbUCeUXfB7k/bNZz3V5aE9rU/xYBhQhtM2IPQqGtX3N6SvZ0bZTA7VhhOHVJ6myp6UNLFzH8M4n4r2CckQNCNfBBFjq21/m9/f+Zj3OLAyRJHvSzwsctmImovbO6gr5nY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1759955878; c=relaxed/simple; bh=Gnot31WV6Rf6UwO1lyaZdKvq8BytFWacetNeQork5qY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=X6gAWUgv5HsStcxHGlVWNS7AEyTfI/TB3zIFxgd+N87eITontFlFniuPNz6G0YEteWN6BEpsqeI0xgRGtx9fB5t6HL4yZe84rKInEBgrKAeDlV4wBRixdULrfAhRwDvT3jQ3bPVElZCWAW8t3yODPff69m5/ffSHOlka1nYFpXc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch; spf=pass smtp.mailfrom=lunn.ch; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b=Fu4v/LEH; arc=none smtp.client-ip=156.67.10.101 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lunn.ch Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="Fu4v/LEH" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=uOtBgy59neRwzlFN7vRpeDS9F6fy/XHcekh+X9rM7j4=; b=Fu4v/LEHTtQvxF+1M+VZp87a6Z FKqmHc3yaf20n53vyb+DRPO9+sHsliF92O3eHk7QsQsW7rps//Up9BwWMV+J8BnGtOxHcqwT0bi4f ZwT5Fyyv/K0zy+uLogdXOTMvuhLp/zf2BHvhmv59624llEY+GIKPX3ti+g+dQLaWPxHE=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1v6av1-00ATg6-PT; Wed, 08 Oct 2025 22:37:51 +0200 Date: Wed, 8 Oct 2025 22:37:51 +0200 From: Andrew Lunn To: Laurent Pinchart Cc: Chris Mason , ksummit@lists.linux.dev, Dan Carpenter , Alexei Starovoitov , Rob Herring Subject: Re: [MAINTAINERS / KERNEL SUMMIT] AI patch review tools Message-ID: <2c04a89f-abd5-48c6-abfc-2e71d24e913f@lunn.ch> References: <20251008192934.GH16422@pendragon.ideasonboard.com> Precedence: bulk X-Mailing-List: ksummit@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20251008192934.GH16422@pendragon.ideasonboard.com> > This raises the interesting and important question of how to get patch > submitters to follow a recommended workflow. We routinely get patches > that produce checkpatch errors that are clearly not false positives. > Rob Herring implemented a bot to run checks on device tree bindings and > device tree sources because lots of patches fail those checks. I'm sure > there are lots of other examples that have led maintainers to automate > checks on the receiver's side, through various types of standard CIs or > hand-made solutions. Submitters should run more tests, how to get them > to do so is a broader question. The netdev CI tooling is available from github. You can run it as a docker image. So it is possible for a netdev developer to run the same tests as netdev Maintainers do. Maybe we need more subsystems to make their CI tooling available to their developers so they can be run locally? It has also been pointed out elsewhere, b4 is gaining more testing capabilities. We should keep building this out, making subsystem tooling more subsystem specific, while b4 can do all the standard stuff we expect all developers to do before submission. Andrew