Merge drm/drm-next into drm-intel-next-queued

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.

=====

The MSG_ZEROCOPY flag enables copy avoidance for socket send calls.

The feature is currently implemented for TCP sockets.

The feature is currently implemented for TCP and UDP sockets.

Opportunity and Caveats

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.