Home
last modified time | relevance | path

Searched full:trivial (Results 1 – 25 of 78) sorted by relevance

1234

/Documentation/devicetree/bindings/rtc/
Dtrivial-rtc.yaml4 $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml#
7 title: Trivial RTCs
13 This is a list of trivial RTC devices that have simple device tree
Disil,isl12057.txt3 ISL12057 is a trivial I2C device (it has simple device tree bindings,
/Documentation/devicetree/bindings/
Dtrivial-devices.yaml4 $id: http://devicetree.org/schemas/trivial-devices.yaml#
7 title: Trivial I2C and SPI devices
13 This is a list of trivial I2C and SPI devices that have simple device tree
90 # DH electronics GmbH on-board CPLD trivial SPI device
220 # Menlo on-board CPLD trivial SPI device
Dwriting-schema.rst190 make dt_binding_check DT_SCHEMA_FILES=trivial-devices.yaml
191 make dt_binding_check DT_SCHEMA_FILES=trivial-devices.yaml:rtc.yaml
193 make dtbs_check DT_SCHEMA_FILES=trivial-devices.yaml
/Documentation/mm/
Dremap_file_pages.rst12 Supporting of nonlinear mapping requires significant amount of non-trivial
/Documentation/devicetree/bindings/net/wireless/
Dbrcm,bcm4329-fmac.yaml89 brcm,ccode-map-trivial:
91 Use a trivial mapping of ISO3166 country codes to brcmfmac firmware
/Documentation/filesystems/iomap/
Dporting.rst56 In most cases, this is a relatively trivial conversion of the existing
58 ``FS_IOC_FIEMAP`` is a good first target because it is trivial to
/Documentation/kbuild/
DKconfig.recursion-issue-0140 # so trivial to resolve, we provide another example below of practical
/Documentation/core-api/
Dprintk-index.rst19 Finding these changes in the sources would require non-trivial parsers.
21 is not always trivial. Various changes might be backported. Various kernel
Dgfp_mask-from-fs-io.rst59 GFP_KERNEL allocations deep inside the allocator which are quite non-trivial
Ddma-attributes.rst33 such mapping is non-trivial task and consumes very limited resources
/Documentation/core-api/irq/
Dirqflags-tracing.rst19 Architecture support for this is certainly not in the "trivial"
/Documentation/maintainer/
Dfeature-and-driver-maintainers.rst55 no matter how trivial. If the patch is a tree wide change and modifies
121 for any piece of code, no matter how trivial. It spreads the burden, helps
/Documentation/driver-api/media/drivers/ccs/
Dccs.rst75 PLL calculator isn't entirely trivial. Yet it is relatively simple to use for a
/Documentation/networking/
Dmsg_zerocopy.rst36 trivial as just passing the flag, then.
79 The change to send (or sendto, sendmsg, sendmmsg) itself is trivial.
Dtproxy.rst51 A trivial patch for netcat is available here:
/Documentation/admin-guide/cgroup-v1/
Dpids.rst11 Since it is trivial to hit the task limit without hitting any kmemcg limits in
/Documentation/admin-guide/
Dsyscall-user-dispatch.rst87 should not be seen as a security mechanism, since it is trivial for a
/Documentation/filesystems/
Dinotify.rst42 cleanly--and we can, the idr layer makes stuff like this trivial--then we
/Documentation/process/
Dsubmit-checklist.rst65 1) Check for trivial violations with the patch style checker prior to
Dmaintainer-kvm-x86.rst99 is a multi-arch series, i.e. has non-trivial modifications to common KVM code
303 In general, regression tests are preferred for any bug that is not trivial to
308 Note, KVM bugs are rarely urgent *and* non-trivial to reproduce. Ask yourself
/Documentation/dev-tools/kunit/api/
Dfunctionredirection.rst18 "pure functions") this is trivial, for others (like device drivers,
/Documentation/arch/x86/i386/
DIO-APIC.rst45 is non-trivial though and cannot be automated. One sample /etc/lilo.conf
/Documentation/locking/
Dpi-futex.rst67 [this is a quite common scenario for most non-trivial RT applications],
/Documentation/security/
Dself-protection.rst43 When all of kernel memory is writable, it becomes trivial for attacks
107 One trivial way to eliminate many syscalls for 64-bit systems is building

1234