Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Egbert Eich <eich@suse.de>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: fix hotplug event bit tracking
Date: Thu, 09 May 2013 13:47:33 +0300	[thread overview]
Message-ID: <87mws4jupm.fsf@intel.com> (raw)
In-Reply-To: <20130509094120.GA5892@phenom.ffwll.local>

On Thu, 09 May 2013, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Thu, May 09, 2013 at 11:47:01AM +0300, Jani Nikula wrote:
>> On Wed, 08 May 2013, Daniel Vetter <daniel@ffwll.ch> wrote:
>> > Queued for -next, thanks for the patch.
>> 
>> Shouldn't this be headed for 3.10 through -fixes?
>
> The hpd filtering is only in -next thus far. Or have I botched up my patch
> tracking again?

No, my mistake, sorry for the noise.

J.

      reply	other threads:[~2013-05-09 10:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07 12:10 [PATCH] drm/i915: fix hotplug event bit tracking Jani Nikula
2013-05-08 12:44 ` Daniel Vetter
2013-05-09  8:47   ` Jani Nikula
2013-05-09  9:41     ` Daniel Vetter
2013-05-09 10:47       ` Jani Nikula [this message]

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=87mws4jupm.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=eich@suse.de \
    --cc=intel-gfx@lists.freedesktop.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