public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: John Machado <john.machado@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] Add TigerLake Registers file
Date: Tue, 21 Jan 2020 11:31:24 +0200	[thread overview]
Message-ID: <20200121093124.GZ25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20200121093014.GY25209@platvala-desk.ger.corp.intel.com>

On Tue, Jan 21, 2020 at 11:30:14AM +0200, Petri Latvala wrote:
> On Fri, Jan 17, 2020 at 05:27:59AM +0530, John Machado wrote:
> > Added the TigerLake register spec file and a register delta file
> > that contain additional registers corresponding to TigerLake.
> > 
> > The spec file uses the icelake file along with the newly added
> > register file for TGL register definations.
> > 
> > Suggested-by: Swati Sharma <swati2.sharma@intel.com>
> > Signed-off-by: John Machado <john.machado@intel.com>
> 
> igt@tools_test@tools_test doesn't explode. The values I'm not going to
> check, if they're incorrect we can fix them later, they're only used
> by the tools and won't affect CI.
> 
> Acked-by: Petri Latvala <petri.latvala@intel.com>

And now merged, thanks.


-- 
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      reply	other threads:[~2020-01-21  9:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 23:57 [igt-dev] [PATCH i-g-t] Add TigerLake Registers file John Machado
2020-01-17  7:49 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-21  4:24 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2020-01-21  9:30 ` [igt-dev] [PATCH i-g-t] " Petri Latvala
2020-01-21  9:31   ` Petri Latvala [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=20200121093124.GZ25209@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=john.machado@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