summaryrefslogtreecommitdiff
path: root/drivers/media/dvb-frontends/tda10071.c
diff options
context:
space:
mode:
authorJosh Poimboeuf <jpoimboe@kernel.org>2022-08-18 19:26:57 +0300
committerPeter Zijlstra <peterz@infradead.org>2022-08-19 20:47:57 +0300
commit3c6f3900808c483b0bbb2c351f995c7b880dae14 (patch)
treee3a0461a9b5c046e5f2b6a9fff315d9c4284203f /drivers/media/dvb-frontends/tda10071.c
parent7b3e31869081771c63c3d006347ad06738f843b5 (diff)
downloadlinux-3c6f3900808c483b0bbb2c351f995c7b880dae14.tar.xz
objtool: Remove "ANNOTATE_NOENDBR on ENDBR" warning
This warning isn't very useful: why would you put ANNOTATE_NOENDBR on ENDBR, and if you did, what's the harm? And thus far it's only found one non-bug, where the '__end_entry_SYSENTER_compat' label happens to land on the ENDBR from entry_SYSCALL_compat: vmlinux.o: warning: objtool: entry_SYSCALL_compat+0x0: ANNOTATE_NOENDBR on ENDBR .. which is fine. Just remove the warning. Reported-by: kernel test robot <lkp@intel.com> Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lkml.kernel.org/r/142341a5dafdfc788e4c95b9e226a6eefc9b626e.1660839773.git.jpoimboe@kernel.org
Diffstat (limited to 'drivers/media/dvb-frontends/tda10071.c')
0 files changed, 0 insertions, 0 deletions