From: Eric Engestrom <eric.engestrom@imgtec.com>
To: intel-gfx@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org
Subject: [PATCH maintainer-tools 2/3] dim: send 'not configured' error to stderr
Date: Wed, 5 Apr 2017 12:15:24 +0100 [thread overview]
Message-ID: <20170405111525.32602-2-eric.engestrom@imgtec.com> (raw)
In-Reply-To: <20170405111525.32602-1-eric.engestrom@imgtec.com>
This fixes `make check` when dim is not configured.
Signed-off-by: Eric Engestrom <eric.engestrom@imgtec.com>
---
dim | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dim b/dim
index 588e859..b373901 100755
--- a/dim
+++ b/dim
@@ -197,7 +197,7 @@ export __dim_running=1
if [ "$subcommand" != "setup" ] && [ "$subcommand" != "help" ] && [ "$subcommand" != "usage" ]; then
for d in $DIM_PREFIX $DIM_PREFIX/$DIM_DRM_INTEL $DIM_PREFIX/drm-rerere $DIM_PREFIX/drm-tip; do
if [ ! -d $d ]; then
- echo "$d is missing, please check your configuration and/or run dim setup"
+ echoerr "$d is missing, please check your configuration and/or run dim setup"
exit 1
fi
done
--
Cheers,
Eric
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-05 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 11:15 [PATCH maintainer-tools 1/3] make: run check on current `dim`, not the installed one Eric Engestrom
2017-04-05 11:15 ` Eric Engestrom [this message]
2017-04-05 11:15 ` [PATCH maintainer-tools 3/3] dim.rst: update CONTRIBUTING instructions Eric Engestrom
2017-04-05 11:25 ` Jani Nikula
2017-04-05 12:12 ` Daniel Vetter
2017-04-05 11:29 ` [PATCH maintainer-tools 1/3] make: run check on current `dim`, not the installed one Jani Nikula
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=20170405111525.32602-2-eric.engestrom@imgtec.com \
--to=eric.engestrom@imgtec.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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.