From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ian W MORRISON <ianwmorrison@gmail.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: "Srivatsa\, Anusha" <anusha.srivatsa@intel.com>, "Vivi\,
Rodrigo" <rodrigo.vivi@intel.com>, "Wajdeczko\,
Michal" <Michal.Wajdeczko@intel.com>,
Greg KH <gregkh@linuxfoundation.org>,
"airlied\@linux.ie" <airlied@linux.ie>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable\@vger.kernel.org" <stable@vger.kernel.org>,
"intel-gfx\@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel\@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake
Date: Fri, 20 Apr 2018 10:50:40 +0300 [thread overview]
Message-ID: <87o9iee2pb.fsf@intel.com> (raw)
In-Reply-To: <CAFXWsS8o72qgO419muew4ei3VgorYWmGq0k=xPNe1es3DmD0gw@mail.gmail.com>
On Fri, 20 Apr 2018, Ian W MORRISON <ianwmorrison@gmail.com> wrote:
> I've performed backport testing and some additional analysis as follows:
What testing did you do beyond booting? Did you run igt?
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2018-04-20 7:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 4:42 [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake ianwmorrison
2018-04-11 9:24 ` Jani Nikula
2018-04-11 10:41 ` Ian W MORRISON
2018-04-11 12:27 ` Jani Nikula
2018-04-11 13:04 ` Ian W MORRISON
2018-04-16 22:47 ` Srivatsa, Anusha
2018-04-17 9:02 ` Jani Nikula
2018-04-17 14:14 ` Joonas Lahtinen
2018-04-20 5:47 ` Ian W MORRISON
2018-04-20 7:50 ` Jani Nikula [this message]
2018-04-20 8:25 ` Ian W MORRISON
2018-04-20 18:03 ` Rodrigo Vivi
2018-04-20 18:30 ` Srivatsa, Anusha
2018-04-21 1:22 ` Botello Ortega, Luis
2018-04-21 22:46 ` Ian W MORRISON
2018-04-25 23:15 ` Ian W MORRISON
2018-04-27 9:20 ` Jani Nikula
2018-04-30 7:58 ` Joonas Lahtinen
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=87o9iee2pb.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Michal.Wajdeczko@intel.com \
--cc=airlied@linux.ie \
--cc=anusha.srivatsa@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=ianwmorrison@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.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).