aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2021-09-15 12:11:48 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2021-09-15 12:11:48 -0700
commitd6efd3f18763ac84098fa318742cd2a3bfdf4d72 (patch)
tree3369fa7a752f9793166f93191588b4fb266b20fa /tools/perf/scripts/python/export-to-postgresql.py
parenttools/bootconfig: Define memblock_free_ptr() to fix build error (diff)
parentalpha: Use absolute_pointer to define COMMAND_LINE (diff)
downloadlinux-dev-d6efd3f18763ac84098fa318742cd2a3bfdf4d72.tar.xz
linux-dev-d6efd3f18763ac84098fa318742cd2a3bfdf4d72.zip
Merge branch 'absolute-pointer' (patches from Guenter)
Merge absolute_pointer macro series from Guenter Roeck: "Kernel test builds currently fail for several architectures with error messages such as the following. drivers/net/ethernet/i825xx/82596.c: In function 'i82596_probe': arch/m68k/include/asm/string.h:72:25: error: '__builtin_memcpy' reading 6 bytes from a region of size 0 [-Werror=stringop-overread] Such warnings may be reported by gcc 11.x for string and memory operations on fixed addresses if gcc's builtin functions are used for those operations. This series introduces absolute_pointer() to fix the problem. absolute_pointer() disassociates a pointer from its originating symbol type and context, and thus prevents gcc from making assumptions about pointers passed to memory operations" * emailed patches from Guenter Roeck <linux@roeck-us.net>: alpha: Use absolute_pointer to define COMMAND_LINE alpha: Move setup.h out of uapi net: i825xx: Use absolute_pointer for memcpy from fixed memory location compiler.h: Introduce absolute_pointer macro
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions