diff --git a/build-support/clang_tidy_gerrit.py b/build-support/clang_tidy_gerrit.py
index 35b206a..cd500b1 100755
--- a/build-support/clang_tidy_gerrit.py
+++ b/build-support/clang_tidy_gerrit.py
@@ -49,6 +49,25 @@
     # Although useful in production code, we use magic numbers liberally in
     # tests, and many would be net less clear as named constants.
     'readability-magic-numbers',
+
+    # IWYU has specific rules for ordering '-inl.h' include files, i.e.
+    # 'header.h' and its 'header-inl.h' counterpart. It seems in some cases
+    # including 'header-inl.h' before 'header.h' might even lead to compilation
+    # failures. So, IWYU intentionally re-orders them even if 'header-inl.h'
+    # comes before 'header.h' lexicographically in default C locale:
+    #   https://github.com/apache/kudu/blob/ \
+    #     89ce529e945731c48445db4a6f8af11f9f905aab/build-support/iwyu/ \
+    #     fix_includes.py#L1786-L1787
+    #
+    # That ordering contradicts with what clang-tidy recommends when using the
+    # 'llvm-include-order' check. To avoid confusion, let's disable the
+    # 'llvm-include-order'.
+    #
+    # TODO(aserbin): clarify whether it's possible to customize clang-tidy
+    #                behavior w.r.t. the sorting of such header files using
+    #                the format style options described at
+    #                https://clang.llvm.org/docs/ClangFormatStyleOptions.html
+    'llvm-include-order',
 ]
 
 def run_tidy(sha="HEAD", is_rev_range=False):