From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [213.167.242.64]) (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 D0F803B7769 for ; Wed, 15 Jul 2026 08:00:08 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.167.242.64 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784102411; cv=none; b=eTBtMkeQBeXNUb8t9/dm3IEIRMSQl02IuKrop82xYbsfLucb3FUiIpjTVggE4jEZEgU+HqMT6Nak45EJfZn+SGzjBOBup3c2bq93GJgim2AZEeosmLIp/e1ip/fOu87/9FtK96ZqaRG53TbyOLTDXvlM7wFQOG19SR7OlpkKxfw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784102411; c=relaxed/simple; bh=aGZbtUuBkoHZ3MAiW7ZdWe10h1VjA7JCip+nkcJtWw4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=P+81/1PjPkLqAGwcRTDZV2Lvz4ZhgP4PB5w3AT9BE2ue1XvAKweCan11tv/uYJY/g/ndD9QD0Pxp3SaE0qwJk7rdlucG490e1p2JuSoofp2ZRIR0qtowzLKB3GIvf18T4s3SuFH9d6DvCmwjGkkL4WnHTDKcStykdqealTCAqvk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=ideasonboard.com; spf=pass smtp.mailfrom=ideasonboard.com; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b=QgPxBMCJ; arc=none smtp.client-ip=213.167.242.64 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b="QgPxBMCJ" Received: from ideasonboard.com (93-46-82-201.ip106.fastwebnet.it [93.46.82.201]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 1DB71104C; Wed, 15 Jul 2026 09:59:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1784102346; bh=aGZbtUuBkoHZ3MAiW7ZdWe10h1VjA7JCip+nkcJtWw4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=QgPxBMCJZlRwQnLSbxfwQVA5VH4LB0G06ioG5gNxksxZxkNFcyGBS7SYH/5p7/a6y Tu0SaPfqCGMvmQzNTlW4CLZg6k6I5J01NTriWT1n75YU6Ql5WDF4/0rBYhw3yyWspr k/gTQoIx2VbiVsLlFv0pc7fqVVZGJTn10p6AQjA8= Date: Wed, 15 Jul 2026 09:59:57 +0200 From: Jacopo Mondi To: Roman Gushchin Cc: Laurent Pinchart , Mauro Carvalho Chehab , Derek Barbosa , Matthieu Baerts , Konstantin Ryabitsev , Jason Gunthorpe , Steven Rostedt , users@kernel.org, Linux Media Mailing List , Stephen Finucane Subject: Re: Linking Patchwork with Sashiko? Message-ID: References: <20260715005909.GF1656185@killaraus.ideasonboard.com> <4928C919-7999-4E76-ADCB-F8643FED105B@linux.dev> Precedence: bulk X-Mailing-List: linux-media@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4928C919-7999-4E76-ADCB-F8643FED105B@linux.dev> Hi Roman On Tue, Jul 14, 2026 at 07:00:54PM -0700, Roman Gushchin wrote: > > On Jul 14, 2026, at 5:59 PM, Laurent Pinchart wrote: > > > > On Tue, Jul 14, 2026 at 10:55:42PM +0000, Roman Gushchin wrote: > >> Mauro Carvalho Chehab writes: > >>>> On Mon, 13 Jul 2026 12:41:20 +0300 Laurent Pinchart wrote: > >>>>>>> Individuals can set their > >>>>>>> spam filters up if they don't want to get these emails, I can't control > >>>>>>> it. Providing individual authors an option "I don't want my patches > >>>>>>> to be reviewed" sound strange to me. It's like "I don't want my patches > >>>>>>> to be tested by unit tests". > >>>>>> > >>>>>> I agree with you, and, on my head, not sending e-mails to the author > >>>>>> is a clear violation to one of the most basic net etiquette rule on > >>>>>> mailing lists: any replies to posts there should reach the author. > >>>>> > >>>>> I don't know where that one comes from. > >>>>> > >>>>> What happened to this other "most basic rule" that subscription to > >>>>> services that deliver e-mails should be opt-in ? > >>> > >>> Replying to an e-mail is not subscribing to a service. It is the > >>> author's right to know if one replies publicly to his e-mails. > >>> Explicitly removing him from the C/C of such replies is a violation > >>> of his rights. > >>> > >>> On other words, it is implicit that, if you post an e-mail, you'll be > >>> expecting actions or answers to it. > >>> > >>> Now, if one really doesn't really want to receive e-mails from a > >>> particular sender, a block list solves it. Alternatively, a way to > >>> opt-out is welcomed. > >>> > >>> See, this is different than adding someone to a mailing list without > >>> his consent: On such case, people receive e-mails unrelated to their > >>> preferences. For those, opt-in is the right net etiquette. > >> > >> I agree with this. > >> > >> But also just practically: if someone who opted out from sashiko emails > >> posts a patch and sashiko finds say a critical issue, do we expect the > >> maintainer to go and manually check each time whether the author opted > >> out and forward the review? > > > > I expect maintainers who want to act on sashiko reviews to triage and > > verify them first before bothering authors, yes. I believe we should > > follow the first two recommendations of the Software Freedom Conservancy > > on using LLM-backed generative AI systems for FOSS contributions ([1]). > > > > [1] https://sfconservancy.org/llm-gen-ai/llm-backed-generative-ai-recommendations.html > > I think it makes the point of sashiko - helping maintainers - unachievable. If the point to not use > LLMs in general, let’s discuss this, not how to make each use case more complex. > Having been in the discussion within the media group, let me try to re-express here the point I made within that circle already. The decision to not send Sashiko replies to developers but rather have them sent to a different mailing list, has been suggested because, after a brief interim period where Sashiko reviews has been sent to the main mailing list, it has caused more load for maintainers, not less. Far-fetched review comments, very convincing word salads mixed with valuable findings have often been escalated by authors to maintainers to have them distil the good from the bad. This might have merits: analyzing 3 false reports to find a bug is still worth it, but has so far caused more load for maintainers and reviewers, not less. Considering reviewers are the most scarce resource we have, analyzing Sashiko reports has been made an opt-in feature by sending its review to a dedicated mailing list where maintainers can (optionally) decide if something's worth acting upon. This would also give some buffer time to evaluate Sashiko and maybe reconsider later on. > It seems like [1] expresses a very anti-LLM position in general, which I can understand and I agree > with some of concerns. But I think it’s up to project leaders to decide if Linux in general takes this > position and my take so far is that the answer is not. > All discussions around AI inevitably ends being about principles and good vs bad. I'm surprised Linus and Ted had to weight in to re-state the "we're not against AI!" principle while I would like to discuss signal-to-noise metrics instead. Maybe you have number I've not seen yet. Thanks j > Thanks