From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=198.175.65.17 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793049820; b=KmGgGLQOFy/m6cKI1JEc/KaF1c9Kfc11xIqL2d0g+r0EbmQHwC5ksUOWMMSQj5RWkomH zrN7ZT0GypzXq3KqdnTUqETcZsk1L+fpGGyejeAzFe+9LbhzFFIQ4XxI1pIFgZXlB+CBN BR0EAl5Us1S+xKdzhHHuBbt8jHKYD6M4FaL9ScdwLmstm98tHaKuRxDdCqL2mH1Wai0g4 l9Xi68VVcVkXuFxqFkCuupN0nx/ZtN217t3H8inM3AZaFB+iBe2Ui7A2+9QvwlJ8sJCy7 YV1YFcLYCdCa3hXZ0SEbf9rEPHtcofihGfZTgDNWhKZzBnmGBqg7oDp7XmjnS8T9vMw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793049820; h=DMARC-Filter:DKIM-Signature:X-CSE-ConnectionGUID:X-CSE-MsgGUID: X-IronPort-AV:X-IronPort-AV:Received:X-CSE-ConnectionGUID: X-CSE-MsgGUID:X-ExtLoop1:X-IronPort-AV:Received:Date:From:To:Cc: Subject:Message-ID:References:MIME-Version:Content-Type: Content-Disposition:Content-Transfer-Encoding:In-Reply-To: Organization; bh=mO8z9Tk1LUkxK1SfW+Zfd2chYfk05ZgjYdVW4ius1x4=; b=OnzODtKQau9xd+QDyfuFkoRPsf1Xrq0/G+DO3S1lfjzsux4Zh87crpEHCMzRG3d8Zl9O +EFXDmd7udUwrTzK2akwNw8qq5CMU4OtkkyEjQ+Pg6R5XqpHLpfEnBPorxN5moT5nrndi mVvLaekKCKwd3gf0ethljfbR2jiRusJbB/HRNM+xOpEO/FF35RITHxcdjCYi3P5P5XoWQ VBoQT1OkLaEFZXquYRazYvZ99Ge641JUY0Lx5aohRPiR1eyFglh/s2X9PS2heHxIys5eM ZULeACXExrMku2TDzdP6QJfGoFboGTq5dnT0F8Pcl5iN44yj4OQj5ClAhJ1zrFZhpFg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass header.d=intel.com header.i=@intel.com header.a=rsa-sha256 header.s=Intel header.b=eGADlttm; arc=none smtp.remote-ip=198.175.65.17 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.17]) (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 96181606A31A; Mon, 26 Oct 2026 21:23:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 96181606A31A Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=intel.com header.i=@intel.com header.a=rsa-sha256 header.s=Intel header.b=eGADlttm DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1793049820; x=1824585820; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=N88Z46/9ztkXkJPZVADk+jnnVNHd4Cz5qKxwO4LyFUo=; b=eGADlttmVdaQtl1/ExOBrnko+xSUWsU0+GGYfKmoigjDvMNpvuMg7giT UawiuBWcS17ywTdi1f+ZcvjH9qVnrxb3tGfTM/Kn0vA2hYSFtMudnr/7w G60kti9jcUM7DYFiPqlPNq8+XG4leCDCHXnkarCyx44QwwBnx9F1iCPrG XniSbXZCJZzbiG9UEKoVnub2Dcd7tvhjq/sH3Nc0JZqAe4DGLRiCx7ebv uHSlkmSwCducDE95tiOmDgzM7y0Gn5ljoiR/U98tLeRpAPFRpBwyAyRTD JMb9IJMbOmUEeSPWs+bnsznqfJHOd+otuEaX0HmBCFzrvtNlbXNmBGkEJ w==; X-CSE-ConnectionGUID: fTtxpReXT+W4gL0bvHsqIQ== X-CSE-MsgGUID: HqbyRsTJRfC3WtB1MunhqA== X-IronPort-AV: E=McAfee;i="6800,10657,11947"; a="1750932" X-IronPort-AV: E=Sophos;i="6.27,180,1787036400"; d="scan'208";a="1750932" Received: from orviesa003.jf.intel.com ([10.64.159.143]) by orvoesa109.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Oct 2026 14:23:39 -0700 X-CSE-ConnectionGUID: pGRmoMDKS5a2N1YN8eSJCw== X-CSE-MsgGUID: A8Mzj4/7QuuLmc+SWALM6A== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.27,180,1787036400"; d="scan'208";a="4325371" Received: from pgcooper-mobl3.ger.corp.intel.com (HELO localhost) ([10.245.245.93]) by smtpauth.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Oct 2026 14:23:32 -0700 Date: Mon, 26 Oct 2026 23:23:29 +0200 From: Andy Shevchenko To: James Hilliard Cc: "Maciej W. Rozycki" , Greg Kroah-Hartman , 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: References: <2026102631-stove-preview-b534@gregkh> <2026102657-tubby-tragedy-5f1b@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: Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo On Mon, Oct 26, 2026 at 02:49:24PM -0600, James Hilliard wrote: > On Mon, Oct 26, 2026 at 2:40 PM Greg Kroah-Hartman > wrote: > > 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 > > :) > > Andy, are you subscribed to the linux-serial list? I think I don't. That may explain why I don't get Sashiko in my mailbox. > I'm wondering if some mail is getting dropped, in this particular thread I never > actually received the review from Maciej W. Rozycki at > all and had to manually import the email from lore. I think that's the > only review > email that I saw go missing myself. > > That one getting dropped seems especially strange since it had a > direct reply to me. -- With Best Regards, Andy Shevchenko