Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net

N: Helge Deller

E: deller@gmx.de

E: hdeller@redhat.de

D: PA-RISC Linux hacker, LASI-, ASP-, WAX-, LCD/LED-driver

S: Schimmelsrain 1

S: D-69231 Rauenberg

W: http://www.parisc-linux.org/

D: PA-RISC Linux architecture maintainer

D: LASI-, ASP-, WAX-, LCD/LED-driver

S: Germany

N: Jean Delvare

S: South Africa

N: Grant Grundler

E: grundler@parisc-linux.org

E: grantgrundler@gmail.com

W: http://obmouse.sourceforge.net/

W: http://www.parisc-linux.org/

D: obmouse - rewrote Olivier Florent's Omnibook 600 "pop-up" mouse driver

S: USA

N: Kyle McMartin

E: kyle@parisc-linux.org

E: kyle@mcmartin.ca

D: Linux/PARISC hacker

D: AD1889 sound driver

S: Ottawa, Canada

S: Cupertino, CA 95014

S: USA

N: Thibaut Varene

E: T-Bone@parisc-linux.org

W: http://www.parisc-linux.org/~varenet/

P: 1024D/B7D2F063 E67C 0D43 A75E 12A5 BB1C  FA2F 1E32 C3DA B7D2 F063

N: Thibaut Varène

E: hacks+kernel@slashdirt.org

W: http://hacks.slashdirt.org/

D: PA-RISC port minion, PDC and GSCPS2 drivers, debuglocks and other bits

D: Some ARM at91rm9200 bits, S1D13XXX FB driver, random patches here and there

D: AD1889 sound driver

S: Paris, France

S: France

N: Heikki Vatiainen

E: hessu@cs.tut.fi

.. _readme:

Linux kernel release 4.x <http://kernel.org/>

Linux kernel release 5.x <http://kernel.org/>

=============================================

These are the release notes for Linux version 4.  Read them carefully,

These are the release notes for Linux version 5.  Read them carefully,

as they tell you what this is all about, explain how to install the

