lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190731.185446.1493596264763518954.davem@davemloft.net>
Date:   Wed, 31 Jul 2019 18:54:46 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     lucasb@...atatu.com
Cc:     netdev@...r.kernel.org, nicolas.dichtel@...nd.com,
        jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us,
        mleitner@...hat.com, vladbu@...lanox.com, dcaratti@...hat.com,
        kernel@...atatu.com
Subject: Re: [PATCH v2 net-next 1/1] tc-testing: Clarify the use of tdc's
 -d option

From: Lucas Bates <lucasb@...atatu.com>
Date: Mon, 29 Jul 2019 19:18:12 -0400

> The -d command line argument to tdc requires the name of a physical device
> on the system where the tests will be run. If -d has not been used, tdc
> will skip tests that require a physical device.
> 
> This patch is intended to better document what the -d option does and how
> it is used.
> 
> Signed-off-by: Lucas Bates <lucasb@...atatu.com>

Applied.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