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 E2CAC325704; Mon, 30 Mar 2026 21:22:06 +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=1774905727; cv=none; b=oUmGZyWuibLH557+JPrQhIXa7d1SSsbbaprGSrl/Mkj0cXlyTPamcoyArlSvMG4M6Pip7LlNPx7h7QslC8ShKlEcPl82Ftie8Z8o4xZ2XH+flqc1bUrV4NRPFUegtHyaRw0mCR4lxU0MrtRUMqwzlu+PK9n9S72jXY3ZW3MSaRM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774905727; c=relaxed/simple; bh=MEWRnboV2bNkwQiahJ5k+v6T4kmH5A38Tmwfekx5+Z8=; h=Date:From:To:Cc:Subject:Message-Id:In-Reply-To:References: Mime-Version:Content-Type; b=IfzcYS/C7hkPrCH2OdBNyak5QZjx7KVTTLCC7EZVJYyqEud+twHPDQ6TQ1phwz4CEq3qYxhS4134A/U7a6862s/DBaQ//Aa+p3bW6EcSNqpprzCgl1ksAP0u9IYwolDfXLO2FGo3ew8Z4SMU2WfEPk/0W9OyLqd9IIwX2hRDbkU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b=TlMRVBcn; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b="TlMRVBcn" Received: by smtp.kernel.org (Postfix) with ESMTPSA id DA31FC4CEF7; Mon, 30 Mar 2026 21:22:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1774905726; bh=MEWRnboV2bNkwQiahJ5k+v6T4kmH5A38Tmwfekx5+Z8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=TlMRVBcnpychpAEroWbQz7/sAYailQgoeMk8W8f0z1h/YGHYywR6Bt3lOAXDRsq0q A0jJ/r6ZD23d96zmJTcG5wWHOjnAu4ikN297Kfk3Kc6loPxpro/ziWHHloQMnFbS/P Y00IMW9Oh84qfrPXQfXH2tjBThYn173ju1hh6ZTo= Date: Mon, 30 Mar 2026 14:22:05 -0700 From: Andrew Morton To: SeongJae Park Cc: Greg KH , "Liam R. Howlett" , "# 5 . 19 . x" , David Hildenbrand , Jonathan Corbet , Lorenzo Stoakes , Michal Hocko , Mike Rapoport , Shuah Khan , Suren Baghdasaryan , Vlastimil Babka , damon@lists.linux.dev, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Roman Gushchin Subject: Re: (sashiko status) [PATCH 0/2] Docs/admin-guide/mm/damon: warn commit_inputs vs other params race Message-Id: <20260330142205.e7c7d7b47ec15a634f6eebf4@linux-foundation.org> In-Reply-To: <20260329193226.59025-1-sj@kernel.org> References: <2026032915-library-embolism-b48c@gregkh> <20260329193226.59025-1-sj@kernel.org> X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sun, 29 Mar 2026 12:32:26 -0700 SeongJae Park wrote: > On Sun, 29 Mar 2026 20:05:53 +0200 Greg KH wrote: > > > On Sun, Mar 29, 2026 at 08:49:16AM -0700, SeongJae Park wrote: > > > Forwarding sashiko.dev review status for this thread. > > > > > > # review url: https://sashiko.dev/#/patchset/20260329153052.46657-1-sj@kernel.org > > > > Why are you doing this? If we want to see the review, can't we just go > > and look at the tool itself? > > We can. But it is bit cumbersome to opening web browser and moving my focus to > there. Reading everything on the mailing tool is easier for some people like > me. Like some test bots send reports are replying to patches, or we sometimes > forwarding bugzilla reports to mailing lists in a form of a plain text mail. > > Secondly, I have to share my opinions about the reviews, as many times AI > reviews need human's opinions. There is no good way to do that on the web ui > of the tool (sashiko) for now, and I think this mail based flow is the best. I do agree with Greg that it's all a bit excessive. Thanks for your your diligence, but perhaps dial it back a bit? It's OK - we're all trying to figure out how best to utilize this tool. I view Sashiko as primarily an author tool. Sometimes I call it checkpatch++. In a better world, author would be able to sort out Sashiko issues before ever sending out the patchset. But in this world, a public send is needed to obtain that review. So what we're presently seeing is author development activity which is unfortunately and inappropriately being conducted on a public list. Personally, I pay only a little attention to author's Sashiko activity. Just enough to see whether I should pay more attention. If author says "oops, let me redo" then fine, I'll await the next spin. If author says "that was all nonsense" then fine, time to take a closer look.