kernel, and what to do if something goes wrong.

   directory where you have permissions (e.g. your home directory) and

   unpack it::

     xz -cd linux-4.X.tar.xz | tar xvf -

     xz -cd linux-5.x.tar.xz | tar xvf -

   Replace "X" with the version number of the latest kernel.

   files.  They should match the library, and not get messed up by

   whatever the kernel-du-jour happens to be.

 - You can also upgrade between 4.x releases by patching.  Patches are

 - You can also upgrade between 5.x releases by patching.  Patches are

   distributed in the xz format.  To install by patching, get all the

   newer patch files, enter the top level directory of the kernel source

   (linux-4.X) and execute::

   (linux-5.x) and execute::

     xz -cd ../patch-4.x.xz | patch -p1

     xz -cd ../patch-5.x.xz | patch -p1

   Replace "x" for all versions bigger than the version "X" of your current

   Replace "x" for all versions bigger than the version "x" of your current

   source tree, **in_order**, and you should be ok.  You may want to remove

   the backup files (some-file-name~ or some-file-name.orig), and make sure

   that there are no failed patches (some-file-name# or some-file-name.rej).

   If there are, either you or I have made a mistake.

   Unlike patches for the 4.x kernels, patches for the 4.x.y kernels

   Unlike patches for the 5.x kernels, patches for the 5.x.y kernels

   (also known as the -stable kernels) are not incremental but instead apply

   directly to the base 4.x kernel.  For example, if your base kernel is 4.0

   and you want to apply the 4.0.3 patch, you must not first apply the 4.0.1

   and 4.0.2 patches. Similarly, if you are running kernel version 4.0.2 and

   want to jump to 4.0.3, you must first reverse the 4.0.2 patch (that is,

   patch -R) **before** applying the 4.0.3 patch. You can read more on this in

   directly to the base 5.x kernel.  For example, if your base kernel is 5.0

   and you want to apply the 5.0.3 patch, you must not first apply the 5.0.1

   and 5.0.2 patches. Similarly, if you are running kernel version 5.0.2 and

   want to jump to 5.0.3, you must first reverse the 5.0.2 patch (that is,

   patch -R) **before** applying the 5.0.3 patch. You can read more on this in

   :ref:`Documentation/process/applying-patches.rst <applying_patches>`.

   Alternatively, the script patch-kernel can be used to automate this

Software requirements

---------------------

   Compiling and running the 4.x kernels requires up-to-date

   Compiling and running the 5.x kernels requires up-to-date

   versions of various software packages.  Consult

   :ref:`Documentation/process/changes.rst <changes>` for the minimum version numbers

   required and how to get updates for these packages.  Beware that using

   place for the output files (including .config).

   Example::

     kernel source code: /usr/src/linux-4.X

     kernel source code: /usr/src/linux-5.x

     build directory:    /home/name/build/kernel

   To configure and build the kernel, use::

     cd /usr/src/linux-4.X

     cd /usr/src/linux-5.x

     make O=/home/name/build/kernel menuconfig

     make O=/home/name/build/kernel

     sudo make O=/home/name/build/kernel modules_install install

  function that the driver has to call for each VLAN the given port is a member

  of. A switchdev object is used to carry the VID and bridge flags.

- port_fdb_prepare: bridge layer function invoked when the bridge prepares the

  installation of a Forwarding Database entry. If the operation is not

  supported, this function should return -EOPNOTSUPP to inform the bridge code

  to fallback to a software implementation. No hardware setup must be done in

  this function. See port_fdb_add for this and details.

- port_fdb_add: bridge layer function invoked when the bridge wants to install a

  Forwarding Database entry, the switch hardware should be programmed with the

  specified address in the specified VLAN Id in the forwarding database

  associated with this VLAN ID

  associated with this VLAN ID. If the operation is not supported, this

  function should return -EOPNOTSUPP to inform the bridge code to fallback to

  a software implementation.

Note: VLAN ID 0 corresponds to the port private database, which, in the context

of DSA, would be the its port-based VLAN, used by the associated bridge device.

Switch ID

^^^^^^^^^

The switchdev driver must implement the switchdev op switchdev_port_attr_get

for SWITCHDEV_ATTR_ID_PORT_PARENT_ID for each port netdev, returning the same

physical ID for each port of a switch.  The ID must be unique between switches

on the same system.  The ID does not need to be unique between switches on

different systems.

The switchdev driver must implement the net_device operation

ndo_get_port_parent_id for each port netdev, returning the same physical ID for

each port of a switch. The ID must be unique between switches on the same

system. The ID does not need to be unique between switches on different

systems.

The switch ID is used to locate ports on a switch and to know if aggregated

ports belong to the same switch.

generate a patch representing the differences between two patches and then

apply the result.

This will let you move from something like 4.7.2 to 4.7.3 in a single

This will let you move from something like 5.7.2 to 5.7.3 in a single

step. The -z flag to interdiff will even let you feed it patches in gzip or

bzip2 compressed form directly without the use of zcat or bzcat or manual

decompression.

Here's how you'd go from 4.7.2 to 4.7.3 in a single step::

Here's how you'd go from 5.7.2 to 5.7.3 in a single step::

	interdiff -z ../patch-4.7.2.gz ../patch-4.7.3.gz | patch -p1

	interdiff -z ../patch-5.7.2.gz ../patch-5.7.3.gz | patch -p1

Although interdiff may save you a step or two you are generally advised to

do the additional steps since interdiff can get things wrong in some cases.

Most recent patches are linked from the front page, but they also have

specific homes.

The 4.x.y (-stable) and 4.x patches live at

The 5.x.y (-stable) and 5.x patches live at

	https://www.kernel.org/pub/linux/kernel/v4.x/

	https://www.kernel.org/pub/linux/kernel/v5.x/

The -rc patches live at

The -rc patches are not stored on the webserver but are generated on

demand from git tags such as

	https://www.kernel.org/pub/linux/kernel/v4.x/testing/

	https://git.kernel.org/torvalds/p/v5.1-rc1/v5.0

The stable -rc patches live at

The 4.x kernels

	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/

The 5.x kernels

===============

These are the base stable releases released by Linus. The highest numbered

release is the most recent.

If regressions or other serious flaws are found, then a -stable fix patch

will be released (see below) on top of this base. Once a new 4.x base

will be released (see below) on top of this base. Once a new 5.x base

kernel is released, a patch is made available that is a delta between the

previous 4.x kernel and the new one.

previous 5.x kernel and the new one.

To apply a patch moving from 4.6 to 4.7, you'd do the following (note

that such patches do **NOT** apply on top of 4.x.y kernels but on top of the

base 4.x kernel -- if you need to move from 4.x.y to 4.x+1 you need to

first revert the 4.x.y patch).

