Searched full:markers (Results 1 – 18 of 18) sorted by relevance
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-jpeg.rst | 56 markers (m = 0..7). The purpose of these markers is to additionally
62 markers will not be inserted.
82 Specify which JPEG markers are included in compressed stream. This
|
| D | vidioc-g-jpegcomp.rst | 40 markers control.
89 - See :ref:`jpeg-markers`. Deprecated. If
96 .. _jpeg-markers:
98 .. flat-table:: JPEG Markers Flags
|
| /Documentation/devicetree/bindings/mtd/ |
| D | raw-nand-chip.yaml | 66 find Bad Block Markers (BBM). These markers will help to
|
| /Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 236 # V4L2 JPEG markers
237 replace define V4L2_JPEG_MARKER_DHT jpeg-markers
238 replace define V4L2_JPEG_MARKER_DQT jpeg-markers
239 replace define V4L2_JPEG_MARKER_DRI jpeg-markers
240 replace define V4L2_JPEG_MARKER_COM jpeg-markers
241 replace define V4L2_JPEG_MARKER_APP jpeg-markers
|
| /Documentation/process/ |
| D | backporting.rst | 43 destination tree, as this will make git output conflict markers and let
105 edits the files to include so-called conflict markers showing you where
247 Understanding conflict markers
255 inserted conflict markers into your file. Out of the box, this will look
277 from its normal behavior. Notice the two columns of diff markers
374 For particularly nasty conflicts with many conflict markers, you can use
385 renamed, as that typically means git won't even put in conflict markers,
|
| D | coding-style.rst | 1094 indicated with special markers. For example, emacs interprets lines marked
1111 Vim interprets markers that look like this:
1119 includes markers for indentation and mode configuration. People may use their
|
| /Documentation/trace/ |
| D | mmiotrace.rst | 70 During tracing you can place comments (markers) into the trace by
73 which action. It is recommended to place descriptive markers about what you
|
| D | ftrace.rst | 1110 markers
1305 markers
|
| /Documentation/power/ |
| D | s2ram.rst | 24 time-consuming - having to insert TRACE_RESUME() markers into the device
|
| /Documentation/ |
| D | dontdiff | 75 Module.markers
|
| /Documentation/arch/x86/ |
| D | shstk.rst | 50 The kernel does not process these applications markers directly. Applications
|
| /Documentation/input/ |
| D | event-codes.rst | 36 - Used as markers to separate events. Events may be separated in time or in
|
| /Documentation/dev-tools/ |
| D | checkpatch.rst | 858 It is possible to use section markers on variables in a way
1211 Since linux moved to git, the CVS markers are no longer used.
|
| /Documentation/RCU/ |
| D | checklist.rst | 359 and the read-side markers (rcu_read_lock() and rcu_read_unlock(),
|
| D | RTFP.txt | 1931 ,Title="Re: [patch 1/2] {Linux} Kernel Markers - Support Multiple Probes"
|
| /Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 76 with the marker rcu_read_unlock(). These markers may be nested, and
698 Reader-side markers such as rcu_read_lock() and
2595 anywhere in the code, it is not possible to use read-side markers such
2597 not work to have these markers in the trampoline itself, because there
|
| /Documentation/scsi/ |
| D | ChangeLog.lpfc | 428 * Fix sparse warnings by adding __iomem markers to lpfc_compat.h.
|
| /Documentation/networking/ |
| D | ethtool-netlink.rst | 611 alignment markers lock
|