From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111637] Document configuration shadowing and clean up handling that in igt_core
Date: Wed, 11 Sep 2019 05:14:49 +0000 [thread overview]
Message-ID: <bug-111637-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1264 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111637
Bug ID: 111637
Summary: Document configuration shadowing and clean up handling
that in igt_core
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: not set
Component: IGT
Assignee: dri-devel@lists.freedesktop.org
Reporter: arkadiusz.hiler@intel.com
The current agreed order of importance is as follows:
.igtrc < ENV < --switch
or to put it in words
.igtrc option is less important than ENV
.igtrc and ENV are both less important than --switch
Real world example:
https://patchwork.freedesktop.org/series/63553/
device for IGT execution can be specified as Common::Device in .igtrc,
IGT_DEVICE env variable or --device switch on command line.
The idea is that .igtrc is the default set on the machine that can be
overwritten for the whole session with env or just for a single test with
--device.
This needs to be documented and the whey we handle this in igt_core.c could use
some streamlining.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2630 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-09-11 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 5:14 bugzilla-daemon [this message]
2019-11-12 7:41 ` [Bug 111637] Document configuration shadowing and clean up handling that in igt_core bugzilla-daemon
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=bug-111637-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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 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.