linux-toradex.git/Makefile, branch v2.6.34.15

Linux 2.6.34.15

2014-02-10T22:31:40+00:00

Signed-off-by: Paul Gortmaker

Linux 2.6.34.14

2013-01-16T21:55:31+00:00

Signed-off-by: Paul Gortmaker

Linux 2.6.34.13

2012-08-20T18:45:22+00:00

Signed-off-by: Paul Gortmaker

kbuild: Fix passing -Wno-* options to gcc 4.4+

2012-08-17T19:35:57+00:00

commit 8417da6f2128008c431c7d130af6cd3d9079922e upstream.

Starting with 4.4, gcc will happily accept -Wno- in the
cc-option test and complain later when compiling a file that has some
other warning. This rather unexpected behavior is intentional as per
http://gcc.gnu.org/PR28322, so work around it by testing for support of
the opposite option (without the no-). Introduce a new Makefile function
cc-disable-warning that does this and update two uses of cc-option in
the toplevel Makefile.

Reported-and-tested-by: Stephen Rothwell 
Signed-off-by: Michal Marek 
Signed-off-by: Paul Gortmaker

kbuild: Disable -Wunused-but-set-variable for gcc 4.6.0

2012-08-17T19:35:54+00:00

commit af0e5d565d2fffcd97d1e2d89669d627cc04e8b8 upstream.

Disable the new -Wunused-but-set-variable that was added in gcc 4.6.0
It produces more false positives than useful warnings.

This can still be enabled using W=1

Signed-off-by: Dave Jones 
Acked-by: Sam Ravnborg 
Tested-by: Sam Ravnborg 
Signed-off-by: Michal Marek 
Signed-off-by: Paul Gortmaker

kbuild: implement several W= levels

2012-08-17T19:35:53+00:00

commit 28bc20dccadc610c56e27255aeef2938141a0cd3 upstream.

Building a kernel with "make W=1" produces far too much noise to be
useful.

Divide the warning options in three groups:

    W=1 - warnings that may be relevant and does not occur too often
    W=2 - warnings that occur quite often but may still be relevant
    W=3 - the more obscure warnings, can most likely be ignored

When building the whole kernel, those levels produce:

W=1 - 4859 warnings
W=2 - 1394 warnings
W=3 - 86666 warnings

respectively. Warnings have been counted with Geert's script at

http://www.kernel.org/pub/linux/kernel/people/geert/linux-log/linux-log-summary.pl

Many warnings occur from .h files so fixing one file may have a nice
effect on the total number of warnings.

With these changes I am actually tempted to try W=1 now and then.
Previously there was just too much noise.

Borislav:

- make the W= levels exclusive
- move very noisy and making little sense for the kernel warnings to W=3
- drop -Woverlength-strings due to useless warning message
- copy explanatory text for the different warning levels to 'make help'
- recount warnings per level

Signed-off-by: Sam Ravnborg 
Signed-off-by: Borislav Petkov 
Cc: Dave Jones 
Cc: Geert Uytterhoeven 
Signed-off-by: Michal Marek 
[PG: used for 2.6.34 to better control new compilers on older code]
Signed-off-by: Paul Gortmaker

kbuild: Add extra gcc checks

2012-08-17T19:35:53+00:00

commit 4a5838ad9d2d4f7354a310982483f4c76aa0abeb upstream.

Add a 'W=1' Makefile switch which adds additional checking per build
object.

The idea behind this option is targeted at developers who, in the
process of writing their code, want to do the occasional

make W=1 [target.o]

and let gcc do more extensive code checking for them. Then, they
could eyeball the output for valid gcc warnings about various
bugs/discrepancies which are not reported during the normal build
process.

For more background information and a use case, read through this
thread: http://marc.info/?l=kernel-janitors&m=129802065918147&w=2

Cc: Michal Marek 
Cc: linux-kbuild@vger.kernel.org
Acked-by: Sam Ravnborg 
Acked-by: Ingo Molnar 
Signed-off-by: Borislav Petkov 
Signed-off-by: Michal Marek 
[PG: used for 2.6.34 to better control new compilers on older code]
Signed-off-by: Paul Gortmaker

Linux 2.6.34.12

2012-05-17T15:27:28+00:00

Signed-off-by: Paul Gortmaker

Linux 2.6.34.11

2012-03-19T00:59:27+00:00

Signed-off-by: Paul Gortmaker

Linux 2.6.34.10

2011-06-26T16:47:42+00:00