From: Damien Lespiau <damien.lespiau@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/5] drm/i915: Use ilk_wm_max_level() in latency debugfs files
Date: Tue, 13 May 2014 17:51:45 +0100 [thread overview]
Message-ID: <20140513165145.GB16632@strange.amr.corp.intel.com> (raw)
In-Reply-To: <20140513164623.GP3908@phenom.ffwll.local>
On Tue, May 13, 2014 at 06:46:23PM +0200, Daniel Vetter wrote:
> On Tue, May 13, 2014 at 03:30:27PM +0100, Damien Lespiau wrote:
> > Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
>
> I prefer "expose foo" and "use foo" in the same patch. I'll squash these
> two if you're ok.
Sure, no problem. There have been a lot of these in the past, so I was
just assuming that was the unspoken way of doing it. I sure don't mind
either way.
--
Damien
next prev parent reply other threads:[~2014-05-13 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 14:30 [PATCH 0/5] Misc preparation patches Damien Lespiau
2014-05-13 14:30 ` [PATCH 1/5] drm/i915: Introduce a for_each_intel_crtc() macro Damien Lespiau
2014-05-13 14:30 ` [PATCH 2/5] drm/i915: Introduce a for_each_crtc() macro Damien Lespiau
2014-05-13 16:45 ` Daniel Vetter
2014-05-13 19:51 ` Daniel Vetter
2014-05-13 14:30 ` [PATCH 3/5] drm/i915: Expose ilk_wm_max_level() Damien Lespiau
2014-05-13 14:30 ` [PATCH 4/5] drm/i915: Use ilk_wm_max_level() in latency debugfs files Damien Lespiau
2014-05-13 16:30 ` Ville Syrjälä
2014-05-13 16:46 ` Daniel Vetter
2014-05-13 16:51 ` Damien Lespiau [this message]
2014-05-13 18:03 ` Daniel Vetter
2014-05-13 14:30 ` [PATCH 5/5] drm/i915: Don't cast void* pointers Damien Lespiau
2014-05-13 16:45 ` 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=20140513165145.GB16632@strange.amr.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=daniel@ffwll.ch \
--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 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.