From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "Summers, Stuart" <stuart.summers@intel.com>,
"Latvala, Petri" <petri.latvala@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"norkernel@freedesktop.org" <norkernel@freedesktop.org>,
"Syrjala, Ville" <ville.syrjala@intel.com>,
"Heikkila, Juha-pekka" <juha-pekka.heikkila@intel.com>,
"Peres, Martin" <martin.peres@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v4] igt/tests: Fix error checking in kms_atomic_transition
Date: Wed, 6 Mar 2019 14:52:59 +0000 [thread overview]
Message-ID: <487844099b0989376b917efee95e87a0efb7f239.camel@intel.com> (raw)
In-Reply-To: <20190306125627.GK4038@platvala-desk.ger.corp.intel.com>
On Wed, 2019-03-06 at 14:56 +0200, Petri Latvala wrote:
> On Tue, Feb 19, 2019 at 09:05:12PM +0000, Summers, Stuart wrote:
> >
> > Reviewed-by: Stuart Summers <stuart.summers@intel.com>
>
>
> Merged, thanks for the patch and review.
>
> Stan, do you have IGT commit access yet?
I didn't try to commit anything, but I guess not.
Best Regards,
Lisovskiy Stanislav
>
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-03-06 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 9:38 [igt-dev] [PATCH i-g-t v4] igt/tests: Fix error checking in kms_atomic_transition Stanislav Lisovskiy
2019-02-19 10:12 ` [igt-dev] ✓ Fi.CI.BAT: success for igt/tests: Fix error checking in kms_atomic_transition (rev4) Patchwork
2019-02-19 12:18 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-02-19 21:05 ` [igt-dev] [PATCH i-g-t v4] igt/tests: Fix error checking in kms_atomic_transition Summers, Stuart
2019-03-06 12:56 ` Petri Latvala
2019-03-06 14:52 ` Lisovskiy, Stanislav [this message]
2019-04-03 14:23 ` Daniel Vetter
2019-04-04 7:33 ` Lisovskiy, Stanislav
2019-04-04 8:10 ` Daniel Vetter
2019-04-04 8:35 ` Lisovskiy, Stanislav
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=487844099b0989376b917efee95e87a0efb7f239.camel@intel.com \
--to=stanislav.lisovskiy@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juha-pekka.heikkila@intel.com \
--cc=martin.peres@intel.com \
--cc=norkernel@freedesktop.org \
--cc=petri.latvala@intel.com \
--cc=stuart.summers@intel.com \
--cc=ville.syrjala@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