Merge tag 'v5.5-rc5' into locking/kcsan, to resolve conflict

.. code-block:: c

    struct kcov_remote_arg {

	unsigned	trace_mode;

	unsigned	area_size;

	unsigned	num_handles;

	uint64_t	common_handle;

	uint64_t	handles[0];

	__u32		trace_mode;

	__u32		area_size;

	__u32		num_handles;

	__aligned_u64	common_handle;

	__aligned_u64	handles[0];

    };

    #define KCOV_INIT_TRACE			_IOR('c', 1, unsigned long)

    |    openrisc: | TODO |

    |      parisc: | TODO |

    |     powerpc: |  ok  |

    |       riscv: | TODO |

    |       riscv: |  ok  |

    |        s390: |  ok  |

    |          sh: |  ok  |

    |       sparc: | TODO |

against this restriction and errors out when appropriate. Schedule analysis is

needed to avoid this, which is outside the scope of the document.

At the moment, the time-aware scheduler can only be triggered based on a

standalone clock and not based on PTP time. This means the base-time argument

from tc-taprio is ignored and the schedule starts right away. It also means it

is more difficult to phase-align the scheduler with the other devices in the

network.

Device Tree bindings and board design

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

   volatile-considered-harmful

   botching-up-ioctls

   clang-format

   ../riscv/patch-acceptance

.. only::  subproject and html

    boot-image-header

    pmu

    patch-acceptance

.. only::  subproject and html