To apply a patch moving from 5.6 to 5.7, you'd do the following (note

that such patches do **NOT** apply on top of 5.x.y kernels but on top of the

base 5.x kernel -- if you need to move from 5.x.y to 5.x+1 you need to

first revert the 5.x.y patch).

Here are some examples::

	# moving from 4.6 to 4.7

	# moving from 5.6 to 5.7

	$ cd ~/linux-4.6		# change to kernel source dir

	$ patch -p1 < ../patch-4.7	# apply the 4.7 patch

	$ cd ~/linux-5.6		# change to kernel source dir

	$ patch -p1 < ../patch-5.7	# apply the 5.7 patch

	$ cd ..

	$ mv linux-4.6 linux-4.7	# rename source dir

	$ mv linux-5.6 linux-5.7	# rename source dir

	# moving from 4.6.1 to 4.7

	# moving from 5.6.1 to 5.7

	$ cd ~/linux-4.6.1		# change to kernel source dir

	$ patch -p1 -R < ../patch-4.6.1	# revert the 4.6.1 patch

					# source dir is now 4.6

	$ patch -p1 < ../patch-4.7	# apply new 4.7 patch

	$ cd ~/linux-5.6.1		# change to kernel source dir

	$ patch -p1 -R < ../patch-5.6.1	# revert the 5.6.1 patch

					# source dir is now 5.6

	$ patch -p1 < ../patch-5.7	# apply new 5.7 patch

	$ cd ..

	$ mv linux-4.6.1 linux-4.7	# rename source dir

	$ mv linux-5.6.1 linux-5.7	# rename source dir

The 4.x.y kernels

The 5.x.y kernels

=================

Kernels with 3-digit versions are -stable kernels. They contain small(ish)

critical fixes for security problems or significant regressions discovered

in a given 4.x kernel.

in a given 5.x kernel.

This is the recommended branch for users who want the most recent stable

kernel and are not interested in helping test development/experimental

versions.

If no 4.x.y kernel is available, then the highest numbered 4.x kernel is

If no 5.x.y kernel is available, then the highest numbered 5.x kernel is

the current stable kernel.

.. note::

 The -stable team usually do make incremental patches available as well

 as patches against the latest mainline release, but I only cover the

 non-incremental ones below. The incremental ones can be found at

 https://www.kernel.org/pub/linux/kernel/v4.x/incr/

 https://www.kernel.org/pub/linux/kernel/v5.x/incr/

These patches are not incremental, meaning that for example the 4.7.3

patch does not apply on top of the 4.7.2 kernel source, but rather on top

of the base 4.7 kernel source.

These patches are not incremental, meaning that for example the 5.7.3

patch does not apply on top of the 5.7.2 kernel source, but rather on top

of the base 5.7 kernel source.

So, in order to apply the 4.7.3 patch to your existing 4.7.2 kernel

source you have to first back out the 4.7.2 patch (so you are left with a

base 4.7 kernel source) and then apply the new 4.7.3 patch.

So, in order to apply the 5.7.3 patch to your existing 5.7.2 kernel

source you have to first back out the 5.7.2 patch (so you are left with a

base 5.7 kernel source) and then apply the new 5.7.3 patch.

