linux-stable.git/Documentation/process, branch v4.19.78

stable-kernel-rules.rst: add link to networking patch queue

2019-03-23T19:10:10+00:00

commit a41e8f25fa8f8f67360d88eb0eebbabe95a64bdf upstream.

The networking maintainer keeps a public list of the patches being
queued up for the next round of stable releases.  Be sure to check there
before asking for a patch to be applied so that you do not waste
people's time.

Signed-off-by: Greg Kroah-Hartman 
Acked-by: David S. Miller 
Signed-off-by: Jonathan Corbet 
Signed-off-by: Greg Kroah-Hartman

Code of Conduct: Change the contact email address

2018-10-22T06:33:36+00:00

The contact point for the kernel's Code of Conduct should now be the
Code of Conduct Committee, not the full TAB.  Change the email address
in the file to properly reflect this.

Acked-by: Chris Mason 
Acked-by: Olof Johansson 
Acked-by: Theodore Ts'o 
Acked-by: Thomas Gleixner 
Signed-off-by: Greg Kroah-Hartman

Code of Conduct Interpretation: Put in the proper URL for the committee

2018-10-22T06:33:36+00:00

There was a blank  reference for how to find the Code of Conduct
Committee.  Fix that up by pointing it to the correct kernel.org website
page location.

Acked-by: Chris Mason 
Acked-by: Olof Johansson 
Acked-by: Theodore Ts'o 
Acked-by: Thomas Gleixner 
Signed-off-by: Greg Kroah-Hartman

Code of Conduct: Provide links between the two documents

2018-10-22T06:33:36+00:00

Create a link between the Code of Conduct and the Code of Conduct
Interpretation so that people can see that they are related.

Acked-by: Chris Mason 
Acked-by: Olof Johansson 
Acked-by: Theodore Ts'o 
Acked-by: Thomas Gleixner 
Signed-off-by: Greg Kroah-Hartman

Code of Conduct Interpretation: Properly reference the TAB correctly

2018-10-22T06:33:35+00:00

We use the term "TAB" before defining it later in the document.  Fix
that up by defining it at the first location.

Reported-by: Kuninori Morimoto 
Acked-by: Chris Mason 
Acked-by: Olof Johansson 
Acked-by: Theodore Ts'o 
Acked-by: Thomas Gleixner 
Signed-off-by: Greg Kroah-Hartman

Code of Conduct Interpretation: Add document explaining how the Code of Conduct is to be interpreted

2018-10-22T06:33:35+00:00

The Contributor Covenant Code of Conduct is a general document meant to
provide a set of rules for almost any open source community.  Every
open-source community is unique and the Linux kernel is no exception.
Because of this, this document describes how we in the Linux kernel
community will interpret it.  We also do not expect this interpretation
to be static over time, and will adjust it as needed.

This document was created with the input and feedback of the TAB as well
as many current kernel maintainers.

