All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Sascha Silbe <silbe@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Kevin Wolf <kwolf@redhat.com>
Cc: Tu Bo <tubo@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 4/4] qemu-iotests: place valgrind log file in scratch dir
Date: Tue, 12 Apr 2016 19:19:53 +0200	[thread overview]
Message-ID: <570D2E39.3070707@redhat.com> (raw)
In-Reply-To: <1460472980-26319-5-git-send-email-silbe@linux.vnet.ibm.com>


[-- Attachment #1.1: Type: text/plain, Size: 453 bytes --]

On 12.04.2016 16:56, Sascha Silbe wrote:
> Do not place the valgrind log file at a predictable path in a
> world-writable location. Use the common scratch directory (${TEST_DIR})
> instead.
> 
> Signed-off-by: Sascha Silbe <silbe@linux.vnet.ibm.com>
> Reviewed-by: Bo Tu <tubo@linux.vnet.ibm.com>
> ---
>  tests/qemu-iotests/common.config | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Reviewed-by: Max Reitz <mreitz@redhat.com>


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-04-12 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 14:56 [Qemu-devel] [PATCH for-2.6 0/4] qemu-iotests: don't use /tmp Sascha Silbe
2016-04-12 14:56 ` [Qemu-devel] [PATCH 1/4] qemu-iotests: drop unused _within_tolerance() filter Sascha Silbe
2016-04-12 16:57   ` Max Reitz
2016-04-12 14:56 ` [Qemu-devel] [PATCH 2/4] qemu-iotests: common.rc: drop unused _do() Sascha Silbe
2016-04-12 17:08   ` Max Reitz
2016-04-12 14:56 ` [Qemu-devel] [PATCH 3/4] qemu-iotests: tests: do not set unused tmp variable Sascha Silbe
2016-04-12 17:14   ` Max Reitz
2016-04-12 14:56 ` [Qemu-devel] [PATCH 4/4] qemu-iotests: place valgrind log file in scratch dir Sascha Silbe
2016-04-12 17:19   ` Max Reitz [this message]
2016-04-12 17:32 ` [Qemu-devel] [PATCH for-2.6 0/4] qemu-iotests: don't use /tmp Max Reitz
2016-04-14 11:41   ` Sascha Silbe

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=570D2E39.3070707@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=silbe@linux.vnet.ibm.com \
    --cc=tubo@linux.vnet.ibm.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.