From fc3f1e2d20d56fc563afab098a51997466ac1880 Mon Sep 17 00:00:00 2001
From: ROCm CI Service Account <66695075+rocm-ci@users.noreply.github.com>
Date: Tue, 17 May 2022 11:32:58 +0530
Subject: [PATCH] SWDEV-330657 - Remove hipThreadIdx definition (#2644)

Change-Id: Ic54c1ad1466c6e950e8b5f95ee8565e28c1db70c
---
 docs/markdown/hip_faq.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/markdown/hip_faq.md b/docs/markdown/hip_faq.md
index 71dd1084ca..d30f63f1d3 100644
--- a/docs/markdown/hip_faq.md
+++ b/docs/markdown/hip_faq.md
@@ -142,7 +142,7 @@ The tools also struggle with more complex CUDA applications, in particular, thos
 - For Nvidia platforms, HIP requires Unified Memory and should run on any device supporting CUDA SDK 6.0 or newer. We have tested the Nvidia Titan and Tesla K40.
 
 ### Do HIPIFY tools automatically convert all source code?
-Typically, HIPIFY tools can automatically convert almost all run-time code, and the coordinate indexing device code ( threadIdx.x -> hipThreadIdx_x ).
+Typically, HIPIFY tools can automatically convert almost all run-time code.
 Most device code needs no additional conversion since HIP and CUDA have similar names for math and built-in functions.
 The hipify-clang tool will automatically modify the kernel signature as needed (automating a step that used to be done manually).
 Additional porting may be required to deal with architecture feature queries or with CUDA capabilities that HIP doesn't support.