summaryrefslogtreecommitdiffstats
path: root/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* Linux 3.18.83v3.18.83Greg Kroah-Hartman2017-11-211-1/+1
|
* Linux 3.18.82v3.18.82Greg Kroah-Hartman2017-11-181-1/+1
|
* Linux 3.18.81v3.18.81Greg Kroah-Hartman2017-11-151-1/+1
|
* Linux 3.18.80v3.18.80Greg Kroah-Hartman2017-11-081-1/+1
|
* Linux 3.18.79v3.18.79Greg Kroah-Hartman2017-11-021-1/+1
|
* Linux 3.18.78v3.18.78Greg Kroah-Hartman2017-10-271-1/+1
|
* Linux 3.18.77v3.18.77Greg Kroah-Hartman2017-10-211-1/+1
|
* Linux 3.18.76v3.18.76Greg Kroah-Hartman2017-10-181-1/+1
|
* Linux 3.18.75v3.18.75Greg Kroah-Hartman2017-10-121-1/+1
|
* Linux 3.18.74v3.18.74Greg Kroah-Hartman2017-10-081-1/+1
|
* Linux 3.18.73v3.18.73Greg Kroah-Hartman2017-10-051-1/+1
|
* Linux 3.18.72v3.18.72Greg Kroah-Hartman2017-09-271-1/+1
|
* Linux 3.18.71v3.18.71Greg Kroah-Hartman2017-09-131-1/+1
|
* Linux 3.18.70v3.18.70Greg Kroah-Hartman2017-09-071-1/+1
|
* Linux 3.18.69v3.18.69Greg Kroah-Hartman2017-09-021-1/+1
|
* Linux 3.18.68v3.18.68Greg Kroah-Hartman2017-08-301-1/+1
|
* Linux 3.18.67v3.18.67Greg Kroah-Hartman2017-08-241-1/+1
|
* Linux 3.18.66v3.18.66Greg Kroah-Hartman2017-08-161-1/+1
|
* Linux 3.18.65v3.18.65Greg Kroah-Hartman2017-08-121-1/+1
|
* Linux 3.18.64v3.18.64Greg Kroah-Hartman2017-08-111-1/+1
|
* Linux 3.18.63v3.18.63Greg Kroah-Hartman2017-07-271-1/+1
|
* disable new gcc-7.1.1 warnings for nowLinus Torvalds2017-07-271-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | commit bd664f6b3e376a8ef4990f87d08271cc2d01ba9a upstream. I made the mistake of upgrading my desktop to the new Fedora 26 that comes with gcc-7.1.1. There's nothing wrong per se that I've noticed, but I now have 1500 lines of warnings, mostly from the new format-truncation warning triggering all over the tree. We use 'snprintf()' and friends in a lot of places, and often know that the numbers are fairly small (ie a controller index or similar), but gcc doesn't know that, and sees an 'int', and thinks that it could be some huge number. And then complains when our buffers are not able to fit the name for the ten millionth controller. These warnings aren't necessarily bad per se, and we probably want to look through them subsystem by subsystem, but at least during the merge window they just mean that I can't even see if somebody is introducing any *real* problems when I pull. So warnings disabled for now. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
* Linux 3.18.62v3.18.62Greg Kroah-Hartman2017-07-211-1/+1
|
* Linux 3.18.61v3.18.61Greg Kroah-Hartman2017-07-151-1/+1
|
* Linux 3.18.60v3.18.60Greg Kroah-Hartman2017-07-051-1/+1
|
* Linux 3.18.59v3.18.59Greg Kroah-Hartman2017-06-291-1/+1
|
* Linux 3.18.58v3.18.58Greg Kroah-Hartman2017-06-261-1/+1
|
* Linux 3.18.57v3.18.57Greg Kroah-Hartman2017-06-141-1/+1
|
* Linux 3.18.56v3.18.56Greg Kroah-Hartman2017-06-071-1/+1
|
* Linux 3.18.55v3.18.55Greg Kroah-Hartman2017-05-251-1/+1
|
* Linux 3.18.54v3.18.54Greg Kroah-Hartman2017-05-201-1/+1
|
* Linux 3.18.53v3.18.53Greg Kroah-Hartman2017-05-151-1/+1
|
* Linux 3.18.52v3.18.52Greg Kroah-Hartman2017-05-081-1/+1
|
* Linux 3.18.51v3.18.51Greg Kroah-Hartman2017-04-301-1/+1
|
* Linux 3.18.50v3.18.50Greg Kroah-Hartman2017-04-221-1/+1
|
* Linux 3.18.49v3.18.49Greg Kroah-Hartman2017-04-181-1/+1
|
* Linux 3.18.48v3.18.48Greg Kroah-Hartman2017-02-081-1/+1
|
* Disable "frame-address" warningLinus Torvalds2017-02-081-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | commit 124a3d88fa20e1869fc229d7d8c740cc81944264 upstream. Newer versions of gcc warn about the use of __builtin_return_address() with a non-zero argument when "-Wall" is specified: kernel/trace/trace_irqsoff.c: In function ‘stop_critical_timings’: kernel/trace/trace_irqsoff.c:433:86: warning: calling ‘__builtin_return_address’ with a nonzero argument is unsafe [-Wframe-address] stop_critical_timing(CALLER_ADDR0, CALLER_ADDR1); [ .. repeats a few times for other similar cases .. ] It is true that a non-zero argument is somewhat dangerous, and we do not actually have very many uses of that in the kernel - but the ftrace code does use it, and as Stephen Rostedt says: "We are well aware of the danger of using __builtin_return_address() of > 0. In fact that's part of the reason for having the "thunk" code in x86 (See arch/x86/entry/thunk_{64,32}.S). [..] it adds extra frames when tracking irqs off sections, to prevent __builtin_return_address() from accessing bad areas. In fact the thunk_32.S states: 'Trampoline to trace irqs off. (otherwise CALLER_ADDR1 might crash)'." For now, __builtin_return_address() with a non-zero argument is the best we can do, and the warning is not helpful and can end up making people miss other warnings for real problems. So disable the frame-address warning on compilers that need it. Acked-by: Steven Rostedt <rostedt@goodmis.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
* Linux 3.18.47v3.18.47Sasha Levin2017-01-181-1/+1
| | | | Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
* Linux 3.18.46v3.18.46Sasha Levin2016-12-241-1/+1
| | | | Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
* Linux 3.18.45v3.18.45Sasha Levin2016-11-291-1/+1
| | | | Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
* kbuild: add -fno-PIESebastian Andrzej Siewior2016-11-241-0/+2
| | | | | | | | | | | | | | | | | | | | | [ Upstream commit 8ae94224c9d72fc4d9aaac93b2d7833cf46d7141 ] Debian started to build the gcc with -fPIE by default so the kernel build ends before it starts properly with: |kernel/bounds.c:1:0: error: code model kernel does not support PIC mode Also add to KBUILD_AFLAGS due to: |gcc -Wp,-MD,arch/x86/entry/vdso/vdso32/.note.o.d … -mfentry -DCC_USING_FENTRY … vdso/vdso32/note.S |arch/x86/entry/vdso/vdso32/note.S:1:0: sorry, unimplemented: -mfentry isn’t supported for 32-bit in combination with -fpic Tagging it stable so it is possible to compile recent stable kernels as well. Cc: stable@vger.kernel.org Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de> Signed-off-by: Michal Marek <mmarek@suse.com> Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
* Linux 3.18.44v3.18.44Sasha Levin2016-10-221-1/+1
| | | | Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
* Linux 3.18.43v3.18.43Sasha Levin2016-10-091-1/+1
| | | | Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
* Linux 3.18.42v3.18.42Sasha Levin2016-09-171-1/+1
| | | | Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
* Linux 3.18.41v3.18.41Sasha Levin2016-09-021-1/+1
| | | | Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
* Linux 3.18.40v3.18.40Sasha Levin2016-08-221-1/+1
| | | | Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
* Linux 3.18.39v3.18.39Sasha Levin2016-08-081-1/+1
| | | | Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
* Linux 3.18.38v3.18.38Sasha Levin2016-07-291-1/+1
| | | | Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
* Linux 3.18.37v3.18.37Sasha Levin2016-07-131-1/+1
| | | | Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-12 13:17:24 +0000