Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [i-g-t V4 0/7] New dir structure for intel specific tests
Date: Wed, 30 Aug 2023 16:44:47 +0200	[thread overview]
Message-ID: <4ae1e113-61fd-a6cc-7c18-e88c3ffe90b3@linux.intel.com> (raw)
In-Reply-To: <20230802193330.3843896-1-bhanuprakash.modem@intel.com>

Hi Bhanu,

On 8/2/23 21:33, Bhanuprakash Modem wrote:
> In-order to organize tests, move all intel specific tests to
> a new directory "tests/intel". And rename all intel specific
> tests to represent the supported driver. Test name should start
> with the driver_name prefix. Below are the Examples.
>
> - tests/intel/xe_*.c   : All XE specific tests. Ex: xe_module_load.c
> - tests/intel/kms_*.c  : All kms tests. Ex: kms_psr.c
> - tests/intel/intel_*.c: All tests those supports both i915 & XE.
> - tests/intel/i915_*.c : All i915 specific tests. Ex: i915_module_load.c
>
> Bhanuprakash Modem (7):
>    testplan/i915: Exclude non-i915 tests from i915 testplan
>    testplan/kms: Move kms testplan to intel dir
>    tests/i915/prime_mmap_kms: Add missing documentation
>    tests/meson.build: Simplify builds for Chamelium targets
>    tests: Move intel specific tests to new directory
>    tests/meson.build: Split intel targets based on their nature
>    tests: Rename all intel specific tests


Could you please rebase it and resend? currently, it doesn't apply cleanly:

$ wget 
https://patchwork.freedesktop.org/api/1.0/series/117227/revisions/7/mbox/ 
-O rename.patch
--2023-08-30 16:43:11-- 
https://patchwork.freedesktop.org/api/1.0/series/117227/revisions/7/mbox/
Resolving proxy-ir.intel.com (proxy-ir.intel.com)... 10.102.248.16
Connecting to proxy-ir.intel.com 
(proxy-ir.intel.com)|10.102.248.16|:912... connected.
Proxy request sent, awaiting response... 200 OK
Length: 145255 (142K) [text/plain]
Saving to: ‘rename.patch’

rename.patch 
100%[=====================================================================================================>] 
141.85K   295KB/s    in 0.5s

2023-08-30 16:43:13 (295 KB/s) - ‘rename.patch’ saved [145255/145255]

$ patch -p1 -i rename.patch -f -s
1 out of 1 hunk FAILED -- saving rejects to file 
tests/i915/i915_test_config.json.rej
1 out of 1 hunk FAILED -- saving rejects to file 
tests/i915/kms_test_config.json.rej
1 out of 4 hunks FAILED -- saving rejects to file 
tests/intel-ci/fast-feedback.testlist.rej

Regards,
Mauro

  parent reply	other threads:[~2023-08-30 14:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 19:33 [igt-dev] [i-g-t V4 0/7] New dir structure for intel specific tests Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 1/7] testplan/i915: Exclude non-i915 tests from i915 testplan Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 2/7] testplan/kms: Move kms testplan to intel dir Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 3/7] tests/i915/prime_mmap_kms: Add missing documentation Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 4/7] tests/meson.build: Simplify builds for Chamelium targets Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 5/7] tests: Move intel specific tests to new directory Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 6/7] tests/meson.build: Split intel targets based on their nature Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 7/7] tests: Rename all intel specific tests Bhanuprakash Modem
2023-08-02 20:31 ` [igt-dev] ○ CI.xeBAT: info for New dir structure for intel specific tests (rev7) Patchwork
2023-08-02 20:40 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2023-08-30 14:44 ` Mauro Carvalho Chehab [this message]
2023-08-31 15:33   ` [igt-dev] [i-g-t V4 0/7] New dir structure for intel specific tests Modem, Bhanuprakash

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=4ae1e113-61fd-a6cc-7c18-e88c3ffe90b3@linux.intel.com \
    --to=mauro.chehab@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.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