From: Jani Nikula <jani.nikula@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: intel-gfx@lists.freedesktop.org, stable@vger.kernel.org,
Eric Blau <eblau@eblau.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: [PATCH] drm/i915: Do not drop pagetables when empty
Date: Thu, 15 Jun 2017 10:40:09 +0300 [thread overview]
Message-ID: <87tw3hya06.fsf@intel.com> (raw)
In-Reply-To: <20170615071251.GB1843@kroah.com>
On Thu, 15 Jun 2017, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Thu, Jun 15, 2017 at 09:55:45AM +0300, Jani Nikula wrote:
> The backport should have been "To:" stable, otherwise it really just
> looks like any other patch sent to the intel-gfx list, right?
>
> But I understand, I'm not grumpy about this one, thanks for the
> reminder, I'm glad to have backports and patches explicitly called out
> like this.
Thanks for the clarification, and for picking the patch up now.
>> I feel like you're having a grumpy bias towards i915, and everything
>> about us ticks you off now. :(
>
> No, this one didn't at all, I was trying to apologize :)
Auch, does my negative reading of your mail mean I have a reverse grumpy
bias about you instead?! :)
> Only thing that makes me grumpy is all of the commits in the tree that
> don't apply at all as they are coming in through multiple
> trees/branches, like I have mentioned before. I would _love_ a list of
> patches I should be taking, or some kind of hint, to help me out here,
> as it is, the current workflow you all have right now isn't working for
> me at all.
It's sad because the workflow really does work well for *us*. But we
hear you, and we haven't forgotten about your complaints. We'll figure
this out.
Thanks,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-06-15 7:40 UTC|newest]
Thread overview: 7+ 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
2017-06-15 7:12 ` Greg KH
2017-06-15 7:40 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-26 8:29 Daniel Vetter
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=87tw3hya06.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@intel.com \
--cc=eblau@eblau.com \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--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).