All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peres, Martin" <martin.peres@intel.com>
To: "Latvala, Petri" <petri.latvala@intel.com>,
	Melissa Wen <melissa.srw@gmail.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"kernel-usp@googlegroups.com" <kernel-usp@googlegroups.com>
Subject: Re: [Intel-gfx] [PATCH i-g-t] tests/kms_plane_alpha_blend: Correct typo in the name and comments of a subtest
Date: Tue, 31 Mar 2020 10:46:35 +0000	[thread overview]
Message-ID: <e6f59148eae545b69a8cbafac05a1d31@intel.com> (raw)
In-Reply-To: 20200331094324.GG9497@platvala-desk.ger.corp.intel.com

[-- Attachment #1: Type: text/plain, Size: 504 bytes --]

On 2020-03-31 12:43, Petri Latvala wrote:
> On Mon, Mar 30, 2020 at 06:55:32PM -0300, Melissa Wen wrote:
>> Typo found in word transparent.
>> Correct the word transparant, replacing the last letter -a- with -e-
>> (transpar-a-nt to transpar-e-nt).
>>
>> Signed-off-by: Melissa Wen <melissa.srw@gmail.com>
> 
> 
> Reviewed-by: Petri Latvala <petri.latvala@intel.com>
> 
> Martin, test rename, ack when cibuglog side is ready to merge this.
> 

ACK, thanks for the patch Melissa!

Martin

[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1774 bytes --]

[-- Attachment #3: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2020-03-31 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30 21:55 [Intel-gfx] [PATCH i-g-t] tests/kms_plane_alpha_blend: Correct typo in the name and comments of a subtest Melissa Wen
2020-03-30 22:11 ` [Intel-gfx] ✗ GitLab.Pipeline: failure for " Patchwork
2020-03-30 22:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-03-31  9:22 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-03-31  9:43 ` [Intel-gfx] [PATCH i-g-t] " Petri Latvala
2020-03-31 10:46   ` Peres, Martin [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=e6f59148eae545b69a8cbafac05a1d31@intel.com \
    --to=martin.peres@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kernel-usp@googlegroups.com \
    --cc=melissa.srw@gmail.com \
    --cc=petri.latvala@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.