From 80e69a6c86f5c73522ff46e4e7abadd06897be61 Mon Sep 17 00:00:00 2001
From: Daniel Verkamp <dverkamp@chromium.org>
Date: Mon, 10 May 2021 14:21:19 -0700
Subject: [PATCH] clippy: re-enable warnings that don't match anything

Some of the "To be resolved" warnings no longer match any of the current
crosvm code, so remove them from the list so new instances can be
caught.

BUG=None
TEST=bin/clippy

Change-Id: I29de2ef49ba1b84250c46fd41844b45b7a3f79a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2885788
Tested-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: Dennis Kempin <denniskempin@google.com>
Reviewed-by: Zach Reizner <zachr@chromium.org>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
---
 bin/clippy | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/bin/clippy b/bin/clippy
index cd1a2480e3..6d8568d771 100755
--- a/bin/clippy
+++ b/bin/clippy
@@ -28,21 +28,9 @@ cd ..
 
 SUPPRESS=(
     # TODO(crbug/908640): To be resolved.
-    borrowed_box
     collapsible_if
     comparison_chain
-    extra_unused_lifetimes
-    for_kv_map
-    inefficient_to_string
-    let_unit_value
     missing_safety_doc
-    needless_range_loop
-    option_map_unit_fn
-    range_plus_one
-    slow_vector_initialization
-    unnecessary_filter_map
-    unneeded_field_pattern
-    useless_format
     wrong_self_convention
     # To be fixed in external libraries
     upper_case_acronyms