Loading Documentation/admin-guide/kernel-parameters.txt +2 −0 Original line number Diff line number Diff line Loading @@ -4713,6 +4713,8 @@ prevent spurious wakeup); n = USB_QUIRK_DELAY_CTRL_MSG (Device needs a pause after every control message); o = USB_QUIRK_HUB_SLOW_RESET (Hub needs extra delay after resetting its port); Example: quirks=0781:5580:bk,0a5c:5834:gij usbhid.mousepoll= Loading Documentation/admin-guide/security-bugs.rst +11 −10 Original line number Diff line number Diff line Loading @@ -32,16 +32,17 @@ Disclosure and embargoed information The security list is not a disclosure channel. For that, see Coordination below. Once a robust fix has been developed, our preference is to release the fix in a timely fashion, treating it no differently than any of the other thousands of changes and fixes the Linux kernel project releases every month. However, at the request of the reporter, we will postpone releasing the fix for up to 5 business days after the date of the report or after the embargo has lifted; whichever comes first. The only exception to that rule is if the bug is publicly known, in which case the preference is to release the fix as soon as it's available. Once a robust fix has been developed, the release process starts. Fixes for publicly known bugs are released immediately. Although our preference is to release fixes for publicly undisclosed bugs as soon as they become available, this may be postponed at the request of the reporter or an affected party for up to 7 calendar days from the start of the release process, with an exceptional extension to 14 calendar days if it is agreed that the criticality of the bug requires more time. The only valid reason for deferring the publication of a fix is to accommodate the logistics of QA and large scale rollouts which require release coordination. Whilst embargoed information may be shared with trusted individuals in order to develop a fix, such information will not be published alongside Loading Documentation/devicetree/bindings/net/dsa/dsa.txt +1 −1 Original line number Diff line number Diff line Loading @@ -7,7 +7,7 @@ limitations. Current Binding --------------- Switches are true Linux devices and can be probes by any means. Once Switches are true Linux devices and can be probed by any means. Once probed, they register to the DSA framework, passing a node pointer. This node is expected to fulfil the following binding, and may contain additional properties as required by the device it is Loading Documentation/media/uapi/v4l/dev-meta.rst +1 −1 Original line number Diff line number Diff line Loading @@ -40,7 +40,7 @@ To use the :ref:`format` ioctls applications set the ``type`` field of the the desired operation. Both drivers and applications must set the remainder of the :c:type:`v4l2_format` structure to 0. .. _v4l2-meta-format: .. c:type:: v4l2_meta_format .. tabularcolumns:: |p{1.4cm}|p{2.2cm}|p{13.9cm}| Loading Documentation/media/uapi/v4l/vidioc-g-fmt.rst +5 −0 Original line number Diff line number Diff line Loading @@ -132,6 +132,11 @@ The format as returned by :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` must be identical - ``sdr`` - Definition of a data format, see :ref:`pixfmt`, used by SDR capture and output devices. * - - struct :c:type:`v4l2_meta_format` - ``meta`` - Definition of a metadata format, see :ref:`meta-formats`, used by metadata capture devices. * - - __u8 - ``raw_data``\ [200] Loading Loading
Documentation/admin-guide/kernel-parameters.txt +2 −0 Original line number Diff line number Diff line Loading @@ -4713,6 +4713,8 @@ prevent spurious wakeup); n = USB_QUIRK_DELAY_CTRL_MSG (Device needs a pause after every control message); o = USB_QUIRK_HUB_SLOW_RESET (Hub needs extra delay after resetting its port); Example: quirks=0781:5580:bk,0a5c:5834:gij usbhid.mousepoll= Loading
Documentation/admin-guide/security-bugs.rst +11 −10 Original line number Diff line number Diff line Loading @@ -32,16 +32,17 @@ Disclosure and embargoed information The security list is not a disclosure channel. For that, see Coordination below. Once a robust fix has been developed, our preference is to release the fix in a timely fashion, treating it no differently than any of the other thousands of changes and fixes the Linux kernel project releases every month. However, at the request of the reporter, we will postpone releasing the fix for up to 5 business days after the date of the report or after the embargo has lifted; whichever comes first. The only exception to that rule is if the bug is publicly known, in which case the preference is to release the fix as soon as it's available. Once a robust fix has been developed, the release process starts. Fixes for publicly known bugs are released immediately. Although our preference is to release fixes for publicly undisclosed bugs as soon as they become available, this may be postponed at the request of the reporter or an affected party for up to 7 calendar days from the start of the release process, with an exceptional extension to 14 calendar days if it is agreed that the criticality of the bug requires more time. The only valid reason for deferring the publication of a fix is to accommodate the logistics of QA and large scale rollouts which require release coordination. Whilst embargoed information may be shared with trusted individuals in order to develop a fix, such information will not be published alongside Loading
Documentation/devicetree/bindings/net/dsa/dsa.txt +1 −1 Original line number Diff line number Diff line Loading @@ -7,7 +7,7 @@ limitations. Current Binding --------------- Switches are true Linux devices and can be probes by any means. Once Switches are true Linux devices and can be probed by any means. Once probed, they register to the DSA framework, passing a node pointer. This node is expected to fulfil the following binding, and may contain additional properties as required by the device it is Loading
Documentation/media/uapi/v4l/dev-meta.rst +1 −1 Original line number Diff line number Diff line Loading @@ -40,7 +40,7 @@ To use the :ref:`format` ioctls applications set the ``type`` field of the the desired operation. Both drivers and applications must set the remainder of the :c:type:`v4l2_format` structure to 0. .. _v4l2-meta-format: .. c:type:: v4l2_meta_format .. tabularcolumns:: |p{1.4cm}|p{2.2cm}|p{13.9cm}| Loading
Documentation/media/uapi/v4l/vidioc-g-fmt.rst +5 −0 Original line number Diff line number Diff line Loading @@ -132,6 +132,11 @@ The format as returned by :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` must be identical - ``sdr`` - Definition of a data format, see :ref:`pixfmt`, used by SDR capture and output devices. * - - struct :c:type:`v4l2_meta_format` - ``meta`` - Definition of a metadata format, see :ref:`meta-formats`, used by metadata capture devices. * - - __u8 - ``raw_data``\ [200] Loading