From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 476DFC32751 for ; Wed, 31 Jul 2019 19:23:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 151CD208E4 for ; Wed, 31 Jul 2019 19:23:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564601014; bh=Y2Pz74QYqGGC1hOcZt1OKTgO0goLWg57a6iQRfF+1Kw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=lNuraftnxbZeq4m3/XBWxAmNBAsQTv8tzRf8p+/ASfBqkUrKrJByzlL3gS3sANCsY 12jq6R7N2ayfUMShYEvvV3Zg4yu6pAeoakenpIFjx9NYzDzTjknGEgVyvmmVAgz7BS p3wb4vhdCP/e5M8Ky07NFgKWkl1rf9lo6wr16Lss= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730873AbfGaTXd (ORCPT ); Wed, 31 Jul 2019 15:23:33 -0400 Received: from mail.kernel.org ([198.145.29.99]:33756 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730870AbfGaTXd (ORCPT ); Wed, 31 Jul 2019 15:23:33 -0400 Received: from localhost (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id D4032208E4; Wed, 31 Jul 2019 19:23:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564601013; bh=Y2Pz74QYqGGC1hOcZt1OKTgO0goLWg57a6iQRfF+1Kw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=NMQDgh1hqFQzzLdCjRq/hLpLWq2U4IIa2H5rpTrVcjyfsysDSRcIYfFfM0OpHVqiS DqSajvRGX6Wwp+u2ME7ta1aPHoUABht0Vly1raA+Epsveadsdpx2pEc/XL0Jf/SjEa YXoUWobDFvjp8HTJj7maSrVoT/CItZnQYjSyGB0g= Date: Wed, 31 Jul 2019 15:23:31 -0400 From: Sasha Levin To: "Vivi, Rodrigo" Cc: Rodrigo Vivi , intel-gfx , "Pandiyan, Dhinakaran" , "stable@vger.kernel.org" Subject: Re: [Intel-gfx] [PATCH] drm/i915/vbt: Fix VBT parsing for the PSR section Message-ID: <20190731192331.GA17697@sasha-vm> References: <20190717223451.2595-1-dhinakaran.pandiyan@intel.com> <20190719004526.B0CC521850@mail.kernel.org> <20190730214851.GF29162@sasha-vm> <1689B7E0-5CA6-4B27-B2A8-F352618096EA@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <1689B7E0-5CA6-4B27-B2A8-F352618096EA@intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Wed, Jul 31, 2019 at 05:14:38PM +0000, Vivi, Rodrigo wrote: >> On Jul 30, 2019, at 2:48 PM, Sasha Levin wrote: >> rather >> than a few weeks later when Greg sends his "FAILED:" mails and gets >> ignored because said folks have moved on. > >however this could potentially cause extra work and confusion like we can see on this >thread where the developer immediately responded to your email and sent the >backported patch to the stable mailing list. > >Maybe it is just because we are used to Greg's failed to apply email or maybe >it was just a matter of education... I think that there were a few things here that ended up causing confusion, but I'm not quite sure how to address them. I think that stable should have a clearer rules as to how backports should be sent. Right now we weed through mails to stable@ to figure out what are backport requests, what are upstream patches, and what are just confused folks. We have gotten pretty good at this, but still not perfect... >But I wonder if there isn't something that could be improved on the automated >message here. Some message clearly stating: > >- No action required at this point One *could* send a backport at this point. My understanding is that when Greg sees a failure to apply a commit tagged for stable he'll grep through his mailbox, hopefully finding the backport as a result of this bot bugging people. >- you can work to prepare the backport in advance >- don't send it to stable before requested by Greg Why not? I think it's fine to put it on the mailing list, specially under the same thread, and let us deal with it after the patch goes upstream. -- Thanks, Sasha