Searched full:workflow (Results 1 – 25 of 35) sorted by relevance
12
| /linux-6.15/Documentation/dev-tools/ |
| D | propeller.rst | 97 Workflow chapter
100 Here is an example workflow for building an AutoFDO+Propeller kernel:
|
| D | autofdo.rst | 96 Workflow chapter
99 Here is an example workflow for AutoFDO kernel:
|
| /linux-6.15/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-6.15/rust/pin-init/ |
| D | README.md | 6 ![GitHub Workflow Status](https://img.shields.io/github/actions/workflow/status/Rust-for-Linux/pin-…
|
| /linux-6.15/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-6.15/Documentation/scsi/ |
| D | hptiop.rst | 107 I/O Request Workflow of Not Marvell Frey
152 I/O Request Workflow of Marvell Frey
|
| /linux-6.15/Documentation/mm/damon/ |
| D | maintainer-profile.rst | 79 support DAMON and general Linux kernel development workflow.
|
| /linux-6.15/Documentation/process/ |
| D | handling-regressions.rst | 561 The rules about regressions are always about "breaks user workflow".
609 workflow breaks. Not some test. Not a "look, I used to be able to do
656 Breaking a user workflow for a "bug" is absolutely the WORST reason
778 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 | 452 this is that the review workflow is email based.
847 workflow of the moment. While the bot message is purely mechanical, it
|
| /linux-6.15/drivers/gpu/drm/xe/ |
| D | xe_survivability_mode.c | 25 * Boot Survivability is a software based workflow for recovering a system in a failed boot state
|
| /linux-6.15/include/drm/ |
| D | gpu_scheduler.h | 427 * procedure usually follows the following workflow:
444 * executed sequentially. The above workflow needs to be slightly
|
| /linux-6.15/Documentation/driver-api/ |
| D | pwm.rst | 162 atomicity in the PWM config workflow, which is required when the PWM controls
|
| /linux-6.15/Documentation/maintainer/ |
| D | pull-requests.rst | 73 the signed tag, so depending on your workflow, you can either
|
| /linux-6.15/Documentation/driver-api/media/ |
| D | maintainer-entry-profile.rst | 44 Media's workflow is heavily based on Patchwork, meaning that, once a patch
|
| /linux-6.15/Documentation/devicetree/bindings/riscv/ |
| D | extensions.yaml | 160 to manually trigger workflow. (#2)") of riscv-count-overflow.
172 workflow. (#2)") of riscv-time-compare.
|
| /linux-6.15/Documentation/driver-api/media/drivers/ |
| D | pxa_camera.rst | 17 Global video workflow
|
| /linux-6.15/Documentation/mm/ |
| D | multigen_lru.rst | 80 Workflow overview
|
| D | page_tables.rst | 271 The actual implementation of the workflow is very complex. Its design allows
|
| /linux-6.15/fs/btrfs/ |
| D | qgroup.h | 72 * So for balance, we use a delayed subtree tracing, whose workflow is:
|
| /linux-6.15/arch/arm/boot/dts/marvell/ |
| D | armada-370.dtsi | 272 * the standard workflow for CPU idle support (relying
|
| /linux-6.15/drivers/w1/ |
| D | w1_io.c | 409 * When the workflow with a slave amongst many requires several
|
| /linux-6.15/net/openvswitch/ |
| D | vport.c | 231 * workflow. in ovs_vport_add()
|
| /linux-6.15/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
|
| /linux-6.15/kernel/cgroup/ |
| D | rstat.c | 254 * cgroup_rstat_flush(), this enables a complete workflow where bpf progs that
|
12