From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com ([192.55.52.115]:63749 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750777AbdFOGzu (ORCPT ); Thu, 15 Jun 2017 02:55:50 -0400 From: Jani Nikula To: Greg KH Cc: Eric Blau , stable@vger.kernel.org, Chris Wilson , Michel Thierry , Mika Kuoppala , Joonas Lahtinen , =?utf-8?Q?Micha=C5=82?= Winiarski , Daniel Vetter , intel-gfx@lists.freedesktop.org Subject: Re: [Intel-gfx] [PATCH] drm/i915: Do not drop pagetables when empty In-Reply-To: <20170615063123.GA32520@kroah.com> References: <20170614170728.GA30101@eric-macbookpro.localdomain> <87a859ztll.fsf@intel.com> <20170615063123.GA32520@kroah.com> Date: Thu, 15 Jun 2017 09:55:45 +0300 Message-ID: <874lvhzqmm.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: stable-owner@vger.kernel.org List-ID: On Thu, 15 Jun 2017, Greg KH wrote: > Ugh, this one flew right by me, and I never even caught it. And that > was because it was sent To: the intel-gfx list, and only had a cc: for > stable, much like all of the other i915 stable patches that you all want > in stable trees, but are not yet included in your tree. I presume this is because git send-email automatically adds Cc's from the patches, and Cc: stable is not an exception. Are you suggesting the backport should've been sent To: stable, or that we should avoid Cc'ing stable altogether when sending patches? I feel like you're having a grumpy bias towards i915, and everything about us ticks you off now. :( BR, Jani. -- Jani Nikula, Intel Open Source Technology Center