Co-Developed-by: Thomas Gleixner 
Co-Developed-by: Olof Johansson 
Acked-by: Alex Deucher 
Acked-by: Alexei Starovoitov 
Acked-by: Amir Goldstein 
Acked-by: Andrew Morton 
Acked-by: Andy Lutomirski 
Acked-by: Anna-Maria Gleixner 
Acked-by: Ard Biesheuvel 
Acked-by: Benjamin Herrenschmidt 
Acked-by: Boris Brezillon 
Acked-by: Borislav Petkov 
Acked-by: Chris Mason 
Acked-by: Christian Lütke-Stetzkamp 
Acked-by: Colin Ian King 
Acked-by: Dan Carpenter 
Acked-by: Dan Williams 
Acked-by: Daniel Borkmann 
Acked-by: Daniel Vetter 
Acked-by: Dave Airlie 
Acked-by: Dave Hansen 
Acked-by: David Ahern 
Acked-by: David Sterba 
Acked-by: Dmitry Torokhov 
Acked-by: Dominik Brodowski 
Acked-by: Eric Dumazet 
Acked-by: Felipe Balbi 
Acked-by: Felix Kuehling 
Acked-by: Florian Fainelli 
Acked-by: Geert Uytterhoeven 
Acked-by: Grant Likely 
Acked-by: Gregory CLEMENT 
Acked-by: Guenter Roeck 
Acked-by: Gustavo A. R. Silva 
Acked-by: Hans Verkuil 
Acked-by: Hans de Goede 
Acked-by: Harry Wentland 
Acked-by: Heiko Stuebner 
Acked-by: Ingo Molnar 
Acked-by: Jaegeuk Kim 
Acked-by: James Smart 
Acked-by: James Smart 
Acked-by: Jan Kara 
Acked-by: Jani Nikula 
Acked-by: Jason A. Donenfeld 
Acked-by: Jeff Kirsher 
Acked-by: Jens Axboe 
Acked-by: Jessica Yu 
Acked-by: Jia-Ju Bai 
Acked-by: Jiri Kosina 
Acked-by: Jiri Olsa 
Acked-by: Joerg Roedel 
Acked-by: Johan Hovold 
Acked-by: Johannes Thumshirn 
Acked-by: Jonathan Corbet 
Acked-by: Julia Lawall 
Acked-by: Kees Cook 
Acked-by: Kirill Tkhai 
Acked-by: Kuninori Morimoto 
Acked-by: Laurent Pinchart 
Acked-by: Lina Iyer 
Acked-by: Linus Torvalds 
Acked-by: Linus Walleij 
Acked-by: Mark Brown 
Acked-by: Masahiro Yamada 
Acked-by: Masami Hiramatsu 
Acked-by: Mathieu Desnoyers 
Acked-by: Matias Bjørling 
Acked-by: Mauro Carvalho Chehab 
Acked-by: Maxime Ripard 
Acked-by: Michael Ellerman 
Acked-by: Mike Rapoport 
Acked-by: Mimi Zohar 
Acked-by: Miquel Raynal 
Acked-by: Mishi Choudhary 
Acked-by: Nikolay Borisov 
Acked-by: Oded Gabbay 
Acked-by: Palmer Dabbelt 
Acked-by: Paul E. McKenney 
Acked-by: Peter Zijlstra 
Acked-by: Rafael J. Wysocki 
Acked-by: Richard Weinberger 
Acked-by: Rik van Riel 
Acked-by: Rob Clark 
Acked-by: Rob Herring 
Acked-by: Rodrigo Vivi 
Acked-by: Sean Paul 
Acked-by: Sebastian Andrzej Siewior 
Acked-by: Sebastian Reichel 
Acked-by: Sergio Paracuellos 
Acked-by: Shawn Guo 
Acked-by: Shuah Khan 
Acked-by: Simon Horman 
Acked-by: Srinivas Kandagatla 
Acked-by: Stephen Hemminger 
Acked-by: Takashi Iwai 
Acked-by: Tejun Heo 
Acked-by: Theodore Ts'o 
Acked-by: Thierry Reding 
Acked-by: Todd Poynor 
Acked-by: Viresh Kumar 
Acked-by: Wei Yongjun 
Acked-by: YueHaibing 
Reviewed-by: Steven Rostedt 
Signed-off-by: Thomas Gleixner 
Signed-off-by: Olof Johansson 
Signed-off-by: Greg Kroah-Hartman

Code of conduct: Fix wording around maintainers enforcing the code of conduct

2018-10-22T06:33:35+00:00

As it was originally worded, this paragraph requires maintainers to
enforce the code of conduct, or face potential repercussions.  It sends
the wrong message, when really we just want maintainers to be part of
the solution and not violate the code of conduct themselves.

Removing it doesn't limit our ability to enforce the code of conduct,
and we can still encourage maintainers to help maintain high standards
for the level of discourse in their subsystem.

