From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752536AbcFNNAb (ORCPT ); Tue, 14 Jun 2016 09:00:31 -0400 Received: from mga14.intel.com ([192.55.52.115]:31788 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752384AbcFNNAa (ORCPT ); Tue, 14 Jun 2016 09:00:30 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,470,1459839600"; d="scan'208";a="975351019" Date: Tue, 14 Jun 2016 16:00:18 +0300 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= To: Ben Hutchings Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, akpm@linux-foundation.org, Chris Wilson , Jani Nikula , Tvrtko Ursulin , Antti =?iso-8859-1?Q?Koskip=E4=E4?= Subject: Re: [PATCH 3.16 012/114] drm/i915: Exit cherryview_irq_handler() after one pass Message-ID: <20160614130018.GV4329@intel.com> References: <20160614104709.GT4329@intel.com> <1465904254.3529.234.camel@decadent.org.uk> <20160614120825.GU4329@intel.com> <1465908527.3529.238.camel@decadent.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1465908527.3529.238.camel@decadent.org.uk> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 14, 2016 at 01:48:47PM +0100, Ben Hutchings wrote: > On Tue, 2016-06-14 at 15:08 +0300, Ville Syrjälä wrote: > > On Tue, Jun 14, 2016 at 12:37:34PM +0100, Ben Hutchings wrote: > > > On Tue, 2016-06-14 at 13:47 +0300, Ville Syrjälä wrote: > > > > On Mon, Jun 13, 2016 at 07:36:37PM +0100, Ben Hutchings wrote: > > > > > 3.16.36-rc1 review patch.  If anyone has any objections, please let me know. > > > > > > > > Do not backport this one. It'll break things. > > > > > > But this has not been re-reverted in mainline, has it?  Is it that > > > 3.16-stable would need more changes backported to make this work, or is > > > mainline currently broken on Cherryview hardware? > > > > No, as of 4.7 we have a proper fix, but it's a bit too big to backport > > (see [1]). I think 4.6.x is still busted, but Greg said he'd revert > > this broken patch there, so it should get fixed eventually. > > > > OTOH CHV wasn't even officially supported until maybe 4.1, so whatever > > you do in 3.16 shouldn't really matter. > > OK, I've dropped this. > > > It's a bit tedious having to block the same patch from different stable > > trees over and over again. It would be nice it there would be some kind > > of stable blacklist you guys could share so that we wouldn't have to > > repeat this dance with every stable maintainer... > > Sorry about that; I do try to look for things like that on the stable > list but it's too high volume for me to keep up with most of the time. I understand. Have the same problem myself often enough. Which is why I think a blacklist type of thing might be the better option. But maybe cc:stable mislabeling doesn't happen often enough to warrant it. -- Ville Syrjälä Intel OTC