All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Fix build when !CONFIG_DEBUG_FS
Date: Fri, 30 Sep 2016 16:19:02 +0300	[thread overview]
Message-ID: <87lgy9jzjt.fsf@intel.com> (raw)
In-Reply-To: <20160930131136.GK9653@nuc-i3427.alporthouse.com>

On Fri, 30 Sep 2016, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Fri, Sep 30, 2016 at 02:20:30PM +0200, Tomeu Vizoso wrote:
>> Add stub for intel_crtc_set_crc_source() and fix arguments of
>> intel_display_crc_init().
>> 
>> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
>> Fixes: 21165bd933ac ("drm/i915/debugfs: Move out pipe CRC code")
>> Fixes: 13fa0253d97a ("drm/i915: Use new CRC debugfs API")
> Reveiwed-by: Chris Wilson <chris@chris-wilson.co.uk>

Reveiwed tyop.

The commits being fixed are in drm-misc, so this needs to go in through
drm-misc as well. Daniel?

BR,
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

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Fix build when !CONFIG_DEBUG_FS
Date: Fri, 30 Sep 2016 16:19:02 +0300	[thread overview]
Message-ID: <87lgy9jzjt.fsf@intel.com> (raw)
In-Reply-To: <20160930131136.GK9653@nuc-i3427.alporthouse.com>

On Fri, 30 Sep 2016, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Fri, Sep 30, 2016 at 02:20:30PM +0200, Tomeu Vizoso wrote:
>> Add stub for intel_crtc_set_crc_source() and fix arguments of
>> intel_display_crc_init().
>> 
>> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
>> Fixes: 21165bd933ac ("drm/i915/debugfs: Move out pipe CRC code")
>> Fixes: 13fa0253d97a ("drm/i915: Use new CRC debugfs API")
> Reveiwed-by: Chris Wilson <chris@chris-wilson.co.uk>

Reveiwed tyop.

The commits being fixed are in drm-misc, so this needs to go in through
drm-misc as well. Daniel?

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2016-09-30 13:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30 12:20 [PATCH v2] drm/i915: Fix build when !CONFIG_DEBUG_FS Tomeu Vizoso
2016-09-30 12:20 ` Tomeu Vizoso
2016-09-30 13:11 ` [Intel-gfx] " Chris Wilson
2016-09-30 13:11   ` Chris Wilson
2016-09-30 13:19   ` Jani Nikula [this message]
2016-09-30 13:19     ` Jani Nikula
2016-09-30 13:53     ` Daniel Vetter
2016-09-30 13:53       ` [Intel-gfx] " Daniel Vetter
2016-09-30 14:19 ` ✗ Fi.CI.BAT: warning for drm/i915: Fix build when !CONFIG_DEBUG_FS (rev2) Patchwork

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=87lgy9jzjt.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomeu.vizoso@collabora.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.