From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793047218; b=J+p4ZjSTCMpCZ1O14w3JcOflXKAN1dXfJHFsUHbw6ZfP+akpql8k/GAtbRkpcWP39EK2 VVnzeVzbwqnqionqH0QX+Vf8UkTEEHX6sFPtXNllve1xoE76B9l0a9HlJuNqucZHdaIkr mTyT5LEvJNkQUp15p40kNVivmtpW/3EvGbxCxy6e6Fn/dGyW7F5RkcD+jyEzOAia+6Zbc Lj/PlW+kMp4zU3rHLNhm9Z3aRXgNmmWgFPxyoZwzP5D7Oo9JMxX2tLvCxNzbsohMrAN3e /IRvolT2OLTwPHC/og1vBoKP+3rfB+ThWcppDbQs6bMnLoR474dTsLtBXF5WR4xfqBA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793047218; h=Received:DKIM-Signature:Date:From:To:Cc:Subject:Message-ID: References:MIME-Version:Content-Type:Content-Disposition: Content-Transfer-Encoding:In-Reply-To; bh=Xu3fbCynnktpfkkN/K5x/WE6WVfufnhucl87fRAo4SE=; b=KEdq8O6ehtQU0iQZCOMiAh4Msud2UJ7+5+wCoyabfS9bBfpyX44NbHcR3VvNU10nMFni UnoFyiMaOUKiRFF1yEd6XIu9aDSUn2Inz7K3R94BFaJhWse7X0k5BycGVMMCa4pHSl/UI 9dU7ud9d6Z8BHY5Q3Wzob7q4IRNMu7sg33r/PhQQSFvfvLZjKYboZz2zIqsDX5q6PBpTN oA+7vVUOmNGaSUxsUd6xb/CDd0BKvOZ3F5t7VqGJ7FwN5MIfJ/swzz394Q29/5R4AEE7x pqANDeq2+TPIAeHkS6gmbwGJbhMJYiErDfe7Du5BiM4BIN/4BfH+YbQtPfeeaA1SHgg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=aAhmzboG; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E89D6606A31D; Mon, 26 Oct 2026 20:40:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=aAhmzboG Received: by smtp.kernel.org (Postfix) with ESMTPSA id C0A5E1F01825; Mon, 26 Oct 2026 20:40:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1793047217; bh=Xu3fbCynnktpfkkN/K5x/WE6WVfufnhucl87fRAo4SE=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=aAhmzboGmKn6SPgg9I60tpW201e6cOJ/1U7hNNdY5Hbq+R66xDfSwant0dSQ2xhm2 N8uh3H1bUhEeEinc69spsXOxUtmIaWtKygTpwiCD32vflykYssB12lejPOCshxKIJY FncmlNQyh1b/URXkhG6+s/bfxhxbszK1CPUenNHg= Date: Mon, 26 Oct 2026 21:40:16 +0100 From: Greg Kroah-Hartman To: James Hilliard Cc: Andy Shevchenko , "Maciej W. Rozycki" , Jiri Slaby , Raul E Rangel , Ilpo =?iso-8859-1?Q?J=E4rvinen?= , Heikki Krogerus , Tony Lindgren , Sebastian Andrzej Siewior , Richard Genoud , Nicolas Ferre , Alexandre Belloni , Claudiu Beznea , Jacky Huang , Shan-Chun Hung , Pali =?iso-8859-1?Q?Roh=E1r?= , Frank Li , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , Timur Tabi , linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org, linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev, linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH v5 2/5] serial: serialize asynchronous write wakeups with the port lock Message-ID: <2026102657-tubby-tragedy-5f1b@gregkh> References: <2026102631-stove-preview-b534@gregkh> X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Mon, Oct 26, 2026 at 02:24:58PM -0600, James Hilliard wrote: > On Mon, Oct 26, 2026 at 2:17 PM Greg Kroah-Hartman > wrote: > > > > On Mon, Oct 26, 2026 at 01:59:06PM -0600, James Hilliard wrote: > > > On Mon, Oct 26, 2026 at 1:53 PM Andy Shevchenko > > > wrote: > > > > > > > > On Mon, Oct 26, 2026 at 10:45:54AM -0600, James Hilliard wrote: > > > > > On Mon, Oct 26, 2026 at 3:33 AM Andy Shevchenko > > > > > wrote: > > > > > > On Sun, Oct 25, 2026 at 04:11:08PM -0600, James Hilliard wrote: > > > > > > > On Sun, Oct 25, 2026 at 2:44 PM Andy Shevchenko > > > > > > > wrote: > > > > > > > > On Sun, Oct 25, 2026 at 02:25:46PM -0600, James Hilliard wrote: > > > > > > > > ... > > > > > > > > > > > > Some people might want to test the stuff. And sending too often you actually > > > > > > > > will get the opposite results, people will be tired to even start reviewing > > > > > > > > and/or testing your code as it's changed way too quickly. > > > > > > > > > > > > > > My thought process was that people wouldn't want to be testing code that > > > > > > > had known bugs flagged in Sashiko reviews. > > > > > > > > > > > > Sashiko reviews are not visible in my or any other mailbox. To see them I have > > > > > > to go to some URL and so on, meaning to waste time to see why on the earth the > > > > > > new version has been sent. > > > > > > > > > > Maybe the Sashiko reviews are getting caught in spam filtering or something? > > > > > They are showing up for me and on the mailing list[0] so I'm a bit confused why > > > > > you aren't seeing them. You shouldn't have to go to the web interface[1] to look > > > > > up the reviews. > > > > > > > > > > [0] https://lore.kernel.org/all/sashiko-outbox-183574@kernel.org/ > > > > > > > > > > [1] https://sashiko.dev/ > > > > > > > > > > > It's better before addressing Sashiko comments, > > > > > > reply to all people involved and to Sashiko's original email, so it will be > > > > > > visible in the previous version why you issued (actually about to issue) the > > > > > > next version. > > > > > > > > > > Hmm, maybe it makes sense to enable recipients in the reply_to config[2]? > > > > > > > > It's up to the list owners / subsystem maintainers. > > > > > > > > > [2] https://github.com/sashiko-dev/sashiko/blob/v.0.6.3/projects/linux/mailing_lists.toml#L290 > > > > > > > > > > > And before even issuing it, wait for a while, people might > > > > > > disagree with Sashiko judgement or your replies on how to address that. > > > > > > > > > > I was assuming everyone was seeing the Sashiko reviews getting posted to > > > > > the mailing list already. The are ending up in lore so unless someone isn't > > > > > subscribed to the list I'm not sure why they wouldn't be seeing those reviews > > > > > already. > > > > > > > > I assume you already answered your Q. mailing list in this sense doesn't mean > > > > recipients. I think it simply goes to the mailing list without forwarding. > > > > > > Do we want those reviews going to recipients as well as the mailing list? > > > > For serial patches, we decided to only have it go to the submitter and > > the list. > > When it goes to the list is it supposed to go to list subscribers as > well or only to lore? All list subscribers as well, I've watched your interactions just fine :) thanks, greg k-h