From: Jani Nikula <jani.nikula@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Eric Blau" <eblau@eblau.com>,
stable@vger.kernel.org, "Chris Wilson" <chris@chris-wilson.co.uk>,
"Michel Thierry" <michel.thierry@intel.com>,
"Mika Kuoppala" <mika.kuoppala@intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Michał Winiarski" <michal.winiarski@intel.com>,
"Daniel Vetter" <daniel.vetter@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Do not drop pagetables when empty
Date: Thu, 15 Jun 2017 09:55:45 +0300 [thread overview]
Message-ID: <874lvhzqmm.fsf@intel.com> (raw)
In-Reply-To: <20170615063123.GA32520@kroah.com>
On Thu, 15 Jun 2017, Greg KH <gregkh@linuxfoundation.org> 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
next prev parent reply other threads:[~2017-06-15 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 17:07 [Intel-gfx] [PATCH] drm/i915: Do not drop pagetables when empty Eric Blau
2017-06-15 5:51 ` Jani Nikula
2017-06-15 6:31 ` [Intel-gfx] " Greg KH
2017-06-15 6:55 ` Jani Nikula [this message]
2017-06-15 7:12 ` Greg KH
2017-06-15 7:40 ` Jani Nikula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lvhzqmm.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.com \
--cc=eblau@eblau.com \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=michal.winiarski@intel.com \
--cc=michel.thierry@intel.com \
--cc=mika.kuoppala@intel.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).