Searched full:let (Results 1 – 25 of 208) sorted by relevance
123456789
| /Documentation/trace/ |
| D | function-graph-fold.vim | 15 let line = getline(a:lnum)
29 let s = split(getline(v:foldstart), '|', 1)
31 let s[2] = ' task switch '
33 let e = split(getline(v:foldend), '|', 1)
34 let s[2] = e[2]
|
| D | events-nmi.rst | 22 Let's say you suspect that perf_event_nmi_handler() is causing
29 Let's also say you are only interested in when that function is
|
| /Documentation/filesystems/ |
| D | sharedsubtree.rst | 47 Let's say /mnt has a mount that is shared::
70 Now let's say we mount a device at /tmp/a::
93 Let's say /mnt has a mount which is shared.
96 Let's bind mount /mnt to /tmp
102 Now let's make the mount at /tmp; a slave of /mnt
105 let's mount /dev/sd0 on /mnt/a
116 However let's see what happens if we mount something on the mount at /tmp
136 let's say we have a mount at /mnt and we make it unbindable::
140 Let's try to bind mount this mount somewhere else::
446 let's say we have the following mount tree::
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | cec.txt | 6 is high. Some boards only let the CEC pin through if the HPD is high,
|
| /Documentation/spi/ |
| D | butterfly.rst | 20 SPI protocol drivers interact with the AVR, and could even let the AVR
42 Then to let Linux master that bus to talk to the DataFlash chip, you must
60 That would let you talk to the AVR using custom SPI-with-USI firmware,
|
| /Documentation/i2c/ |
| D | old-module-parameters.rst | 11 <linux/i2c.h> which created standard module parameters to let the user
13 parameters were known as ``probe`` (to let the driver probe for an extra
|
| /Documentation/process/ |
| D | management-style.rst | 75 It turns out that since nobody would be stupid enough to ever really let
164 And the more convinced you are that you are right (and let's face it,
188 knowledge that we're better than the average person (let's face it,
209 specific directions, but let's face it, they might be good at what they
232 importantly, they're also likely the person who can fix it. Because, let's
284 boys, let's not be judgmental or sexist here) knocking on your dressing
|
| D | applying-patches.rst | 153 Let's look a bit more at some of the messages patch can produce.
219 This will let you move from something like 5.7.2 to 5.7.3 in a single
220 step. The -z flag to interdiff will even let you feed it patches in gzip or
368 # now let's move from 5.8-rc3 to 5.8-rc5
376 # finally let's try and move from 5.7.3 to 5.8-rc5
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | brcm,bcm4708-pinmux.txt | 5 functions. They can be referenced later by other bindings to let system
|
| /Documentation/devicetree/bindings/power/ |
| D | pd-samsung.yaml | 39 to let user to distinguish between multiple domains in SoC.
|
| /Documentation/admin-guide/laptops/ |
| D | toshiba_haps.rst | 27 however, this driver only provides a notification via a sysfs file to let
76 provides a way to let userspace query the current protection
|
| /Documentation/devicetree/bindings/ |
| D | ABI.rst | 23 1) Maintainers, don't let perfect be the enemy of good. Don't hold up a
|
| /Documentation/driver-api/nfc/ |
| D | nfc-hci.rst | 27 let the HCI driver handle proprietary events or override standard behavior.
104 - complete_target_discovered() is an optional entry point to let the driver
119 can handle the event or return 1 to let HCI attempt standard processing.
309 space to let it know that the poll operation will never be able to detect a
|
| /Documentation/driver-api/iio/ |
| D | triggered-buffers.rst | 5 Now that we know what buffers and triggers are let's see how they work together.
|
| D | triggers.rst | 45 Let's see a simple example of how to setup a trigger to be used by a driver::
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 25 # have. Let's assume we have some CORE functionality, then the kernel has a
|
| /Documentation/xtensa/ |
| D | atomctl.rst | 21 Memory controller we let it to the atomic operations internally while
|
| /Documentation/driver-api/gpio/ |
| D | using-gpio.rst | 7 and preferred way to use GPIO lines is to let kernel hardware drivers deal
|
| /Documentation/sphinx/ |
| D | load_config.py | 24 # Let's avoid one conf.py file just due to latex_documents
|
| /Documentation/arm/ |
| D | vlocks.rst | 46 /* let's suggest ourself */
103 /* we won the town election, let's go for the state */
|
| /Documentation/input/devices/ |
| D | pxrc.rst | 7 This driver let you use your own RC controller plugged into the
|
| /Documentation/iio/ |
| D | ep93xx_adc.rst | 17 not defined. So the last three are numbered randomly, let's say.
|
| /Documentation/networking/ |
| D | driver.rst | 74 mitigation scheme to let TX packets "hang out" in the TX
|
| /Documentation/staging/ |
| D | remoteproc.rst | 90 /* let's power on and boot our remote processor */
102 /* let's shut it down now */
225 processor and let it know it has pending messages. Notifying remote processors
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-nfit | 211 support exposes an option let the platform force idle devices in
213 do it. The safe default is to let the platform force idle
|
123456789