Here's a small example::

	$ cd ~/linux-4.7.2		# change to the kernel source dir

	$ patch -p1 -R < ../patch-4.7.2	# revert the 4.7.2 patch

	$ patch -p1 < ../patch-4.7.3	# apply the new 4.7.3 patch

	$ cd ~/linux-5.7.2		# change to the kernel source dir

	$ patch -p1 -R < ../patch-5.7.2	# revert the 5.7.2 patch

	$ patch -p1 < ../patch-5.7.3	# apply the new 5.7.3 patch

	$ cd ..

	$ mv linux-4.7.2 linux-4.7.3	# rename the kernel source dir

	$ mv linux-5.7.2 linux-5.7.3	# rename the kernel source dir

The -rc kernels

===============

development kernels but do not want to run some of the really experimental

stuff (such people should see the sections about -next and -mm kernels below).

The -rc patches are not incremental, they apply to a base 4.x kernel, just

like the 4.x.y patches described above. The kernel version before the -rcN

The -rc patches are not incremental, they apply to a base 5.x kernel, just

like the 5.x.y patches described above. The kernel version before the -rcN

suffix denotes the version of the kernel that this -rc kernel will eventually

turn into.

So, 4.8-rc5 means that this is the fifth release candidate for the 4.8

kernel and the patch should be applied on top of the 4.7 kernel source.

So, 5.8-rc5 means that this is the fifth release candidate for the 5.8

kernel and the patch should be applied on top of the 5.7 kernel source.

Here are 3 examples of how to apply these patches::

	# first an example of moving from 4.7 to 4.8-rc3

	# first an example of moving from 5.7 to 5.8-rc3

	$ cd ~/linux-4.7			# change to the 4.7 source dir

	$ patch -p1 < ../patch-4.8-rc3		# apply the 4.8-rc3 patch

	$ cd ~/linux-5.7			# change to the 5.7 source dir

	$ patch -p1 < ../patch-5.8-rc3		# apply the 5.8-rc3 patch

	$ cd ..

	$ mv linux-4.7 linux-4.8-rc3		# rename the source dir

	$ mv linux-5.7 linux-5.8-rc3		# rename the source dir

	# now let's move from 4.8-rc3 to 4.8-rc5

	# now let's move from 5.8-rc3 to 5.8-rc5

	$ cd ~/linux-4.8-rc3			# change to the 4.8-rc3 dir

	$ patch -p1 -R < ../patch-4.8-rc3	# revert the 4.8-rc3 patch

	$ patch -p1 < ../patch-4.8-rc5		# apply the new 4.8-rc5 patch

	$ cd ~/linux-5.8-rc3			# change to the 5.8-rc3 dir

	$ patch -p1 -R < ../patch-5.8-rc3	# revert the 5.8-rc3 patch

	$ patch -p1 < ../patch-5.8-rc5		# apply the new 5.8-rc5 patch

	$ cd ..

	$ mv linux-4.8-rc3 linux-4.8-rc5	# rename the source dir

	$ mv linux-5.8-rc3 linux-5.8-rc5	# rename the source dir

	# finally let's try and move from 4.7.3 to 4.8-rc5

	# finally let's try and move from 5.7.3 to 5.8-rc5

	$ cd ~/linux-4.7.3			# change to the kernel source dir

	$ patch -p1 -R < ../patch-4.7.3		# revert the 4.7.3 patch

	$ patch -p1 < ../patch-4.8-rc5		# apply new 4.8-rc5 patch

	$ cd ~/linux-5.7.3			# change to the kernel source dir

	$ patch -p1 -R < ../patch-5.7.3		# revert the 5.7.3 patch

	$ patch -p1 < ../patch-5.8-rc5		# apply new 5.8-rc5 patch

	$ cd ..

	$ mv linux-4.7.3 linux-4.8-rc5		# rename the kernel source dir

	$ mv linux-5.7.3 linux-5.8-rc5		# rename the kernel source dir

The -mm patches and the linux-next tree