From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 3/3] drm/i915: move watermark structs more towards usage
Date: Mon, 02 Mar 2020 14:14:52 +0200 [thread overview]
Message-ID: <87v9nnosw3.fsf@intel.com> (raw)
In-Reply-To: <158287816601.19174.1174685946100420568@skylake-alporthouse-com>
On Fri, 28 Feb 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2020-02-27 17:00:47)
>> Shrink i915_drv.h a bit by moving watermark structs where they are
>> needed.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Series is
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Thanks, pushed 1-2 to dinq, will need to rebase 3.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-02 12:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 17:00 [Intel-gfx] [PATCH 1/3] drm/i915: add i915_ioc32.h for compat Jani Nikula
2020-02-27 17:00 ` [Intel-gfx] [PATCH 2/3] drm/i915: remove unused orig_clock i915 member Jani Nikula
2020-02-27 17:00 ` [Intel-gfx] [PATCH 3/3] drm/i915: move watermark structs more towards usage Jani Nikula
2020-02-28 8:22 ` Chris Wilson
2020-03-02 12:14 ` Jani Nikula [this message]
2020-03-03 10:46 ` Jani Nikula
2020-02-27 20:48 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915: add i915_ioc32.h for compat Patchwork
2020-02-27 21:11 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-02-28 8:05 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915: add i915_ioc32.h for compat (rev2) Patchwork
2020-02-28 8:53 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-02-29 20:10 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=87v9nnosw3.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--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