All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Damien Lespiau <damien.lespiau@intel.com>,
	"He, Shuang" <shuang.he@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 9/9] drm/i915: Make all plane disables use
Date: Fri, 28 Nov 2014 14:55:42 +0200	[thread overview]
Message-ID: <87oarro569.fsf@intel.com> (raw)
In-Reply-To: <20141128122127.GA2695@strange.ger.corp.intel.com>

On Fri, 28 Nov 2014, Damien Lespiau <damien.lespiau@intel.com> wrote:
> Hi,
>
> So References: is now in the new replies, but that's still not enough to
> make threading work in gmail.
>
> Maybe truncating the subject is the cause then? Headers can be
> multi-lines and you're only taking the first line. For instance:
>
> Subject: [Intel-gfx] [PATCH] drm/i915: Disable FBC if primary plane is
> 	rotated on Haswell
>
> The Subject header carries over a second line, while your script only
> takes the first. Can we try to fix that and see if it then threads
> properly?

Arguably gmail is broken in this sense, but the subject changing is the
likely culprit here.

http://mid.gmane.org/87fvd83ooi.fsf@intel.com


BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2014-11-28 12:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 19:52 [PATCH 0/9] i915 display refactoring (v3) Matt Roper
2014-11-24 19:52 ` [PATCH 1/9] drm: add helper to get crtc timings (v4) Matt Roper
2014-11-27 14:19   ` [Intel-gfx] " Ander Conselvan de Oliveira
2014-11-24 19:52 ` [PATCH 2/9] drm/i915: remove intel_crtc_cursor_set_obj() (v5) Matt Roper
2014-11-24 19:53 ` [PATCH 3/9] drm/i915: remove intel_pipe_set_base() (v4) Matt Roper
2014-11-27 14:20   ` Ander Conselvan de Oliveira
2014-11-24 19:53 ` [PATCH 4/9] drm/i915: Introduce intel_prepare_cursor_plane() Matt Roper
2014-11-28 12:15   ` Ander Conselvan de Oliveira
2014-11-28 13:12     ` Ander Conselvan de Oliveira
2014-11-28 18:10     ` Daniel Vetter
2014-12-01  8:26   ` Ander Conselvan de Oliveira
2014-11-24 19:53 ` [PATCH 5/9] drm/i915: Make intel_plane_state subclass drm_plane_state Matt Roper
2014-11-24 19:53 ` [PATCH 6/9] drm/i915: Consolidate plane 'prepare' functions Matt Roper
2014-11-28 13:00   ` Ander Conselvan de Oliveira
2014-12-01  8:29   ` Ander Conselvan de Oliveira
2014-12-01 21:25     ` Matt Roper
2014-11-24 19:53 ` [PATCH 7/9] drm/i915: Consolidate plane 'cleanup' operations Matt Roper
2014-12-01 13:46   ` Ander Conselvan de Oliveira
2014-11-24 19:53 ` [PATCH 8/9] drm/i915: Consolidate top-level .update_plane() handlers Matt Roper
2014-11-24 19:53 ` [PATCH 9/9] drm/i915: Make all plane disables use 'update_plane' Matt Roper
2014-11-25  7:39   ` [PATCH 9/9] drm/i915: Make all plane disables use shuang.he
2014-11-27 15:57     ` Damien Lespiau
2014-11-28  0:53       ` He, Shuang
2014-11-28 12:21         ` Damien Lespiau
2014-11-28 12:55           ` Jani Nikula [this message]
2014-12-01 14:04   ` [PATCH 9/9] drm/i915: Make all plane disables use 'update_plane' Ander Conselvan de Oliveira
2014-12-01 16:46     ` 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=87oarro569.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=damien.lespiau@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=shuang.he@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.