From 86c4b39d929c37b2899b41c030c9756ea336333f Mon Sep 17 00:00:00 2001 From: Stefano Cianciulli Date: Thu, 9 Jun 2022 14:46:08 +0000 Subject: Fix modernize-use-using clang-tidy issues All the // NOLINT comments introduced in this CL were meant to disable only the modernize-use-using checks, but changing the comment to be // NOLINT(modernize-use-using) as explained in https://clang.llvm.org/extra/clang-tidy/#suppressing-undesired-diagnostics will make cpplint throw an error, as also cpplint uses the // NOLINT(...) notation to suppress unwanted warnings. Test: m tidy-art Test: art/libnativebridge/tests/runtests.sh Bug: 213953102 Change-Id: I9a992e0f0ecd06f7e64fd0bbf473bec4582370f6 --- libnativebridge/include/nativebridge/native_bridge.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'libnativebridge/include/nativebridge/native_bridge.h') diff --git a/libnativebridge/include/nativebridge/native_bridge.h b/libnativebridge/include/nativebridge/native_bridge.h index 2199bab552..5904c0fe3f 100644 --- a/libnativebridge/include/nativebridge/native_bridge.h +++ b/libnativebridge/include/nativebridge/native_bridge.h @@ -40,7 +40,7 @@ struct NativeBridgeRuntimeValues; // Function pointer type for sigaction. This is mostly the signature of a signal handler, except // for the return type. The runtime needs to know whether the signal was handled or should be given // to the chain. -typedef bool (*NativeBridgeSignalHandlerFn)(int, siginfo_t*, void*); +typedef bool (*NativeBridgeSignalHandlerFn)(int, siginfo_t*, void*); // NOLINT // Open the native bridge, if any. Should be called by Runtime::Init(). A null library filename // signals that we do not want to load a native bridge. -- cgit v1.2.3-59-g8ed1b