From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=18.9.28.11 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1792442192; b=J9dW1gWd99QBab+SOBzAEW6I9ShlFKRbBPaRF8cJy8zhEkj+gvYwX5eFdK84maDZNGAq O2INowHGr86JsYhGEcf8iZ8x5A2GTdFyEXrM9zinxANxBW1JAnUx9EZxV+EUI2cRlAi37 mb+JK9I/B9zGULFmHvxRh9hSLzd5Qd80b+WUfQOuantMlX0NrgdBmpufhUyRV3NEOZF6Q e2Hrf1OFW8WOEBXvu/b0TU0mn7rf/ZX/mEwHHRwepYZcwKJs4ozf63RwO7JR8KTt79xZA gL0jrBHLRLnu5O7sZiAxAixPkTXoVarPQp5Kd13brud5gc881iJaVXHPBvCmnitfiBw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1792442192; h=DMARC-Filter:Received:DKIM-Signature:Received:Date:From:To:Cc: Subject:Message-ID:References:MIME-Version:Content-Type: Content-Disposition:In-Reply-To; bh=B6FtEfAfSM20kF3gL1QXFqVXMDj00WWmcxMKnNYkW/8=; b=gWTITLLGwXKLea7vRpILR8fyHBv/0sBueLpkNZ5jpqnhPBy7FCoq7OtGpSdeunzqkL5A MuteIdaZ0dqezDvQaYjTzeDoDHIdWg/Ibu+bNMxry/l88IEuri43mNZx4389m3DlzdMeK 5dM/+iPIX2VCu722bSM8pFPy1BPqdyDNxVa/kPZgIAbNBjzRTBI1qqU2JFN5s7BnKRNVl DoBu7r729TCV4qUY20tiRgJG3OUwuUNRzVoeYU0LarBvHC8YkxYwBv45f9H3w8dfZOJEu ANcy/xs4bCtnXVqGz3/CN/OtRN77FfXCoLSvLpJ0f1G67uqVSVfLxpMMJoqVk9HZ/4w== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=mit.edu; spf=pass smtp.mailfrom=mit.edu; dkim=pass header.d=mit.edu header.i=@mit.edu header.a=rsa-sha256 header.s=outgoing header.b=KgYYjjQC; arc=none smtp.remote-ip=18.9.28.11 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2CD6C606A31C for ; Mon, 19 Oct 2026 20:36:32 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 2CD6C606A31C Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=mit.edu Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=mit.edu Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=mit.edu header.i=@mit.edu header.a=rsa-sha256 header.s=outgoing header.b=KgYYjjQC Received: from macsyma.thunk.org (pool-173-48-113-115.bstnma.fios.verizon.net [173.48.113.115]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 69JKaNJZ029714 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 19 Oct 2026 16:36:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1792442185; bh=B6FtEfAfSM20kF3gL1QXFqVXMDj00WWmcxMKnNYkW/8=; h=Date:From:Subject:Message-ID:MIME-Version:Content-Type; b=KgYYjjQCsxUjZjuavPKuhRQn5TSUT2npd4i3Sj4VGAu2Td7a43acy2Sd0nPdGryQS Q/T22Lgc/NM9POcuJXBJr8JlK4++jNhQrl2BvbFXYpOAo9hMn0oiJ78JqLdQDYcbcA p2Rw+eIi2jFtOsZJN9E9LvV0VKZ7mJpJo72FtR9j2pjA6xKqwBeTWu1vjQhbQz2/EW T3Lj1DURkqZmZHCnIaXG/WbmEbF8Qumdn1qDjQJntHOKsM89FtTmOic9WSJmo8hAIA XRKEwiBSxsNKi2ZiE3Of0/ULDlkmzfCMx/3aB3rkaexd2YCkdm5/11S21kN7VbDDG9 v6M5in5i80Ajg== Received: by macsyma.thunk.org (Postfix, from userid 15806) id 198FE219F1C1; Mon, 19 Oct 2026 16:35:23 -0400 (EDT) Date: Mon, 19 Oct 2026 16:35:23 -0400 From: "Theodore Tso" To: Shuah Khan Cc: Krzysztof Kozlowski , Jiri Kosina , ksummit@lists.linux.dev, sashiko@lists.linux.dev Subject: Re: Patch pre-submission to Sashiko Message-ID: References: <350c7564-a833-4dd4-abf3-b8488280b0fa@kernel.org> X-Mailing-List: sashiko@lists.linux.dev List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Mon, Oct 19, 2026 at 11:53:27AM -0500, Shuah Khan wrote: > > When a submitter uses LLMs to generate a patch, it is reasonable for > maintainers and reviewers to ask them to use shashiko to find problems > before sending it to us. Asking for a shashkiko run before submitting > patches could become part of the patch submitting process. > > How about updating the submitting patches document to add a section on > this with instructions on how to run it? > > This shifts the responsibility to run shashiko to people using LLMs. If people are using LLM's to generate a patch, it would be useful if we can make it super easy for LLM's to call out to Sashiko as an sub-agent. We would probably want to make it easier for LLM's to run our kunit and selftests as well. Basically, we want to push the work to the submmiter, instead of expecting the maintainer and/or reviewers to do that work --- especially since if it's in the agenting coding loop, the LLM agent can fix the problem more quickly and without burning human review time. - Ted