Signed-off-by: Chris Mason 
Acked-by: Alex Deucher 
Acked-by: Amir Goldstein 
Acked-by: Andrew Morton 
Acked-by: Anna-Maria Gleixner 
Acked-by: Ard Biesheuvel 
Acked-by: Benjamin Herrenschmidt 
Acked-by: Boris Brezillon 
Acked-by: Borislav Petkov 
Acked-by: Christian Lütke-Stetzkamp 
Acked-by: Christoph Hellwig 
Acked-by: Colin Ian King 
Acked-by: Dan Carpenter 
Acked-by: Dan Williams 
Acked-by: Daniel Borkmann 
Acked-by: Dave Airlie 
Acked-by: Dave Hansen 
Acked-by: David Ahern 
Acked-by: David Sterba 
Acked-by: Dmitry Torokhov 
Acked-by: Dominik Brodowski 
Acked-by: Eric Dumazet 
Acked-by: Felipe Balbi 
Acked-by: Felix Kuehling 
Acked-by: Florian Fainelli 
Acked-by: Florian Westphal 
Acked-by: Geert Uytterhoeven 
Acked-by: Grant Likely 
Acked-by: Gregory CLEMENT 
Acked-by: Guenter Roeck 
Acked-by: Gustavo A. R. Silva 
Acked-by: Hans Verkuil 
Acked-by: Hans de Goede 
Acked-by: Harry Wentland 
Acked-by: Heiko Stuebner 
Acked-by: Ingo Molnar 
Acked-by: Jaegeuk Kim 
Acked-by: James Smart 
Acked-by: James Smart 
Acked-by: Jan Kara 
Acked-by: Jason A. Donenfeld 
Acked-by: Jeff Kirsher 
Acked-by: Jens Axboe 
Acked-by: Jessica Yu 
Acked-by: Jia-Ju Bai 
Acked-by: Jiri Kosina 
Acked-by: Jiri Olsa 
Acked-by: Joerg Roedel 
Acked-by: Johan Hovold 
Acked-by: Johannes Thumshirn 
Acked-by: Jonathan Corbet 
Acked-by: Julia Lawall 
Acked-by: Kees Cook 
Acked-by: Kirill Tkhai 
Acked-by: Kuninori Morimoto 
Acked-by: Laurent Pinchart 
Acked-by: Lina Iyer 
Acked-by: Linus Torvalds 
Acked-by: Linus Walleij 
Acked-by: Mark Brown 
Acked-by: Masahiro Yamada 
Acked-by: Masami Hiramatsu 
Acked-by: Mathieu Desnoyers 
Acked-by: Matias Bjørling 
Acked-by: Maxime Ripard 
Acked-by: Michael Ellerman 
Acked-by: Mike Rapoport 
Acked-by: Mimi Zohar 
Acked-by: Miquel Raynal 
Acked-by: Nikolay Borisov 
Acked-by: Oded Gabbay 
Acked-by: Olof Johansson 
Acked-by: Palmer Dabbelt 
Acked-by: Paul E. McKenney 
Acked-by: Peter Zijlstra 
Acked-by: Rafael J. Wysocki 
Acked-by: Richard Weinberger 
Acked-by: Rik van Riel 
Acked-by: Rob Clark 
Acked-by: Rob Herring 
Acked-by: Rodrigo Vivi 
Acked-by: Sebastian Andrzej Siewior 
Acked-by: Sebastian Reichel 
Acked-by: Sergio Paracuellos 
Acked-by: Shawn Guo 
Acked-by: Shuah Khan 
Acked-by: Simon Horman 
Acked-by: Srinivas Kandagatla 
Acked-by: Stephen Hemminger 
Acked-by: Takashi Iwai 
Acked-by: Tejun Heo 
Acked-by: Theodore Ts'o 
Acked-by: Thierry Reding 
Acked-by: Thomas Gleixner 
Acked-by: Tim Bird 
Acked-by: Todd Poynor 
Acked-by: Trond Myklebust 
Acked-by: Viresh Kumar 
Acked-by: Wei Yongjun 
Acked-by: YueHaibing 
Reviewed-by: Mauro Carvalho Chehab 
Reviewed-by: Steven Rostedt 
Signed-off-by: Greg Kroah-Hartman

Code of Conduct: Let's revamp it.

2018-09-16T18:42:28+00:00

The Code of Conflict is not achieving its implicit goal of fostering
civility and the spirit of 'be excellent to each other'.  Explicit
guidelines have demonstrated success in other projects and other areas
of the kernel.

Here is a Code of Conduct statement for the wider kernel.  It is based
on the Contributor Covenant as described at www.contributor-covenant.org

From this point forward, we should abide by these rules in order to help
make the kernel community a welcoming environment to participate in.

Signed-off-by: Chris Mason 
Signed-off-by: Dan Williams 
Signed-off-by: Jonathan Corbet 
Signed-off-by: Olof Johansson 
Signed-off-by: Steven Rostedt (VMware) 
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Linus Torvalds

kconfig: do not require pkg-config on make {menu,n}config

2018-09-02T17:13:48+00:00

Meelis Roos reported a {menu,n}config regression:
 "I have libncurses devel package installed in the default system
  location (as do 99%+ on actual developers probably) and in this
  case, pkg-config is useless.  pkg-config is needed only when
  libraries and headers are installed in non-default locations but
  it is bad to require installation of pkg-config on all the machines
  where make menuconfig would be possibly run."

For {menu,n}config, do not use pkg-config if it is not installed.
For {g,x}config, keep checking pkg-config since we really rely on it
for finding the installation paths of the required packages.

Fixes: 4ab3b80159d4 ("kconfig: check for pkg-config on make {menu,n,g,x}config")
Reported-by: Meelis Roos 
Signed-off-by: Masahiro Yamada 
Tested-by: Meelis Roos 
Tested-by: Randy Dunlap

Raise the minimum required gcc version to 4.6

2018-08-20T21:12:38+00:00

Various architectures fail to build properly with older versions of the
gcc compiler.

An example from Guenter Roeck in thread [1]:
>
>   In file included from ./include/linux/mm.h:17:0,
>                    from ./include/linux/pid_namespace.h:7,
>                    from ./include/linux/ptrace.h:10,
>                    from arch/openrisc/kernel/asm-offsets.c:32:
>   ./include/linux/mm_types.h:497:16: error: flexible array member in otherwise empty struct
>
> This is just an example with gcc 4.5.1 for or32. I have seen the problem
> with gcc 4.4 (for unicore32) as well.

So update the minimum required version of gcc to 4.6.

[1] https://lore.kernel.org/lkml/20180814170904.GA12768@roeck-us.net/

Miscellanea:

 - Update Documentation/process/changes.rst

 - Remove and consolidate version test blocks in compiler-gcc.h for
   versions lower than 4.6

Signed-off-by: Joe Perches 
Reviewed-by: Kees Cook 
Reviewed-by: Nick Desaulniers 
Signed-off-by: Linus Torvalds