From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 0/2] lib/igt_device_scan: add filer card=all
Date: Tue, 18 Oct 2022 17:06:29 +0100 [thread overview]
Message-ID: <640e3f12-db6d-1ea1-9a43-441b36540776@linux.intel.com> (raw)
In-Reply-To: <20221018091001.18552-1-kamil.konieczny@linux.intel.com>
On 18/10/2022 10:09, Kamil Konieczny wrote:
> Allow to select all (up to 16) discrete cards with the help of
> card=all or card=*, for example:
>
> ./gem_basic --device=pci:vendor=intel,device=discrete,card=all
What should this do btw? Run the tests on more than one card in
sequence? Isn't that test runner's job?
Regards,
Tvrtko
> Kamil Konieczny (2):
> lib/igt_device_scan: refactor filer adding
> lib/igt_device_scan: add card=all filter selector
>
> lib/igt_device_scan.c | 36 ++++++++++++++++++++++++++++++++++--
> 1 file changed, 34 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2022-10-18 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 9:09 [igt-dev] [PATCH i-g-t 0/2] lib/igt_device_scan: add filer card=all Kamil Konieczny
2022-10-18 9:10 ` [igt-dev] [PATCH i-g-t 1/2] lib/igt_device_scan: refactor filer adding Kamil Konieczny
2022-10-18 15:12 ` Zbigniew Kempczyński
2022-10-18 15:13 ` Zbigniew Kempczyński
2022-10-18 9:10 ` [igt-dev] [PATCH i-g-t 2/2] lib/igt_device_scan: add card=all filter selector Kamil Konieczny
2022-10-18 10:56 ` Petri Latvala
2022-10-18 9:38 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/igt_device_scan: add filer card=all Patchwork
2022-10-18 9:51 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2022-10-18 16:06 ` Tvrtko Ursulin [this message]
2022-10-19 11:43 ` [igt-dev] [PATCH i-g-t 0/2] " Kamil Konieczny
2022-10-21 8:14 ` Tvrtko Ursulin
2022-10-19 8:25 ` [igt-dev] ✗ Fi.CI.IGT: failure for " 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=640e3f12-db6d-1ea1-9a43-441b36540776@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.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.