From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Subject: Re: [Intel-gfx] [PATCH] drm/i915/vbt: Fix VBT parsing for the PSR section Date: Wed, 31 Jul 2019 15:23:31 -0400 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 Return-path: Content-Disposition: inline In-Reply-To: <1689B7E0-5CA6-4B27-B2A8-F352618096EA@intel.com> Sender: stable-owner@vger.kernel.org To: "Vivi, Rodrigo" Cc: Rodrigo Vivi , intel-gfx , "Pandiyan, Dhinakaran" , "stable@vger.kernel.org" List-Id: intel-gfx@lists.freedesktop.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.