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 1893E1B296; Wed, 29 Nov 2023 17:45:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="KeBk4Xyg" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4BDB2C433C7; Wed, 29 Nov 2023 17:45:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1701279937; bh=KIKFPp9BUhkaU/2v9P9pMinmYm10lPKZw6CRfN0EZXc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=KeBk4XygSV3H0Is1ff9twMb+Vvnsb+6+M0b40/ajSzkslItd2N+/xFslXdoPIxyPt 7Hb2LdvV+cUc+utmT8UXA+hFN97KoFCgk5tZvcsbKxbw4f3Ybmd9Fh5857EGaBghHW G4T/giZZD88DarE3ZLYNYr3IuZB6XQDObaTajLo9qVz9LwZ88Qcl0b3Pf0+YwW787Q qXz67vU/Bfl9lhgbrgnCE0tpKC3+6jrUns53wktIfF0SYRQVkbusQdzqAYjwJap2jH 2SUnH7BPId3PoDLHiVajSo0tsKYMlNyQoSNIj6zwfkk5bCXQl27axRVNYytWYSlUuZ tbw2WyRqN6QHg== Date: Wed, 29 Nov 2023 12:45:35 -0500 From: Sasha Levin To: Pavel Machek Cc: Greg Kroah-Hartman , Ilpo =?iso-8859-1?Q?J=E4rvinen?= , stable@vger.kernel.org, patches@lists.linux.dev, LKML , torvalds@linux-foundation.org, akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org, lkft-triage@lists.linaro.org, jonathanh@nvidia.com, f.fainelli@gmail.com, sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org, allen.lkml@gmail.com, alexander.deucher@amd.com, mario.limonciello@amd.com, zhujun2@cmss.chinamobile.com, skhan@linuxfoundation.org, bhelgaas@google.com Subject: Re: [PATCH 4.14 00/53] 4.14.331-rc2 review Message-ID: References: <20231125163059.878143365@linuxfoundation.org> <2023112818-browse-floss-eb6f@gregkh> <2023112844-sesame-overdrawn-5853@gregkh> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Wed, Nov 29, 2023 at 10:00:44AM +0100, Pavel Machek wrote: >On Tue 2023-11-28 21:10:03, Greg Kroah-Hartman wrote: >> On Tue, Nov 28, 2023 at 09:48:42PM +0100, Pavel Machek wrote: >> > Hi! >> > >> > > > > > > Ilpo Järvinen >> > > > > > > RDMA/hfi1: Use FIELD_GET() to extract Link Width >> > > > > > >> > > > > > This is a good cleanup, but not a bugfix. >> > > > > > >> > > > > > > Ilpo Järvinen >> > > > > > > atm: iphase: Do PCI error checks on own line >> > > > > > >> > > > > > Just a cleanup, not sure why it was picked for stable. >> > > > > >> > > > > Just an additional bit of information, there have been quite many cleanups >> > > > > from me which have recently gotten the stable notification for some >> > > > > mysterious reason. When I had tens of them in my inbox and for various >> > > > > kernel versions, I immediately stopped caring to stop it from happening. >> > > > > >> > > > > AFAIK, I've not marked those for stable inclusion so I've no idea what >> > > > > got them included. >> > > > >> > > > Fixes tag can do it. Plus, "AUTOSEL" robot does it randomly, with no >> > > > human oversight :-(. >> > > >> > > the autosel bot has lots of oversight. >> > >> > Can you describe how that oversight works? >> >> There have been many papers and presentations about it, no need for me >> to say it all here again... > >Give a pointer. > >And explain why AUTOSEL is full of cleanups, as noticed by Ilpo, me >and others. AFAICT Sasha does not hand-check patches picked by >AUTOSEL, simply spams the mailing lists, and hopes that maintainers >will react. And they won't, because they don't understand the Awesome feedback, thanks. >implications, and simply ignore the spam. Or they will, and Sasha >simply ignores the reply. Incorrect, I just gotten tired of litigating this with *you*. How about this: instead of complaining about work you get for free, try doing it yourself and send us a list of patches that should go into the -stable tree during the next merge window. Deal? -- Thanks, Sasha