Home
last modified time | relevance | path

Searched full:workflow (Results 1 – 25 of 54) sorted by relevance

123

/kernel/linux/linux-6.6/Documentation/driver-api/nfc/
Dnfc-hci.rst223 Workflow executing an HCI command (using shdlc)
263 The workflow is the same, except that the API call returns immediately, and
266 Workflow receiving an HCI event or command
/kernel/linux/linux-5.10/Documentation/driver-api/nfc/
Dnfc-hci.rst223 Workflow executing an HCI command (using shdlc)
263 The workflow is the same, except that the API call returns immediately, and
266 Workflow receiving an HCI event or command
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/riscv/
Dextensions.yaml142 to manually trigger workflow. (#2)") of riscv-count-overflow.
148 workflow. (#2)") of riscv-time-compare.
/kernel/linux/linux-6.6/rust/alloc/
DREADME.md20 freedom in both workflow and actual features if actually needed
/kernel/linux/linux-5.10/tools/perf/Documentation/
Dperf-c2c.txt34 The basic workflow with this tool follows the standard record/report phase.
158 The report command workflow is following:
/kernel/linux/linux-6.6/tools/perf/Documentation/
Dperf-c2c.txt39 The basic workflow with this tool follows the standard record/report phase.
176 The report command workflow is following:
/kernel/linux/linux-5.10/Documentation/scsi/
Dhptiop.rst107 I/O Request Workflow of Not Marvell Frey
152 I/O Request Workflow of Marvell Frey
/kernel/linux/linux-6.6/Documentation/scsi/
Dhptiop.rst107 I/O Request Workflow of Not Marvell Frey
152 I/O Request Workflow of Marvell Frey
/kernel/linux/linux-6.6/include/drm/
Dgpu_scheduler.h423 * procedure usually follows the following workflow:
440 * executed sequentially. The above workflow needs to be slightly
/kernel/linux/linux-6.6/Documentation/process/
Dhandling-regressions.rst555 The rules about regressions are always about "breaks user workflow".
603 workflow breaks. Not some test. Not a "look, I used to be able to do
650 Breaking a user workflow for a "bug" is absolutely the WORST reason
772 something breaks existing users' workflow.
D7.AdvancedTopics.rst60 The normal git workflow involves the use of a lot of branches. Each line
Dmaintainer-tip.rst436 this is that the review workflow is email based.
803 workflow of the moment. While the bot message is purely mechanical, it
/kernel/linux/linux-5.10/Documentation/driver-api/
Dpwm.rst141 atomicity in the PWM config workflow, which is required when the PWM controls
/kernel/linux/linux-6.6/Documentation/driver-api/
Dpwm.rst152 atomicity in the PWM config workflow, which is required when the PWM controls
/kernel/linux/linux-6.6/Documentation/maintainer/
Dpull-requests.rst73 the signed tag, so depending on your workflow, you can either
/kernel/linux/linux-5.10/Documentation/maintainer/
Dpull-requests.rst75 the signed tag, so depending on your workflow, you can either
/kernel/linux/linux-6.6/Documentation/driver-api/media/
Dmaintainer-entry-profile.rst44 Media's workflow is heavily based on Patchwork, meaning that, once a patch
/kernel/linux/linux-5.10/Documentation/process/
D7.AdvancedTopics.rst60 The normal git workflow involves the use of a lot of branches. Each line
/kernel/linux/linux-5.10/Documentation/virt/kvm/
Damd-memory-encryption.rst86 context. In a typical workflow, this command should be the first command issued.
/kernel/linux/linux-5.10/Documentation/driver-api/media/drivers/
Dpxa_camera.rst17 Global video workflow
/kernel/linux/linux-6.6/Documentation/mm/
Dmultigen_lru.rst80 Workflow overview
/kernel/linux/linux-6.6/Documentation/driver-api/media/drivers/
Dpxa_camera.rst17 Global video workflow
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Darmada-370.dtsi252 * the standard workflow for CPU idle support (relying
/kernel/linux/linux-6.6/arch/arm/boot/dts/marvell/
Darmada-370.dtsi272 * the standard workflow for CPU idle support (relying
/kernel/linux/linux-5.10/fs/btrfs/
Dqgroup.h58 * So for balance, we use a delayed subtree tracing, whose workflow is:

123