Home
last modified time | relevance | path

Searched refs:thing (Results 1 – 25 of 175) sorted by relevance

1234567

/Linux-v5.4/Documentation/scsi/
Dsmartpqi.txt62 The above three ioctls all do exactly the same thing, which is to cause the driver
63 to rescan for new devices. This does exactly the same thing as writing to the
Dhpsa.txt111 The above three ioctls all do exactly the same thing, which is to cause the driver
112 to rescan for new devices. This does exactly the same thing as writing to the
/Linux-v5.4/Documentation/media/uapi/dvb/
Dquery-dvb-frontend-info.rst16 Usually, the first thing to do when the frontend is opened is to check
Dfrontend_f_open.rst60 thing to do after a successful open is to find out the frontend type
/Linux-v5.4/arch/arc/plat-eznps/
Dentry.S38 ; First thing we invalidate D$
/Linux-v5.4/Documentation/ABI/obsolete/
Dsysfs-bus-usb31 same thing.
/Linux-v5.4/Documentation/process/
Dmanagement-style.rst79 thing you can backtrack on is a technical decision, and there
103 might be the wrong thing. You should always reserve the right to change
106 stupid thing.
120 thing you can do as a manager is not to instill confidence, but rather a
207 One thing to look out for is to realize that greatness in one area does
245 There's one thing people hate even more than being called "d*ckhead",
Dstable-kernel-rules.rst11 - It must fix only one thing.
13 problem..." type thing).
/Linux-v5.4/Documentation/sound/designs/
Dpowersave.rst43 Try to turn it off when you experience such a thing too often.
/Linux-v5.4/Documentation/driver-api/
Disa.rst54 them in at all. The id is the only thing we ever want other then the
94 The first thing this does is check if this device is in fact one of this
/Linux-v5.4/Documentation/driver-api/usb/
Dpersist.rst30 "officially correct" thing to do.
83 same thing that happens whenever a USB device is reset.) If the
90 The same thing happens if the host controller is in the expected state
/Linux-v5.4/Documentation/usb/
Dgadget_multi.rst59 The only thing to worry is that the gadget has to have a single
66 The other, trickier thing is making Windows install drivers for each
/Linux-v5.4/Documentation/sh/
Dnew-machine.txt15 The first thing to note is the new directory structure. Under 2.4, most
88 The first thing to determine is whether the board you are adding will be
204 The first thing to do is to add an entry to arch/sh/Kconfig, under the
/Linux-v5.4/Documentation/filesystems/
Dbfs.txt47 Just in case, you can verify that you have done the right thing by checking
/Linux-v5.4/drivers/hwmon/
Df75375s.c644 #define show_fan(thing) \ argument
645 static ssize_t show_##thing(struct device *dev, struct device_attribute *attr, \
650 return sprintf(buf, "%d\n", rpm_from_reg(data->thing[nr])); \
/Linux-v5.4/Documentation/core-api/
Didr.rst13 small numbers which identify a thing. Examples include file descriptors,
Dcircular-buffers.rst146 consumer that empties it. Only one thing should be filling a buffer at any one
147 time, and only one thing should be emptying a buffer at any one time, but the
/Linux-v5.4/Documentation/
Dbus-virt-phys-mapping.txt57 Now, that looks simple enough. However, when you look at the same thing from
71 where all the addresses actually point to the same thing. It's just seen
/Linux-v5.4/drivers/staging/vc04_services/interface/vchi/
DTODO90 The first thing one generally sees in a probe function is a memory allocation
/Linux-v5.4/net/bluetooth/
DKconfig105 cases are run first thing at module load time. When the Bluetooth
/Linux-v5.4/arch/powerpc/boot/dts/
Dacadia.dts175 /* This thing is a bit weird. It has it's own UIC
Dep405.dts218 /* That's all I know about IRQs on that thing ... */
/Linux-v5.4/Documentation/vm/
Dmmu_notifier.rst11 thing like ATS/PASID to get the IOMMU to walk the CPU page table to access a
/Linux-v5.4/Documentation/power/
Ds2ram.rst22 debugging - the thing that Chuck tried to disable. That's often the _only_
/Linux-v5.4/Documentation/powerpc/
Ddscr.rst52 the same thing as above but unlike the global one above, it just changes

1234567