| /linux/Documentation/translations/zh_CN/core-api/ |
| H A D | protection-keys.rst | 64 *ptr = foo; // assign something
81 something(ptr);
87 something(ptr);
89 无论something()是否是对'ptr'的直接访问，这都应该为真。
|
| /linux/Documentation/process/ |
| H A D | deprecated.rst | 185 If you are debugging something where "%p" hashing is causing problems,
248 struct something {
259 struct something {
272 struct something {
288 struct something {
293 struct something *instance;
319 struct something {
324 struct something *instance;
338 struct something {
343 struct something *instance;
[all …]
|
| /linux/scripts/kconfig/tests/preprocess/variable/ |
| H A D | Kconfig | 18 # Append something to a simply expanded variable.
24 # Append something to a recursively expanded variable.
|
| /linux/Documentation/core-api/ |
| H A D | protection-keys.rst | 76 *ptr = foo; // assign something
96 something(ptr);
102 something(ptr);
104 That should be true whether something() is a direct access to 'ptr'
|
| H A 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/Documentation/driver-api/media/ |
| H A D | dtv-common.rst | 32 /* do something */
39 /* do something */
|
| /linux/Documentation/translations/it_IT/process/ |
| H A D | deprecated.rst | 276 struct something {
288 struct something {
303 struct something {
320 struct something {
325 struct something *instance;
355 struct something {
360 struct something *instance;
374 struct something {
379 struct something *instance;
393 struct something {
[all …]
|
| /linux/tools/perf/Documentation/ |
| H A D | callchain-overhead-calculation.txt | 26 /* do something */
30 /* do something */
45 recorded with callchains the output will show something like below
|
| /linux/Documentation/filesystems/ |
| H A D | automount-support.rst | 20 Then from userspace, you can just do something like::
30 And then if you look in the mountpoint catalogue, you'll see something like::
87 If the mountpoint in question is in referenced by something other than
|
| /linux/Documentation/usb/ |
| H A D | dwc3.rst | 9 Please pick something while reading :)
42 handed something to thread so we don't process event X prio Y
|
| /linux/Documentation/translations/sp_SP/process/ |
| H A D | deprecated.rst | 269 struct something {
277 struct something {
289 struct something {
303 struct something {
318 struct something {
323 struct something *instance;
351 struct something {
356 struct something *instance;
371 struct something {
376 struct something *instance;
|
| /linux/Documentation/ABI/testing/ |
| H A 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/Documentation/filesystems/caching/ |
| H A D | fscache.rst | 107 files (typically something that a netfs would get for a superblock); and
108 data file cookies are used to cache data (something that would be got for
229 This will look something like::
260 This will look something like::
288 This will look something like::
|
| /linux/Documentation/admin-guide/ |
| H A D | cpu-load.rst | 42 |_ something begins working |
43 |_ something goes to sleep
|
| H A D | reporting-issues.rst | 65 something else. These steps thus help to ensure the time you invest in this
102 (say something broke when updating from 5.10.4 to 5.10.5), scroll down to
135 that hear about it for the first time. And if you learned something in this
173 face one of those if something breaks when updating from 5.10.4 to 5.10.5 (a
401 An issue is a 'really severe problem' when something totally unacceptably bad
436 * When dealing with a regression, make sure it's not something else that
441 something in the BIOS Setup can also lead to problems that on look a lot
485 The kernel marks itself with a 'taint' flag when something happens that might
578 (say something broke when updating from 5.10.4 to 5.10.5), scroll down to
581 Regression within a stable and longterm kernel version line are something the
[all …]
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-class-rfkill | 64 transmitter is forced off by something outside of
78 The transmitter is forced off by something outside of
|
| /linux/Documentation/driver-api/ |
| H A D | generic_pt.rst | 23 per-format compilation unit. For something like IOMMU each format will be
79 is usually a good reference for something simple, and AMDv1 is something fairly
|
| /linux/Documentation/devicetree/bindings/net/ieee802154/ |
| H A D | mrf24j40.txt | 7 - spi-max-frequency: maximal bus speed, should be set something under or equal
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | log-writes.rst | 82 we're fsck'ing something reasonable, you would do something like
104 Say you want to test fsync on your file system. You would do something like
|
| /linux/Documentation/i2c/busses/ |
| H A D | i2c-nvidia-gpu.rst | 16 If your ``lspci -v`` listing shows something like the following::
|
| /linux/Documentation/i2c/ |
| H A D | i2c-protocol.rst | 72 generates something like::
82 system memory into something that appears as a single transfer to the
|
| /linux/Documentation/driver-api/driver-model/ |
| H A D | design-patterns.rst | 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/Documentation/translations/zh_CN/admin-guide/ |
| H A D | reporting-issues.rst | 480 [user@something ~]$ lspci -k
492 … [user@something ~]$ realpath --relative-to=/sys/module//sys/class/net/wlp58s0/device/driver/module
758 [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh ./linux-5.10.5/vmlinux
764 [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh \
|
| /linux/Documentation/translations/zh_TW/admin-guide/ |
| H A D | reporting-issues.rst | 481 [user@something ~]$ lspci -k
493 … [user@something ~]$ realpath --relative-to=/sys/module//sys/class/net/wlp58s0/device/driver/module
759 [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh ./linux-5.10.5/vmlinux
765 [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh \
|
| /linux/Documentation/arch/sh/ |
| H A D | booting.rst | 10 select a legacy board option (something other than CONFIG_SH_DEVICE_TREE)
|