From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH 5/5] drm/i915: remove intel_pipe_set_base() (v3)
Date: Tue, 18 Nov 2014 13:25:50 -0800 [thread overview]
Message-ID: <20141118132550.528f17ca@jbarnes-hsw> (raw)
In-Reply-To: <1416276639-30297-6-git-send-email-matthew.d.roper@intel.com>
On Mon, 17 Nov 2014 18:10:39 -0800
Matt Roper <matthew.d.roper@intel.com> wrote:
> -static int
> -intel_pipe_set_base(struct drm_crtc *crtc, int x, int y,
> - struct drm_framebuffer *fb)
> -{
I'm gonna miss this old function... But on the plus side I won't
confuse pipe_set_base and set_pipe_base anymore, always got that wrong
when searching.
--
Jesse Barnes, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2014-11-18 21:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 2:10 [PATCH 0/5] i915 display refactoring Matt Roper
2014-11-18 2:10 ` [PATCH 1/5] drm: Refactor mode stereo doubling into its own function Matt Roper
2014-11-18 2:10 ` [PATCH 2/5] drm: add helper to get crtc timings (v2) Matt Roper
2014-11-18 7:56 ` Daniel Vetter
2014-11-18 8:49 ` Jani Nikula
2014-11-18 17:12 ` [PATCH 2/5] drm: add helper to get crtc timings (v3) Matt Roper
2014-11-18 20:11 ` Ville Syrjälä
2014-11-18 2:10 ` [PATCH 3/5] drm/i915: remove intel_crtc_cursor_set_obj() (v5) Matt Roper
2014-11-18 2:10 ` [PATCH 4/5] drm/i915: Don't store panning coordinates as 16.16 fixed point Matt Roper
2014-11-18 19:52 ` Ville Syrjälä
2014-11-18 2:10 ` [PATCH 5/5] drm/i915: remove intel_pipe_set_base() (v3) Matt Roper
2014-11-18 8:34 ` shuang.he
2014-11-18 20:35 ` Ville Syrjälä
2014-11-18 21:25 ` Jesse Barnes [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=20141118132550.528f17ca@jbarnes-hsw \
--to=jbarnes@virtuousgeek.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox