From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3 1/3] drm/i915/csr: keep firmware name and required version together
Date: Wed, 26 Sep 2018 16:41:40 +0300 [thread overview]
Message-ID: <878t3otlyj.fsf@intel.com> (raw)
In-Reply-To: <153796915298.22836.8320862918219114683@skylake-alporthouse-com>
On Wed, 26 Sep 2018, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2018-09-26 14:34:12)
>> Having two separate if ladders gets increasingly hard to maintain. Put
>> them together.
>>
>> v2: Rebase
>>
>> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> # v1
>
> Didn't spot anything wrong in the revisions, so keep the r-b on both
> patches.
Thanks for the quick check; I'll push once the CI overlords give me the
green light.
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:[~2018-09-26 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 13:34 [PATCH v3 1/3] drm/i915/csr: keep firmware name and required version together Jani Nikula
2018-09-26 13:34 ` [PATCH v3 2/3] drm/i915/csr: keep max firmware size together with firmare name and version Jani Nikula
2018-09-26 13:34 ` [PATCH v3 3/3] drm/i915/csr: bypass firmware request on i915.dmc_firmware_path="" Jani Nikula
2018-09-26 13:39 ` [PATCH v3 1/3] drm/i915/csr: keep firmware name and required version together Chris Wilson
2018-09-26 13:41 ` Jani Nikula [this message]
2018-09-27 6:29 ` Jani Nikula
2018-09-26 14:14 ` ✗ Fi.CI.SPARSE: warning for series starting with [v3,1/3] " Patchwork
2018-09-26 14:35 ` ✓ Fi.CI.BAT: success " 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=878t3otlyj.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;
as well as URLs for NNTP newsgroup(s).