Searched full:workflow (Results 1 – 25 of 32) sorted by relevance
12
| /Linux-v6.6/Documentation/driver-api/nfc/ |
| D | nfc-hci.rst | 223 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
|
| /Linux-v6.6/Documentation/devicetree/bindings/riscv/ |
| D | extensions.yaml | 142 to manually trigger workflow. (#2)") of riscv-count-overflow.
148 workflow. (#2)") of riscv-time-compare.
|
| /Linux-v6.6/rust/alloc/ |
| D | README.md | 20 freedom in both workflow and actual features if actually needed
|
| /Linux-v6.6/tools/perf/Documentation/ |
| D | perf-c2c.txt | 39 The basic workflow with this tool follows the standard record/report phase.
176 The report command workflow is following:
|
| /Linux-v6.6/Documentation/scsi/ |
| D | hptiop.rst | 107 I/O Request Workflow of Not Marvell Frey
152 I/O Request Workflow of Marvell Frey
|
| /Linux-v6.6/include/drm/ |
| D | gpu_scheduler.h | 423 * procedure usually follows the following workflow:
440 * executed sequentially. The above workflow needs to be slightly
|
| /Linux-v6.6/Documentation/process/ |
| D | handling-regressions.rst | 555 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.
|
| D | 7.AdvancedTopics.rst | 60 The normal git workflow involves the use of a lot of branches. Each line
|
| D | maintainer-tip.rst | 436 this is that the review workflow is email based.
803 workflow of the moment. While the bot message is purely mechanical, it
|
| D | submitting-patches.rst | 25 their workflow and expectations, see
|
| /Linux-v6.6/Documentation/driver-api/ |
| D | pwm.rst | 152 atomicity in the PWM config workflow, which is required when the PWM controls
|
| /Linux-v6.6/Documentation/maintainer/ |
| D | pull-requests.rst | 73 the signed tag, so depending on your workflow, you can either
|
| /Linux-v6.6/Documentation/driver-api/media/ |
| D | maintainer-entry-profile.rst | 44 Media's workflow is heavily based on Patchwork, meaning that, once a patch
|
| /Linux-v6.6/Documentation/driver-api/media/drivers/ |
| D | pxa_camera.rst | 17 Global video workflow
|
| /Linux-v6.6/Documentation/mm/ |
| D | multigen_lru.rst | 80 Workflow overview
|
| /Linux-v6.6/fs/btrfs/ |
| D | qgroup.h | 59 * So for balance, we use a delayed subtree tracing, whose workflow is:
|
| /Linux-v6.6/arch/arm/boot/dts/marvell/ |
| D | armada-370.dtsi | 272 * the standard workflow for CPU idle support (relying
|
| /Linux-v6.6/Documentation/virt/kvm/x86/ |
| D | amd-memory-encryption.rst | 88 context. In a typical workflow, this command should be the first command issued.
|
| /Linux-v6.6/kernel/cgroup/ |
| D | rstat.c | 151 * cgroup_rstat_flush(), this enables a complete workflow where bpf progs that
|
| /Linux-v6.6/drivers/w1/ |
| D | w1_io.c | 409 * When the workflow with a slave amongst many requires several
|
| /Linux-v6.6/net/openvswitch/ |
| D | vport.c | 231 * workflow. in ovs_vport_add()
|
| /Linux-v6.6/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 51 results, here we focus on the UI based workflow.
64 Shortly after the pull request has been created, the CI workflow will run. Note
|
| D | btf.rst | 565 The workflow typically looks like:
|
| /Linux-v6.6/Documentation/networking/ |
| D | filter.rst | 414 The usual workflow would be to ...
|
| /Linux-v6.6/drivers/scsi/ |
| D | wd719x.c | 22 * Driver workflow:
|
12
