Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karthik B S <karthik.b.s@intel.com>
To: Kunal Joshi <kunal1.joshi@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH 3/3] tests/intel-ci: added blacklist to meson.build
Date: Thu, 20 Jul 2023 10:26:05 +0530	[thread overview]
Message-ID: <2c602a4d-b955-0d14-1969-19513f0414f2@intel.com> (raw)
In-Reply-To: <20230719070939.562159-4-kunal1.joshi@intel.com>


On 7/19/2023 12:39 PM, Kunal Joshi wrote:
> Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com>
Reviewed-by: Karthik B S <karthik.b.s@intel.com>
> ---
>   tests/intel-ci/meson.build | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/tests/intel-ci/meson.build b/tests/intel-ci/meson.build
> index d5a6e4f47..9f6ed501d 100644
> --- a/tests/intel-ci/meson.build
> +++ b/tests/intel-ci/meson.build
> @@ -7,6 +7,8 @@ intelci_files = [
>     'blacklist-pre-merge.txt',
>     'xe-fast-feedback.testlist',
>     'xe.blocklist.txt',
> +  'chamelium.blacklist',
> +  'psr.blacklist',
>   ]
>   
>   install_data(sources : intelci_files, install_dir : datadir)

  reply	other threads:[~2023-07-20  4:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19  7:09 [igt-dev] [PATCH 0/3] Add seperate blacklist for specific config Kunal Joshi
2023-07-19  7:09 ` [igt-dev] [PATCH 1/3] tests/intel-ci: Added chamelium config blacklist Kunal Joshi
2023-07-20  4:50   ` Karthik B S
2023-07-20  4:54     ` Joshi, Kunal1
2023-07-19  7:09 ` [igt-dev] [PATCH 2/3] tests/intel-ci: Added psr " Kunal Joshi
2023-07-20  4:53   ` Karthik B S
2023-07-19  7:09 ` [igt-dev] [PATCH 3/3] tests/intel-ci: added blacklist to meson.build Kunal Joshi
2023-07-20  4:56   ` Karthik B S [this message]
2023-07-19  8:08 ` [igt-dev] ○ CI.xeBAT: info for Add seperate blacklist for specific config (rev2) Patchwork
2023-07-19  8:19 ` [igt-dev] ✗ Fi.CI.BAT: failure " 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=2c602a4d-b955-0d14-1969-19513f0414f2@intel.com \
    --to=karthik.b.s@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kunal1.joshi@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