Searched refs:something (Results 1 – 25 of 366) sorted by relevance
12345678910>>...15
| /Linux-v4.19/drivers/scsi/dpt/ |
| D | sys_info.h | 285 uCHAR something; member
319 uCHAR something; member
353 uCHAR something; member
387 uCHAR something; member
|
| /Linux-v4.19/Documentation/devicetree/bindings/i2c/ |
| D | i2c-gpio.txt | 21 - i2c-gpio,sda-open-drain: this means that something outside of our
23 that something is not the GPIO chip. It is essentially an
25 - i2c-gpio,scl-open-drain: this means that something outside of our
27 that something is not the GPIO chip. It is essentially an
|
| /Linux-v4.19/Documentation/x86/ |
| D | protection-keys.txt | 51 *ptr = foo; // assign something
70 something(ptr);
76 something(ptr);
78 That should be true whether something() is a direct access to 'ptr'
|
| /Linux-v4.19/scripts/kconfig/tests/preprocess/variable/ |
| D | Kconfig | 18 # Append something to a simply expanded variable.
24 # Append something to a recursively expanded variable.
|
| /Linux-v4.19/Documentation/networking/ |
| D | cops.txt | 37 Or in lilo.conf put something like this:
40 Then bring up the interface with ifconfig. It will look something like this:
48 You will need to configure atalkd with something like the following to make
|
| D | tc-actions-env-rules.txt | 23 Post on netdev if something is unclear.
|
| /Linux-v4.19/tools/perf/Documentation/ |
| D | callchain-overhead-calculation.txt | 25 /* do something */
29 /* do something */
44 recorded with callchains the output will show something like below
|
| /Linux-v4.19/Documentation/media/kapi/ |
| D | dtv-common.rst | 39 /* do something */
46 /* do something */
|
| /Linux-v4.19/Documentation/usb/ |
| D | dwc3.txt | 4 Please pick something while reading :)
35 handed something to thread so we don't process event X prio Y
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | automount-support.txt | 14 Then from userspace, you can just do something like:
24 And then if you look in the mountpoint catalogue, you'll see something like:
82 If the mountpoint in question is in referenced by something other than
|
| /Linux-v4.19/Documentation/devicetree/bindings/net/ieee802154/ |
| D | mrf24j40.txt | 7 - spi-max-frequency: maximal bus speed, should be set something under or equal
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-class-fpga-manager | 12 The intent is to provide enough detail that if something goes
13 wrong during FPGA programming (something that the driver can't
|
| /Linux-v4.19/Documentation/ABI/stable/ |
| D | sysfs-class-rfkill | 62 transmitter is forced off by something outside of
75 The transmitter is forced off by something outside of
|
| /Linux-v4.19/Documentation/ |
| D | cpu-load.txt | 42 |_ something begins working |
43 |_ something goes to sleep
|
| /Linux-v4.19/drivers/parport/ |
| D | TODO-parport | 13 bits when they have something to say. We should read out and deal
|
| /Linux-v4.19/Documentation/devicetree/bindings/spi/ |
| D | jcore,spi.txt | 17 Necessary only if the input clock rate is something other than a
|
| /Linux-v4.19/Documentation/driver-model/ |
| D | design-patterns.txt | 102 The design pattern is the same for an hrtimer or something similar that will
110 standard C, which allows something similar to object oriented behaviours.
|
| /Linux-v4.19/Documentation/device-mapper/ |
| D | log-writes.txt | 77 we're fsck'ing something reasonable, you would do something like
99 Say you want to test fsync on your file system. You would do something like
|
| /Linux-v4.19/Documentation/i2c/busses/ |
| D | i2c-ismt | 33 something similar to the following:
|
| D | i2c-amd8111 | 16 If you see something like this:
|
| /Linux-v4.19/Documentation/power/ |
| D | tricks.txt | 12 * use ext2. At least it has working fsck. [If something seems to go
|
| /Linux-v4.19/Documentation/i2c/ |
| D | i2c-protocol | 68 generates something like:
75 system memory into something that appears as a single transfer to the
|
| /Linux-v4.19/Documentation/core-api/ |
| D | circular-buffers.rst | 154 The producer will look something like this::
182 Note that wake_up() does not guarantee any sort of barrier unless something
195 The consumer will look something like this::
228 fact that we are writing to something that can be read concurrently,
|
| /Linux-v4.19/Documentation/sh/ |
| D | new-machine.txt | 113 might look something like:
138 * do something useful.
183 __IO_PREFIX to something sensible. A typical example would be:
192 this must be defined as something like:
261 Looking at the 'make help' output, you should now see something like:
|
| /Linux-v4.19/arch/m68k/q40/ |
| D | README | 19 When something blocks interrupts (HD) it will lose some of them, so far
22 poll the floppy for this reason - something that can't be done in Linux.
54 preceded by the booter signature. This is a trace just in case something
|
12345678910>>...15
