diff mbox

[rdma-core] debian: Whitelist architectures that support valgrind

Message ID 20180430164000.5022-1-benjamin.drung@profitbricks.com (mailing list archive)
State Accepted
Headers show

Commit Message

Benjamin Drung April 30, 2018, 4:40 p.m. UTC 
Instead of maintaining a blacklist of architectures that do not have
valgrind available, use a whitelist instead (since valgrind uses also a
whitelist for the supported architectures).

Signed-off-by: Benjamin Drung <benjamin.drung@profitbricks.com>
---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

Doug Ledford May 1, 2018, 3:43 p.m. UTC | #1 
On Mon, 2018-04-30 at 18:40 +0200, Benjamin Drung wrote:
> Instead of maintaining a blacklist of architectures that do not have
> valgrind available, use a whitelist instead (since valgrind uses also a
> whitelist for the supported architectures).
> 
> Signed-off-by: Benjamin Drung <benjamin.drung@profitbricks.com>

Thanks, applied.
diff mbox

Patch

diff --git a/debian/control b/debian/control
index fa897c2f..a7802563 100644
--- a/debian/control
+++ b/debian/control
@@ -12,7 +12,7 @@  Build-Depends: cmake (>= 2.8.11),
                ninja-build,
                pkg-config,
                python,
-               valgrind [!alpha !armel !hppa !ia64 !m68k !powerpcspe !riscv64 !sh4 !sparc64 !x32]
+               valgrind [amd64 arm64 armhf i386 mips mips64el mipsel powerpc ppc64 ppc64el s390x]
 Standards-Version: 4.1.3
 Vcs-Git: https://github.com/linux-rdma/rdma-core.git
 Vcs-Browser: https://github.com/linux-rdma/rdma-core