Nicholas Piggin's on February 7, 2019 2:27 pm: > Michael Ellerman's on February 5, 2019 9:32 pm: >> From: Christophe Leroy <christophe.le...@c-s.fr> >> >> Now that thread_info is similar to task_struct, its address is in r2 >> so CURRENT_THREAD_INFO() macro is useless. This patch removes it. > > You wouldn't want to keep CURRENT_THREAD_INFO(r2) to mean get the thread > info out of current, as just a no-op for documentation purpose? I don't > know /32 code at all so it's up to you.
I see that I said roughly the opposite last year, if that helps to determine the importance of my opinion. Thanks, Nick
