Searched refs:something (Results 1 – 25 of 411) sorted by relevance
12345678910>>...17
64 *ptr = foo; // assign something81 something(ptr);87 something(ptr);89 无论something()是否是对'ptr'的直接访问，这都应该为真。
55 description: this means that something outside of our control has put56 the GPIO line used for SDA into open drain mode, and that something is62 description: this means that something outside of our control has put the63 GPIO line used for SCL into open drain mode, and that something is not
58 *ptr = foo; // assign something78 something(ptr);84 something(ptr);86 That should be true whether something() is a direct access to 'ptr'
18 # Append something to a simply expanded variable.24 # Append something to a recursively expanded variable.
25 /* do something */29 /* do something */44 recorded with callchains the output will show something like below
46 Or in lilo.conf put something like this::50 Then bring up the interface with ifconfig. It will look something like this::61 You will need to configure atalkd with something like the following to make
41 /* do something */48 /* do something */
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;
9 Please pick something while reading :)42 handed something to thread so we don't process event X prio Y
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
7 - spi-max-frequency: maximal bus speed, should be set something under or equal
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;
12 The intent is to provide enough detail that if something goes13 wrong during FPGA programming (something that the driver can't
16 If your ``lspci -v`` listing shows something like the following::
21 If you see something like this::
10 select a legacy board option (something other than CONFIG_SH_DEVICE_TREE)
42 |_ something begins working |43 |_ something goes to sleep
64 transmitter is forced off by something outside of78 The transmitter is forced off by something outside of
107 files (typically something that a netfs would get for a superblock); and108 data file cookies are used to cache data (something that would be got for229 This will look something like::260 This will look something like::288 This will look something like::
13 bits when they have something to say. We should read out and deal
487 [user@something ~]$ lspci -k499 … [user@something ~]$ realpath --relative-to=/sys/module//sys/class/net/wlp58s0/device/driver/module764 [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh ./linux-5.10.5/vmlinux770 [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh \
17 Necessary only if the input clock rate is something other than a
72 generates something like::82 system memory into something that appears as a single transfer to the
102 The design pattern is the same for an hrtimer or something similar that will110 standard C, which allows something similar to object oriented behaviours.
82 we're fsck'ing something reasonable, you would do something like104 Say you want to test fsync on your file system. You would do something like