/linux/arch/arm64/include/asm/ |
H A D | stack_pointer.h | a9ea0017ebe8889dfa136cac2aa7ae0ee6915e1f Thu Nov 03 21:23:05 CET 2016 Mark Rutland <mark.rutland@arm.com> arm64: factor out current_stack_pointer
We define current_stack_pointer in <asm/thread_info.h>, though other files and header relying upon it do not have this necessary include, and are thus fragile to changes in the header soup.
Subsequent patches will affect the header soup such that directly including <asm/thread_info.h> may result in a circular header include in some of these cases, so we can't simply include <asm/thread_info.h>.
Instead, factor current_thread_info into its own header, and have all existing users include this explicitly.
Signed-off-by: Mark Rutland <mark.rutland@arm.com> Tested-by: Laura Abbott <labbott@redhat.com> Cc: Will Deacon <will.deacon@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
|
H A D | perf_event.h | diff a9ea0017ebe8889dfa136cac2aa7ae0ee6915e1f Thu Nov 03 21:23:05 CET 2016 Mark Rutland <mark.rutland@arm.com> arm64: factor out current_stack_pointer
We define current_stack_pointer in <asm/thread_info.h>, though other files and header relying upon it do not have this necessary include, and are thus fragile to changes in the header soup.
Subsequent patches will affect the header soup such that directly including <asm/thread_info.h> may result in a circular header include in some of these cases, so we can't simply include <asm/thread_info.h>.
Instead, factor current_thread_info into its own header, and have all existing users include this explicitly.
Signed-off-by: Mark Rutland <mark.rutland@arm.com> Tested-by: Laura Abbott <labbott@redhat.com> Cc: Will Deacon <will.deacon@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
|
H A D | percpu.h | diff a9ea0017ebe8889dfa136cac2aa7ae0ee6915e1f Thu Nov 03 21:23:05 CET 2016 Mark Rutland <mark.rutland@arm.com> arm64: factor out current_stack_pointer
We define current_stack_pointer in <asm/thread_info.h>, though other files and header relying upon it do not have this necessary include, and are thus fragile to changes in the header soup.
Subsequent patches will affect the header soup such that directly including <asm/thread_info.h> may result in a circular header include in some of these cases, so we can't simply include <asm/thread_info.h>.
Instead, factor current_thread_info into its own header, and have all existing users include this explicitly.
Signed-off-by: Mark Rutland <mark.rutland@arm.com> Tested-by: Laura Abbott <labbott@redhat.com> Cc: Will Deacon <will.deacon@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
|
H A D | thread_info.h | diff a9ea0017ebe8889dfa136cac2aa7ae0ee6915e1f Thu Nov 03 21:23:05 CET 2016 Mark Rutland <mark.rutland@arm.com> arm64: factor out current_stack_pointer
We define current_stack_pointer in <asm/thread_info.h>, though other files and header relying upon it do not have this necessary include, and are thus fragile to changes in the header soup.
Subsequent patches will affect the header soup such that directly including <asm/thread_info.h> may result in a circular header include in some of these cases, so we can't simply include <asm/thread_info.h>.
Instead, factor current_thread_info into its own header, and have all existing users include this explicitly.
Signed-off-by: Mark Rutland <mark.rutland@arm.com> Tested-by: Laura Abbott <labbott@redhat.com> Cc: Will Deacon <will.deacon@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
|
/linux/arch/arm64/kernel/ |
H A D | return_address.c | diff a9ea0017ebe8889dfa136cac2aa7ae0ee6915e1f Thu Nov 03 21:23:05 CET 2016 Mark Rutland <mark.rutland@arm.com> arm64: factor out current_stack_pointer
We define current_stack_pointer in <asm/thread_info.h>, though other files and header relying upon it do not have this necessary include, and are thus fragile to changes in the header soup.
Subsequent patches will affect the header soup such that directly including <asm/thread_info.h> may result in a circular header include in some of these cases, so we can't simply include <asm/thread_info.h>.
Instead, factor current_thread_info into its own header, and have all existing users include this explicitly.
Signed-off-by: Mark Rutland <mark.rutland@arm.com> Tested-by: Laura Abbott <labbott@redhat.com> Cc: Will Deacon <will.deacon@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
|
H A D | stacktrace.c | diff a9ea0017ebe8889dfa136cac2aa7ae0ee6915e1f Thu Nov 03 21:23:05 CET 2016 Mark Rutland <mark.rutland@arm.com> arm64: factor out current_stack_pointer
We define current_stack_pointer in <asm/thread_info.h>, though other files and header relying upon it do not have this necessary include, and are thus fragile to changes in the header soup.
Subsequent patches will affect the header soup such that directly including <asm/thread_info.h> may result in a circular header include in some of these cases, so we can't simply include <asm/thread_info.h>.
Instead, factor current_thread_info into its own header, and have all existing users include this explicitly.
Signed-off-by: Mark Rutland <mark.rutland@arm.com> Tested-by: Laura Abbott <labbott@redhat.com> Cc: Will Deacon <will.deacon@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
|
H A D | traps.c | diff a9ea0017ebe8889dfa136cac2aa7ae0ee6915e1f Thu Nov 03 21:23:05 CET 2016 Mark Rutland <mark.rutland@arm.com> arm64: factor out current_stack_pointer
We define current_stack_pointer in <asm/thread_info.h>, though other files and header relying upon it do not have this necessary include, and are thus fragile to changes in the header soup.
Subsequent patches will affect the header soup such that directly including <asm/thread_info.h> may result in a circular header include in some of these cases, so we can't simply include <asm/thread_info.h>.
Instead, factor current_thread_info into its own header, and have all existing users include this explicitly.
Signed-off-by: Mark Rutland <mark.rutland@arm.com> Tested-by: Laura Abbott <labbott@redhat.com> Cc: Will Deacon <will.deacon@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
|