Merge 6.4-rc3 into tty-next

Nicolas Saenz Julienne <nsaenz@kernel.org> <nsaenzjulienne@suse.de>

Nicolas Saenz Julienne <nsaenz@kernel.org> <nsaenzjulienne@suse.com>

Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>

Nikolay Aleksandrov <razor@blackwall.org> <naleksan@redhat.com>

Nikolay Aleksandrov <razor@blackwall.org> <nikolay@redhat.com>

Nikolay Aleksandrov <razor@blackwall.org> <nikolay@cumulusnetworks.com>

Nikolay Aleksandrov <razor@blackwall.org> <nikolay@nvidia.com>

Nikolay Aleksandrov <razor@blackwall.org> <nikolay@isovalent.com>

Oleksandr Natalenko <oleksandr@natalenko.name> <oleksandr@redhat.com>

Oleksij Rempel <linux@rempel-privat.de> <bug-track@fisher-privat.net>

Oleksij Rempel <linux@rempel-privat.de> <external.Oleksij.Rempel@de.bosch.com>

S: D-69126 Heidelberg

S: Germany

N: Neil Horman

M: nhorman@tuxdriver.com

D: SCTP protocol maintainer.

N: Simon Horman

M: horms@verge.net.au

D: Renesas ARM/ARM64 SoC maintainer

   reduce the compile time enormously, especially if you are running an

   universal kernel from a commodity Linux distribution.

   There is a catch: the make target 'localmodconfig' will disable kernel

   features you have not directly or indirectly through some program utilized

   since you booted the system. You can reduce or nearly eliminate that risk by

   using tricks outlined in the reference section; for quick testing purposes

   that risk is often negligible, but it is an aspect you want to keep in mind

   in case your kernel behaves oddly.

   There is a catch: 'localmodconfig' is likely to disable kernel features you

   did not use since you booted your Linux -- like drivers for currently

   disconnected peripherals or a virtualization software not haven't used yet.

   You can reduce or nearly eliminate that risk with tricks the reference

   section outlines; but when building a kernel just for quick testing purposes

   it is often negligible if such features are missing. But you should keep that

   aspect in mind when using a kernel built with this make target, as it might

   be the reason why something you only use occasionally stopped working.

   [:ref:`details<configuration>`]

   does nothing at all; in that case you have to manually install your kernel,

   as outlined in the reference section.

   If you are running a immutable Linux distribution, check its documentation

   and the web to find out how to install your own kernel there.

   [:ref:`details<install>`]

.. _another_sbs:

   version you care about, as git otherwise might retrieve the entire commit

   history::

     git fetch --shallow-exclude=v6.1 origin

   If you modified the sources (for example by applying a patch), you now need

   to discard those modifications; that's because git otherwise will not be able

   to switch to the sources of another version due to potential conflicting

   changes::

     git reset --hard

     git fetch --shallow-exclude=v6.0 origin

   Now checkout the version you are interested in, as explained above::

   Now switch to the version you are interested in -- but be aware the command

   used here will discard any modifications you performed, as they would

   conflict with the sources you want to checkout::

     git checkout --detach origin/master

     git checkout --force --detach origin/master

   At this point you might want to patch the sources again or set/modify a build

   tag, as explained earlier; afterwards adjust the build configuration to the

   new codebase and build your next kernel::

   tag, as explained earlier. Afterwards adjust the build configuration to the

   new codebase using olddefconfig, which will now adjust the configuration file

   you prepared earlier using localmodconfig  (~/linux/.config) for your next

   kernel::

     # reminder: if you want to apply patches, do it at this point

     # reminder: you might want to update your build tag at this point

     make olddefconfig

   Now build your kernel::

     make -j $(nproc --all)

   Install the kernel as outlined above::

   Afterwards install the kernel as outlined above::

     command -v installkernel && sudo make modules_install install

    curl -L \

      https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/clone.bundle \

      -o linux-stable.git.bundle

    git clone clone.bundle ~/linux/

    git clone linux-stable.git.bundle ~/linux/

    rm linux-stable.git.bundle

    cd ~/linux/

    git remote set-url origin

    git remote set-url origin \

      https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    git fetch origin

    git checkout --detach origin/master

   kyber-iosched

   null_blk

   pr

   request

   stat

   switching-sched

   writeback_cache_control

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

struct request documentation

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

Jens Axboe <jens.axboe@oracle.com> 27/05/02

.. FIXME:

   No idea about what does mean - seems just some noise, so comment it

   1.0

   Index

   2.0 Struct request members classification

       2.1 struct request members explanation

   3.0

   2.0

Short explanation of request members

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

Classification flags:

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

	D	driver member

	B	block layer member

	I	I/O scheduler member

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

Unless an entry contains a D classification, a device driver must not access

this member. Some members may contain D classifications, but should only be

access through certain macros or functions (eg ->flags).

<linux/blkdev.h>

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

Member				Flag	Comment

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

struct list_head queuelist	BI	Organization on various internal

					queues

``void *elevator_private``	I	I/O scheduler private data

unsigned char cmd[16]		D	Driver can use this for setting up

					a cdb before execution, see

					blk_queue_prep_rq

unsigned long flags		DBI	Contains info about data direction,

					request type, etc.

int rq_status			D	Request status bits

kdev_t rq_dev			DBI	Target device

int errors			DB	Error counts

sector_t sector			DBI	Target location

unsigned long hard_nr_sectors	B	Used to keep sector sane

unsigned long nr_sectors	DBI	Total number of sectors in request

unsigned long hard_nr_sectors	B	Used to keep nr_sectors sane

unsigned short nr_phys_segments	DB	Number of physical scatter gather

					segments in a request

unsigned short nr_hw_segments	DB	Number of hardware scatter gather

					segments in a request

unsigned int current_nr_sectors	DB	Number of sectors in first segment

					of request

unsigned int hard_cur_sectors	B	Used to keep current_nr_sectors sane

int tag				DB	TCQ tag, if assigned

``void *special``		D	Free to be used by driver

``char *buffer``		D	Map of first segment, also see

					section on bouncing SECTION

``struct completion *waiting``	D	Can be used by driver to get signalled

					on request completion

``struct bio *bio``		DBI	First bio in request

``struct bio *biotail``		DBI	Last bio in request

``struct request_queue *q``	DB	Request queue this request belongs to

``struct request_list *rl``	B	Request list this request came from

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