Skip to content

Instantly share code, notes, and snippets.

@fabiospampinato

fabiospampinato/rg.txt

Last active June 9, 2024 15:40
Show Gist options
  • Save fabiospampinato/feb3c06c21fdda4e66ce39632226d999 to your computer and use it in GitHub Desktop.
Save fabiospampinato/feb3c06c21fdda4e66ce39632226d999 to your computer and use it in GitHub Desktop.
Download ZIP
output for "rg something linux-master --sort path"
Raw
rg.txt
~/Downloads ❯ time (rg something linux-master --sort path)
linux-master/Documentation/ABI/stable/sysfs-class-infiniband
214: unless set to something else by the driver. Users may echo a
linux-master/Documentation/ABI/stable/sysfs-class-rfkill
64: transmitter is forced off by something outside of
78: The transmitter is forced off by something outside of
linux-master/Documentation/ABI/stable/vdso
14:if you set CS on x86 to something strange, the vDSO functions are
linux-master/Documentation/ABI/testing/sysfs-bus-intel_th-devices-msc
45: other operating mode or attempts to write something other than "1".
linux-master/Documentation/ABI/testing/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-master/Documentation/ABI/testing/sysfs-class-rc
24: something like::
81: for the wakeup filter, something like::
linux-master/Documentation/ABI/testing/sysfs-devices-waiting_for_supplier
7: and is set to something stricter than "permissive". It is
linux-master/Documentation/Kconfig
10: warning when something is missing. Works only if the Kernel
linux-master/Documentation/PCI/acpi-info.rst
82:and (2) should not be assigned by the OS to something else.
linux-master/Documentation/PCI/pci.rst
223:it's set to something bogus by the BIOS. pci_clear_master() will
504:on the bus need to be capable of doing it, so this is something which needs
linux-master/Documentation/RCU/Design/Data-Structures/Data-Structures.rst
279:two bits indicates that something is broken. This field is protected by
468:| something, so commences RCU softirq processing. |
linux-master/Documentation/RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.rst
468:zone”, expedited grace periods must do something else during this time.
linux-master/Documentation/RCU/Design/Requirements/Requirements.rst
149: 8 void do_something_dlm(void)
156: 15 do_something();
158: 17 do_something_carefully();
173:The RCU read-side critical section in do_something_dlm() works with
175:do_something() never runs concurrently with recovery(), but with
176:little or no synchronization overhead in do_something_dlm().
186:| do_something_dlm() executing do_something() concurrently with |
306:do_something_gp_buggy() below:
310: 1 bool do_something_gp_buggy(void)
315: 6 do_something(p->a, p->b);
331: 1 bool do_something_gp_buggy_optimized(void)
335: 5 do_something(gp->a, gp->b);
347:do_something_gp() uses rcu_dereference() to fetch from ``gp``:
351: 1 bool do_something_gp(void)
356: 6 do_something(p->a, p->b);
417:that readers will reach line 7 of do_something_gp() before the data
439:| Let's start with what happens to do_something_gp() if it fails to |
500: do_something_gp() and find the newly deleted ``struct foo``.
564:| #. CPU 1: ``do_something_with(q->a);`` |
584:| #. CPU 1: ``do_something_with(q->a); /* Boom!!! */`` |
764: 6 do_something_with_nonzero_x();
1349:places that needed something like synchronize_rcu() simply
1395: 15 do_something_while_waiting();
1558:argue that such workloads should instead use something other than RCU,
1777:wait for something, as opposed to simply returning immediately.
2029: 6 do_something_with(v, user_v);
2041: 6 do_something_with(v, user_v);
2486: 4 do_something();
2503: 4 do_something();
linux-master/Documentation/RCU/NMI-RCU.rst
55:for anyone attempting to do something similar on Alpha or on systems
linux-master/Documentation/RCU/RTFP.txt
103:led to yet another independent invention of something like RCU
233: Oldest use of something vaguely resembling RCU that I have found.
1437: something else always proved superior. Partitioning or RCU. ;-)
linux-master/Documentation/RCU/UP.rst
128: a process-context acquisition of this lock must use something
linux-master/Documentation/RCU/checklist.rst
545: If necessary, you can use something like workqueues to execute
linux-master/Documentation/RCU/listRCU.rst
42: /* Do something with p */
296:The update_lsm_rule() does something very similar, for those who would
linux-master/Documentation/RCU/rcu_dereference.rst
270: do_something_with(r1, r2);
335: do_something_with(r1, r2);
463:For example, suppose someone mistakenly does something like this::
466: do_something_with(p->a);
467: do_something_else_with(p->b);
470:of existence, transforming the code to something like this::
472: do_something_with(q->rcu_protected_pointer->a);
473: do_something_else_with(q->rcu_protected_pointer->b);
487: do_something_with(p->a);
488: do_something_else_with(p->b);
linux-master/Documentation/RCU/stallwarn.rst
299:will include something like the following::
linux-master/Documentation/RCU/whatisRCU.rst
98:So the typical RCU update sequence goes something like the following:
503: need to use locking (or something similar) to keep concurrent
1291: who just went out for a pizza or something. And although
linux-master/Documentation/admin-guide/RAS/main.rst
1087: starts the error generation when something different than 0 is written.
linux-master/Documentation/admin-guide/README.rst
8:kernel, and what to do if something goes wrong.
290: - Keep a backup kernel handy in case something goes wrong. This is
351:If something goes wrong
linux-master/Documentation/admin-guide/bcache.rst
346: maturity, but simply because in writeback mode you'll lose data if something
linux-master/Documentation/admin-guide/blockdev/drbd/drbd-connection-state-overview.dot
65: WFReportParams -> StandAlone [ label="during handshake\lpeers do not agree\labout something essential" ]
linux-master/Documentation/admin-guide/blockdev/zram.rst
53:and, in general case, something like::
linux-master/Documentation/admin-guide/cgroup-v1/cgroups.rst
186: subsystem state is something that's expected to happen frequently
315:the "cpuset" cgroup subsystem, the steps are something like::
413:Now you want to do something with this cgroup:
linux-master/Documentation/admin-guide/cgroup-v1/cpusets.rst
757:Now you want to do something with this cpuset::
linux-master/Documentation/admin-guide/cifs/usage.rst
851:installed and something like the following lines should be added to the
linux-master/Documentation/admin-guide/cpu-load.rst
42: |_ something begins working |
43: |_ something goes to sleep
linux-master/Documentation/admin-guide/device-mapper/cache.rst
72:something of a compromise. For instance, a small part of a block may be
linux-master/Documentation/admin-guide/device-mapper/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-master/Documentation/admin-guide/device-mapper/persistent-data.rst
78:There are plans to add more. For example, something with an
linux-master/Documentation/admin-guide/device-mapper/verity.rst
185:The tree looks something like:
linux-master/Documentation/admin-guide/kernel-parameters.txt
56: has something to do with the repair mechanism.
2541: useful for debugging when something happens in the window
3680: something different and driver-specific.
linux-master/Documentation/admin-guide/laptops/laptop-mode.rst
212: memory stick or something like that as a "working area". (Be aware though
linux-master/Documentation/admin-guide/laptops/thinkpad-acpi.rst
394:this section, as it is either something else (e.g. another input device
593:signal that something is wrong, they should never happen on normal
598:cycle, or a system shutdown. Obviously, something is very wrong if this
609:automatically for the cases were userspace has to do something to
linux-master/Documentation/admin-guide/ldm.rst
69:When Linux boots, you will see something like::
linux-master/Documentation/admin-guide/media/bttv.rst
247:might be something else ...
linux-master/Documentation/admin-guide/media/cec.rst
265: then something (hardware and/or software) is preventing the CEC
linux-master/Documentation/admin-guide/media/faq.rst
16: you'll be able to get something useful there. It is hosted
linux-master/Documentation/admin-guide/media/philips.rst
83: something more than 4 is an absolute waste. This memory is only
197: If you want to trace something, look up the bit value(s) in the table
linux-master/Documentation/admin-guide/media/remote-controller.rst
72:the keycodes to something that your favorite media application likes.
linux-master/Documentation/admin-guide/media/vivid.rst
1239:This driver also supports larger 'bytesperline' settings, something that
linux-master/Documentation/admin-guide/mm/pagemap.rst
176:Using pagemap to do something useful
linux-master/Documentation/admin-guide/mm/userfaultfd.rst
10:memory page faults, something otherwise only the kernel code could do.
linux-master/Documentation/admin-guide/module-signing.rst
100: Setting this option to something other than its default of
linux-master/Documentation/admin-guide/parport.rst
77:kernel boot parameters to get the same effect. Add something like the
linux-master/Documentation/admin-guide/quickly-build-trimmed-linux.rst
79: quickly look something up in the reference section and afterwards jump back
86: to be prepared for the unlikely case of something going sideways.
191: Running ``uname -r`` under your kernel later will then print something like
225: be the reason why something you only use occasionally stopped working.
377:for something going sideways, even if that should not happen.
501:something like ``O=~/linux-builddir/`` to all make calls; also adjust the path
633:not something to worry about; but in case you really need the latest code, just
749:something important you can turn on a missing feature later and quickly run the
864:(ncurses, Qt5, Gtk2); an error message will tell you if something required is
905:This most of the time will find something that will explain what is wrong; quite
1041:Now remove the belonging initramfs, which often will be called something like
linux-master/Documentation/admin-guide/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
586:regressions with newer kernel version line (say something broke when switching
617:code it builds upon, but unless you suspect something like that stick to the
618:driver. If it's really something else, the driver's developers will get the
628: [user@something ~]$ lspci -k
639:interface, which might be something like 'wlp58s0'. This name can be used like
642: [user@something ~]$ realpath --relative-to=/sys/module/ /sys/class/net/wlp58s0/device/driver/module
654:MAINTAINERS file, as then you might find something like this::
754:regular internet search engine and add something like
829:to that if you're dealing with something that shouldn't wait. In that case
917:something happens that can lead to follow-up errors that look totally
947: that hear about it for the first time. And if you learned something in this
978: [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh ./linux-5.10.5/vmlinux
985: [user@something ~]$ sudo dmesg | ./linux-5.10.5/scripts/decode_stacktrace.sh \
1025:get something quickly fixed. But for that to happen the change that's causing
1045:introduced the regression. If something for example breaks when switching from
1058:the kernel and not by something else, as outlined above already.
1145: report. Ideally use something where the files stay available for years, as
1196:Don't worry too much about forgetting something, as developers will ask for
1206:something like 'The detailed description:' before the part you just wrote and
1315: * Someone tells you to send something privately.
1317: * You were told to send something, but noticed it contains sensitive
1323:process someone might tell you to do something that requires a skill you might
1344:should wait a week at maximum (or just two days if it's something urgent)
1364:idea, but only report your results if something relevant changed or if you are
1365:writing something anyway.
1386:**Inquiries for data**: Often you will be asked to test something or provide
1409:your report arrived or had something more important to take care of. When
1457:together that mentions how many you are and why this is something that in your
1519:a recheck. Say something broke when you updated from 5.10.4-vendor.42 to
1546:try to find that version using vanilla kernels. Lets assume something broke when
1701:Maybe their test hardware broke, got replaced by something more fancy, or is so
1702:old that it's something you don't find much outside of computer museums
1704:something different in their life became way more important. In some cases
1715:much time and energy in maintaining a Linux kernel driver for something they
linux-master/Documentation/admin-guide/reporting-regressions.rst
19:#. It's a regression if something running fine with one Linux kernel works worse
180:something might break. This is in the interest of the kernel developers to make
linux-master/Documentation/admin-guide/rtc.rst
6:something that tracks wall clock time and is battery backed so that it
linux-master/Documentation/admin-guide/serial-console.rst
125: Programs that want to do something with the virtual console usually
linux-master/Documentation/admin-guide/spkguide.txt
368:If you issue the above ls command, you will get back something like
444:might look something like this:
482:regardless of which shell you use, you should be able to do something
linux-master/Documentation/admin-guide/svga.rst
79:you wish to set and press <RETURN>. If the computer complains something about
linux-master/Documentation/admin-guide/sysctl/index.rst
14:don't know they need to tweak something, or because they don't
linux-master/Documentation/admin-guide/sysctl/vm.rst
541:security module. Setting this value to something like 64k will allow the
linux-master/Documentation/admin-guide/sysrq.rst
227:keyboard, and hitting an invalid sysrq sequence again. (i.e., something like
linux-master/Documentation/admin-guide/tainted-kernels.rst
4:The kernel will mark itself as 'tainted' when something occurs that might be
57:and execute it with ``sh kernel-chktaint``, which would print something like
74:script, but if you need something quick you can use this shell command to check
134: scsi/snic on something else than x86_64, scsi/ips on non
linux-master/Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
22: read and navigate this document -- especially when you want to look something
286: to be prepared for the unlikely case of something going sideways.
318: * Do you face a regression, e.g. something broke or works worse after
428: of your currently working kernel. If the line instead continues with something
466: something to keep in mind: if something is misbehaving with the kernels built
829: will print something like 'Bisecting: 675 revisions left to test after this
835: when Git after tagging a change as 'good' or 'bad' prints something like
938: 'good') might become handy to verify something later -- thus better keep them
973: days: it's pretty likely that you will be asked to recheck something.
1104:for something going sideways, even if that should not happen.
1448:something important you can turn on a missing feature manually later and quickly
1563:respectively Qt5 or Qt6); an error message will tell you if something required
1608: older kernel. That security feature might get into the way of something you
1628: * Regressions also happening in mainline are something the regular Linux
1690:This most of the time will find something that will explain what is wrong; quite
1801:Linux marks itself as tainted when something happens that potentially leads to
1862:appealing, but is usually a bad idea, as it does something important:
1867:starting to suspect something might be wrong with the build configuration.
1895:* Check the taint status and the output of ``dmesg``, maybe something unrelated
1898:* Maybe localmodconfig did something odd and disabled the module required to
1903:* Maybe it's not a kernel regression and something that is caused by some fluke,
linux-master/Documentation/arch/arm/interrupts.rst
108:"simple", or your own specific handler if you need to do something special.
linux-master/Documentation/arch/arm/omap/omap_pm.rst
17: latency framework or something else;
linux-master/Documentation/arch/arm/porting.rst
106: out of bounds memory accesses (eg, something writing off the end
linux-master/Documentation/arch/arm/sa1100/assabet.rst
185:However Linux should display something like::
linux-master/Documentation/arch/arm/sunxi/clocks.rst
16: While the system is operational, you would see something like::
linux-master/Documentation/arch/arm64/arm-acpi.rst
84:really just duplicates something that already works. ACPI already does what
linux-master/Documentation/arch/powerpc/dawr-power9.rst
101:Any errors/failures/skips mean something is wrong.
linux-master/Documentation/arch/powerpc/kasan.txt
51: is hopefully something we can revisit once we get KASLR for Book3S.
linux-master/Documentation/arch/sh/booting.rst
10: select a legacy board option (something other than CONFIG_SH_DEVICE_TREE)
linux-master/Documentation/arch/sh/new-machine.rst
117:might look something like::
179: __IO_PREFIX to something sensible. A typical example would be::
188: this must be defined as something like::
257:Looking at the 'make help' output, you should now see something like:
linux-master/Documentation/arch/x86/boot.rst
846: could require a lot of stack space in something that needs to parse it
950:leaves us with 25 very precious bytes. This isn't something that can be fixed
linux-master/Documentation/arch/x86/exception-tables.rst
45:was not swapped in, write protected or something similar. However,
158:The optimizer does a good job and gives us something we can actually
linux-master/Documentation/arch/x86/tdx.rst
91:If the TDX module is initialized successfully, dmesg shows something
linux-master/Documentation/atomic_t.txt
220:Further, while something like:
228:as well. Similarly, something like:
336:which on LL/SC becomes something like:
linux-master/Documentation/bpf/kfuncs.rst
536: * In a typical program you'd do something like store
linux-master/Documentation/bpf/prog_cgroup_sockopt.rst
143: /* do something */
linux-master/Documentation/cdrom/cdrom-standard.rst
364: CDS_DRIVE_NOT_READY /* something is wrong, tray is moving? */
linux-master/Documentation/core-api/asm-annotations.rst
124: So in most cases, developers should write something like in the following
linux-master/Documentation/core-api/assoc_array.rst
247:something that would require memory to be allocated.
linux-master/Documentation/core-api/cachetlb.rst
24:"TLB" is abstracted under Linux as something the cpu uses to cache
linux-master/Documentation/core-api/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-master/Documentation/core-api/dma-api-howto.rst
129:something like __va(). [ EDIT: Update this when we integrate
206:The 24-bit addressing device would do something like this::
213:The standard 64-bit addressing device would do something like this::
248:address you might do something like::
332: something like::
linux-master/Documentation/core-api/dma-api.rst
389:critical that the driver do something, in the case of a block driver
linux-master/Documentation/core-api/errseq.rst
26:Thus we end up with a value that looks something like this:
linux-master/Documentation/core-api/kref.rst
136:do something like::
155:something else or passing it off to something else, there is no reason
linux-master/Documentation/core-api/protection-keys.rst
58: *ptr = foo; // assign something
78: something(ptr);
84: something(ptr);
86:That should be true whether something() is a direct access to 'ptr'
linux-master/Documentation/core-api/rbtree.rst
299:with something like::
linux-master/Documentation/core-api/this_cpu_ops.rst
281:something which could be problematic because this_cpu ops do not
linux-master/Documentation/core-api/watch_queue.rst
272: * ``type`` is the event type to filter for and should be something like
294:A buffer is created with something like the following::
303:The notifications can then be consumed by something like the following::
linux-master/Documentation/core-api/workqueue.rst
742:If something is busy looping on work queueing, it would be dominating
linux-master/Documentation/cpu-freq/cpu-drivers.rst
280: /* Do something with pos */
linux-master/Documentation/crypto/asymmetric-keys.rst
201: Mandatory. This allows the subtype to display something in /proc/keys
linux-master/Documentation/crypto/descore-readme.rst
196:the table size. in fairness though he might be encoding something particular
366: S-box mapping order or something) into the right format for you.
linux-master/Documentation/dev-tools/checkpatch.rst
893: #define MAC do_something;
901: do_something;
1194: } while(something);
linux-master/Documentation/dev-tools/kgdb.rst
573: If you are having problems connecting or something is going seriously
898:generic drm fb helper functions or implement something custom for the
linux-master/Documentation/dev-tools/kunit/run_wrapper.rst
93:.. note:: Removing something from the ``.kunitconfig`` will
linux-master/Documentation/dev-tools/kunit/usage.rst
32:An *expectation* specifies that we expect a piece of code to do something in a
774:Had we wanted something more flexible, we could have used a named ``kunit_resource``.
linux-master/Documentation/dev-tools/sparse.rst
19:"__bitwise" is a type attribute, so you have to do something like this::
linux-master/Documentation/devicetree/bindings/bus/qcom,ebi2.txt
37:this is something just used on the FAST chip selects and that the SLOW
linux-master/Documentation/devicetree/bindings/example-schema.yaml
82: there's something unique to add.
linux-master/Documentation/devicetree/bindings/gpio/gpio.txt
143:typical example is something like this: the hardware register is 32 bits
linux-master/Documentation/devicetree/bindings/i2c/i2c-gpio.yaml
59: description: this means that something outside of our control has put
60: the GPIO line used for SDA into open drain mode, and that something is
66: description: this means that something outside of our control has put the
67: GPIO line used for SCL into open drain mode, and that something is not
linux-master/Documentation/devicetree/bindings/iio/adc/qcom,pm8018-adc.yaml
32: something like 2.2 or 1.8V.
linux-master/Documentation/devicetree/bindings/mfd/rohm,bd71815-pmic.yaml
59: something other but 30MOhm resistor is used the resistance value
linux-master/Documentation/devicetree/bindings/net/ethernet-controller.yaml
62: # something proprietary is being used to embed the PHY in the
linux-master/Documentation/devicetree/bindings/net/ieee802154/mrf24j40.txt
7: - spi-max-frequency: maximal bus speed, should be set something under or equal
linux-master/Documentation/devicetree/bindings/pinctrl/allwinner,sun4i-a10-pinctrl.yaml
102: # than 3, or something that doesn't start with 'p',
linux-master/Documentation/devicetree/bindings/serial/sifive-serial.yaml
27: Should be something similar to "sifive,<chip>-uart"
linux-master/Documentation/devicetree/bindings/spi/jcore,spi.txt
17: Necessary only if the input clock rate is something other than a
linux-master/Documentation/devicetree/usage-model.rst
191:Linux it will look something like this::
387:can look something like this::
linux-master/Documentation/doc-guide/kernel-doc.rst
467:used for something like a theory of operation for a driver or library code, for
linux-master/Documentation/driver-api/clk.rst
282:lock in core, unless you want to do something else with the information of
linux-master/Documentation/driver-api/crypto/iaa/iaa-crypto.rst
489:You should see something like the following in the dmesg output::
585:see something similar to the following in dmesg output if you've
639:You should see something like the following in the dmesg output if
linux-master/Documentation/driver-api/driver-model/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-master/Documentation/driver-api/driver-model/devres.rst
117: if (check something)
185:For example, you can do something like the following::
187: int my_midlayer_create_something()
189: if (!devres_open_group(dev, my_midlayer_create_something, GFP_KERNEL))
194: devres_close_group(dev, my_midlayer_create_something);
198: void my_midlayer_destroy_something()
200: devres_release_group(dev, my_midlayer_create_something);
linux-master/Documentation/driver-api/driver-model/driver.rst
90:need to register with the bus using something like pci_driver_register.
linux-master/Documentation/driver-api/driver-model/overview.rst
98:or something similar in the /lib/init/fstab file on Debian-based systems::
linux-master/Documentation/driver-api/driver-model/porting.rst
236: Just like with devices, do something like::
linux-master/Documentation/driver-api/eisa.rst
32: by the bus code. This can go from something as simple as reserving
linux-master/Documentation/driver-api/firmware/request_firmware.rst
77:If something went wrong request_firmware() returns non-zero and fw_entry
linux-master/Documentation/driver-api/gpio/driver.rst
28:The hardware GPIO number should be something intuitive to the hardware, for
125:Debouncing in practice involves setting up a timer when something happens on
238:the circuit board. This is not something we deal with or model in software. The
319: disabled. The GPIO irqchip will then end up calling something like this
355: The GPIO irqchip will then end up calling something like this sequence in
375: by the driver. The hallmark of this driver is to call something like
linux-master/Documentation/driver-api/gpio/legacy.rst
255:signal, or (b) something wrongly believes it's safe to remove drivers
linux-master/Documentation/driver-api/ipmi.rst
529:system. By default, the driver will only register with something it
626:host drivers, not something on the IPMB bus.
linux-master/Documentation/driver-api/libata.rst
817:indicates something is very wrong with the system. Resetting host
linux-master/Documentation/driver-api/mailbox.rst
67: return; /* Or do something else here */
linux-master/Documentation/driver-api/md/md-cluster.rst
383:There are somethings which are not supported by cluster MD yet.
linux-master/Documentation/driver-api/media/cec-core.rst
271: or LOW_DRIVE if the hardware cannot differentiate or something
284:The hardware must be able to differentiate between OK, NACK and 'something
linux-master/Documentation/driver-api/media/drivers/cx2341x-devel.rst
90: something.
2179: 6=something to do with the quantization matrix
linux-master/Documentation/driver-api/media/drivers/pvrusb2.rst
171: mmap()'ed buffers or something even more exotic.
linux-master/Documentation/driver-api/media/drivers/zoran.rst
461:(quantization) tables, and you'll get to something like 512kB per frame for
512:by one, or something like that.) We can't use 165 bits per block, but have to
linux-master/Documentation/driver-api/media/dtv-common.rst
32: /* do something */
39: /* do something */
linux-master/Documentation/driver-api/media/maintainer-entry-profile.rst
51:probably something went wrong on your submission. Please check if the
163:a few cases, ``checkpatch.pl`` may actually point to something that would
linux-master/Documentation/driver-api/media/tx-rx.rst
105:in software, especially when there is no interrupt telling something is
linux-master/Documentation/driver-api/media/v4l2-controls.rst
23:All the rest is something that can be done centrally.
230:Note that if something fails, the function will return NULL or an error and
345:For all other types use ctrl->p_cur.p<something>. Basically the val
linux-master/Documentation/driver-api/media/v4l2-dev.rst
45:- :c:type:`video_device`->name: set to something descriptive and unique.
linux-master/Documentation/driver-api/media/v4l2-fh.rst
122:Several drivers need to do something when the first file handle is opened and
linux-master/Documentation/driver-api/media/v4l2-subdev.rst
36:``i2c_get_clientdata()``. For other buses something similar needs to be done.
540:Both functions return ``NULL`` if something went wrong.
545:The use of chipid is something that needs to be looked at more closely at a
linux-master/Documentation/driver-api/mtd/nand_ecc.rst
16:or someone learns something from it.
664:into the wrong direction. Maybe something to investigate later. Could
687:in the result byte and then do something like::
757:programmed in C. Of course it might be possible to squeeze something more
linux-master/Documentation/driver-api/nfc/nfc-hci.rst
286:must be reported such that upper layers don't stay ignorant that something
linux-master/Documentation/driver-api/parport-lowlevel.rst
407:the ``irq`` function will be called. (Write something about shared
554:``parport_claim_or_block`` may do. (Put something here about blocking
linux-master/Documentation/driver-api/pin-control.rst
444:On the bottom row at { A1, B1, C1, D1, E1, F1, G1, H1 } we have something
477: In this case the array could be something like: { spi0, i2c0, mmc0 }
579:group of pins would work something like this:
701:and similar functions. There are cases where you may be using something
853:to think that you need to come up with something really complex, that the
927:when going to sleep, it might imply that the pin is set into something the
1140:The result of grabbing this mapping from the device with something like
linux-master/Documentation/driver-api/pm/devices.rst
41: This is something that device, bus, and class drivers collaborate on
417:and :c:func:`pci_enable_wake()` does something similar for the PCI PME signal.
linux-master/Documentation/driver-api/pps.rst
53:OK for the serial and parallel port, where you can do something
linux-master/Documentation/driver-api/surface_aggregator/client.rst
163:such requests, however, most of them boil down to something similar as shown
linux-master/Documentation/driver-api/thermal/cpu-idle-cooling.rst
148:... which is more than the sustainable power (or there is something
linux-master/Documentation/driver-api/thermal/power_allocator.rst
90:`thermal_zone_params` were being passed, then something like below
linux-master/Documentation/driver-api/uio-howto.rst
56:Find something wrong with this document? (Or perhaps something right?) I
293: using something like :c:func:`ioremap()`. Addresses returned by
643: device. Do something to it. */
linux-master/Documentation/driver-api/usb/dwc3.rst
110:something that has been exercised very frequently. If you experience
linux-master/Documentation/driver-api/usb/hotplug.rst
128:something like this::
linux-master/Documentation/driver-api/usb/usb.rst
945:example, use something like ``grep ^T: /sys/kernel/debug/usb/devices``
linux-master/Documentation/driver-api/xillybus.rst
42:them. It's usually pointless to reimplement something that is already
linux-master/Documentation/fault-injection/fault-injection.rst
273:does something. Thus if the function error injection skips whole of the
linux-master/Documentation/fb/cirrusfb.rst
8:.. just a little something to get people going; contributors welcome!
linux-master/Documentation/fb/cmap_xfbdev.rst
24:- X11 apps do something like the following when trying to use grayscale::
linux-master/Documentation/fb/sstfb.rst
16:in progress, I feel uncomfortable with releasing tarballs of something
linux-master/Documentation/fb/vesafb.rst
78:"bad mode number" message if something goes wrong.
linux-master/Documentation/filesystems/autofs.rst
146: something on the second it must be able to "walk" down past the
281:mounts. If it finds something in the root directory to expire it will
352:so messages can indicate that a name is missing (something tried to
411: is required. This is filled in with the name of something
linux-master/Documentation/filesystems/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-master/Documentation/filesystems/bcachefs/CodingStyle.rst
48:should you need to debug something that caused the assertion to fail, you can
51:A good assertion checks something that the compiler could check for us, and
53:the compiler could check. This is something that exists today, but it'll likely
95:something, and if it's intermittent it may not even be possible.
136:productive in the long run if you notice this early and shift to something
160:often go astray - doing something because it seems like it'll be useful often
164:afraid to throw things away and do something simpler.
linux-master/Documentation/filesystems/befs.rst
81:filesystem (experimental)", or something like that. Enable that option
linux-master/Documentation/filesystems/caching/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-master/Documentation/filesystems/caching/netfs-api.rst
63:blob into something it can use and may employ hash tables, trees or whatever to
382:Firstly, the netfs should determine if caching is available by doing something
linux-master/Documentation/filesystems/coda.rst
1298: Looks up something.
1319: expands something in a dynamic set.
linux-master/Documentation/filesystems/cramfs.rst
81:something like "root=mtd:fs_partition" on the kernel command line.
linux-master/Documentation/filesystems/debugfs.rst
42:something went wrong. If ERR_PTR(-ENODEV) is returned, that is an
157:If you want to dump a block of registers (something that happens quite
linux-master/Documentation/filesystems/directory-locking.rst
88:a subdirectory that already has an alias, something needs to be done with
119:filesystem, overlayfs doing something to the layers, network filesystem
linux-master/Documentation/filesystems/fuse.rst
366:something must be done about these.
linux-master/Documentation/filesystems/gfs2-uevents.rst
65:information about what the error is, which is something that needs to
linux-master/Documentation/filesystems/hpfs.rst
88:something like 'chown luser file; chown root file' the file will contain
linux-master/Documentation/filesystems/locking.rst
215:dqio_sem) (unless an admin really wants to screw up something and
563:since this is something the userspace has to take care about.
570:not normally something one needs to worry about. Return values > 0 will be
713:(if you break something or notice that it is broken and do not fix it yourself
linux-master/Documentation/filesystems/mount_api.rst
139: something more exotic, such as the "host:/path" that NFS desires.
linux-master/Documentation/filesystems/nfs/reexport.rst
91:something that also supports NFSv3, you're *probably* OK. Re-exporting
linux-master/Documentation/filesystems/orangefs.rst
162:Change the ID to something other than the ID of the first FileSystem
linux-master/Documentation/filesystems/overlayfs.rst
463:layer is fully trusted (by using dm-verity or something similar), then
linux-master/Documentation/filesystems/path-lookup.rst
173:be freed and used for something else, so the values in various fields
318:look ups from the start and will normally return something from the
507:goal of the lookup is to create something, then any value for
525:further up the path and that something that was thought to be valid
638:notices that something has changed or is changing, or if something
822:something that actually is there. When RCU-walk fails to find
823:something in the dentry cache, whether it is really there or not, it
933:this whole process is assuming something is safe when in reality it
1155:something that looks like a symlink. It is really a reference to the
linux-master/Documentation/filesystems/path-lookup.txt
367:Note that a graceful drop from rcu-walk mode due to something such as the
linux-master/Documentation/filesystems/porting.rst
706:by ->iterate_shared(), you might need something to serialize the access
734:work just as well; if it's something more complicated, use dentry->d_parent.
751:to fake something for readlink(2).
821:that goes only for the things that are not needed to balance something
linux-master/Documentation/filesystems/proc.rst
594:2) If there is something at a given vaddr during the entirety of the
linux-master/Documentation/filesystems/ramfs-rootfs-initramfs.rst
21:Virtual Memory system needs the memory for something else. Similarly, data
327: something brand new. The kernel provides its own tools to create and
linux-master/Documentation/filesystems/relay.rst
348:an implementation of the subbuf_start() callback something like the
linux-master/Documentation/filesystems/seq_file.rst
49:sequence will continue until the user loses patience and finds something
50:better to do. The file is seekable, in that one can do something like the
190:code in the usual manner indicates that something went wrong; it will be
linux-master/Documentation/filesystems/sharedsubtree.rst
116: However let's see what happens if we mount something on the mount at /tmp
linux-master/Documentation/filesystems/vfs.rst
654: symlink, device, or just something filesystem won't do atomic
linux-master/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
2056: /* do something with rec */
2072: /* do something with rec */
3927:| it's something to be aware of. |
4508:| The original parent pointer design was too unstable for something like |
5333:an iteration of an existing mechanism and not something totally novel.
linux-master/Documentation/firmware-guide/acpi/DSD-properties-rules.rst
77:In all cases in which kernel code may do something that will confuse AML as a
linux-master/Documentation/firmware-guide/acpi/apei/einj.rst
23:has an option to enable error injection. Look for something called WHEA
197:You should see something like this in dmesg::
linux-master/Documentation/firmware-guide/acpi/osi.rst
42:using the same BIOS image? Often they need to do something different
50:In the past the kernel used to support something like:
159:for _REV = 3, and do something for Linux, but when Linux returned
linux-master/Documentation/gpu/amdgpu/debugging.rst
22:log may look something like this:
linux-master/Documentation/gpu/amdgpu/display/dc-debug.rst
72:change in real-time by using something like::
linux-master/Documentation/gpu/amdgpu/display/dcn-overview.rst
56:Always approach the DCN architecture as something flexible that can be
80:dc_plane should work to convert all pixels in the plane to something that can
linux-master/Documentation/gpu/amdgpu/display/display-contributing.rst
79:something simple to start contributing to the display, you can make patches for
152:display output fidelity, it would be good if this option was something that
linux-master/Documentation/gpu/amdgpu/display/index.rst
43:It is good to stress that the test phase is something that we take extremely
linux-master/Documentation/gpu/rfc/i915_scheduler.rst
99:I915_SUBMIT_FENCE is by design a future fence, so not really something we should
linux-master/Documentation/gpu/rfc/i915_small_bar.h
139: * it's something we can expect to see in the wild. See
linux-master/Documentation/gpu/rfc/i915_small_bar.rst
47: error capture, when for example something is not currently CPU accessible.
linux-master/Documentation/gpu/todo.rst
134:``drm_atomic_state`` should be renamed to something clearer like
331: default page prots to write-protected with something like this::
502:currently prints a warning whenever something is relying on this check with
linux-master/Documentation/gpu/vgaarbiter.rst
74: event if something changes on any card (not just the target)
linux-master/Documentation/hid/hid-bpf.rst
67:Morph a device into something else and control that from userspace
71:It cannot decide to dynamically transform a given device into something else
218: return 0; /* something went wrong */
linux-master/Documentation/hid/hiddev.rst
21:The data flow for a HID event produced by a device is something like
linux-master/Documentation/hid/hidintro.rst
414:When something does not work
linux-master/Documentation/hid/intel-ish-hid.rst
192:ISHTP client from either host or FW side wants to send something, it decides
linux-master/Documentation/hwmon/lm93.rst
87:value of prochot1_avg and prochot2_avg is something like a 2 period
linux-master/Documentation/hwmon/w83781d.rst
306: respectively. ATT could stand for Asustek something (although it would be
linux-master/Documentation/i2c/busses/i2c-ali15x3.rst
75:output of lspci will show something similar to the following::
89: then you must enable ACPI, the PMU, SMB, or something similar
linux-master/Documentation/i2c/busses/i2c-amd-mp2.rst
21:If you see something like this::
linux-master/Documentation/i2c/busses/i2c-amd8111.rst
18:If you see something like this::
linux-master/Documentation/i2c/busses/i2c-i801.rst
89:PCI devices. An output of lspci will show something similar to the
152:and you think there's something interesting on the SMBus (e.g. a
linux-master/Documentation/i2c/busses/i2c-ismt.rst
41:something similar to the following::
linux-master/Documentation/i2c/busses/i2c-nforce2.rst
35:If your ``lspci -v`` listing shows something like the following::
linux-master/Documentation/i2c/busses/i2c-nvidia-gpu.rst
16:If your ``lspci -v`` listing shows something like the following::
linux-master/Documentation/i2c/busses/i2c-ocores.rst
28:E.G. something like::
linux-master/Documentation/i2c/busses/i2c-sis630.rst
38:If you see something like this::
linux-master/Documentation/i2c/busses/i2c-sis96x.rst
29:The command ``lspci`` as root should produce something like these lines::
linux-master/Documentation/i2c/fault-codes.rst
76: This rather vague error means something went wrong when
linux-master/Documentation/i2c/i2c-protocol.rst
72: generates something like::
82: system memory into something that appears as a single transfer to the
linux-master/Documentation/i2c/i2c-stub.rst
66:something like relayfs.
linux-master/Documentation/i2c/i2c-topology.rst
28:Depending of the particular mux driver, something happens when there is
113: gates/muxes, i.e. something that closes automatically after a given
linux-master/Documentation/i2c/muxes/i2c-mux-gpio.rst
37:E.G. something like this for a MUX providing 4 bus segments
linux-master/Documentation/i2c/slave-interface.rst
16:use a character device, be in-kernel only, or something completely different::
linux-master/Documentation/i2c/writing-clients.rst
289:or reboots (including kexec) -- like turning something off -- use a
linux-master/Documentation/input/devices/joystick-parport.rst
151:In the era of 8-bit machines, there was something like de-facto standard
linux-master/Documentation/input/devices/yealink.rst
207::A: If you see something like:
linux-master/Documentation/input/ff.rst
36:something goes wrong.
linux-master/Documentation/input/gameport-programming.rst
36:space only when something really is using it. Disable it again in the
linux-master/Documentation/input/joydev/joystick-api.rst
184: /* do something interesting with processed events */
214:replace the read above with something like::
253: #if JS_VERSION > 0xsomething
linux-master/Documentation/input/joydev/joystick.rst
83:For automatic module loading, something like this might work - tailor to
linux-master/Documentation/input/multi-touch-protocol.rst
223:finger or a pen or something else. Finally, the ABS_MT_TRACKING_ID event
linux-master/Documentation/kbuild/kbuild.rst
18:by modprobe to not fail when trying to load something builtin.
linux-master/Documentation/kbuild/kconfig-language.rst
97: a) A new Kconfig option for something that used to always be built
linux-master/Documentation/kbuild/kconfig.rst
169: names, so you have to know something close to what you are
271: names, so you have to know something close to what you are
linux-master/Documentation/kernel-hacking/false-sharing.rst
107:perf reports something like::
linux-master/Documentation/kernel-hacking/hacking.rst
729: people to make sure you're not duplicating effort, or trying something
linux-master/Documentation/kernel-hacking/locking.rst
113:released. This means the CPU can do something else while you are
linux-master/Documentation/locking/preempt-locking.rst
30: something = tux[smp_processor_id()];
63:play while another task releases it. If you want to do something
linux-master/Documentation/locking/robust-futexes.rst
84:So something had to be done.
linux-master/Documentation/locking/rt-mutex-design.rst
30:is something called unbounded priority inversion. That is when the high
248: /* do something */
259: /* do something else */
269: /* do something again */
277:in func4 in the "do something again" area, we have a locking that follows::
linux-master/Documentation/maintainer/maintainer-entry-profile.rst
97:to do something different in the near future.
linux-master/Documentation/maintainer/pull-requests.rst
63: Note that if there is something odd about the pull request, that
174:something like::
linux-master/Documentation/maintainer/rebasing-and-merging.rst
222:arisen and be prepared to explain why something abnormal needs to be done.
linux-master/Documentation/memory-barriers.txt
745: do_something();
749: do_something_else();
760: do_something();
763: do_something_else();
776: do_something();
779: do_something_else();
788: do_something();
791: do_something_else();
804: do_something();
807: do_something_else();
816: do_something_else();
829: do_something();
832: do_something_else();
1585: do_something_with(tmp);
1593: do_something_with(tmp);
1598: do_something_with(tmp);
1606: do_something_with(tmp);
1612: do_something_with(a);
1615: passing a zero to do_something_with() in the case where the variable
1617: the call to do_something_with().
1622: do_something_with(tmp);
1635: do_something_with(tmp);
1649: do_something_with(tmp);
1656: do_something_with(tmp);
1730: be interrupted by something that also accesses 'flag' and 'msg',
2161:Firstly, the sleeper normally follows something like this sequence of events:
2200:Secondly, code that performs a wake up normally follows something like this:
2210:A general memory barrier is executed by wake_up() if it wakes something up.
2228:if something is actually awakened, but otherwise there is no such guarantee.
2276: do_something(my_data);
2292: do_something(my_data);
2489:efficient to reorder, combine or merge accesses - something that would cause
linux-master/Documentation/mm/damon/design.rst
452:self-written programs or have good profiling tools, they could know something
linux-master/Documentation/mm/highmem.rst
193: page being 32-bytes that would end up being something in the order of 112G
linux-master/Documentation/mm/hugetlbfs_reserv.rst
155:the global reservation count resv_huge_pages is adjusted something like the
linux-master/Documentation/mm/slub.rst
337:to something easier -- visual analysis.
linux-master/Documentation/mm/vmalloced-kernel-stacks.rst
53:- If the stack overflows into a guard page, something reasonable
linux-master/Documentation/networking/6pack.rst
33: to experiment with something completely different from the known CSMA and
171:this is a problem of the 6pack driver or something else in the kernel.
linux-master/Documentation/networking/af_xdp.rst
415:going to receive something when you in fact will not, and this can
775:really used to make something more advanced, take a look at the libbpf
linux-master/Documentation/networking/arcnet-hardware.rst
46:well-designed standard. It uses something called "modified token passing"
137: must be properly terminated with 93 Ohm (or something else if you don't
1160: something else. Put only one jumper on the IRQ pins.
linux-master/Documentation/networking/arcnet.rst
253:do something like this::
594:Go take a nap or something. You'll feel better in the morning.
linux-master/Documentation/networking/bonding.rst
1127:something like this::
linux-master/Documentation/networking/can.rst
348: /* do something with the received CAN frame */
linux-master/Documentation/networking/device_drivers/cable/sb1000.rst
126: If this doesn't help, try something like ``ping -c 5 204.71.200.67`` to
203: and try setting the delay to something like 60 microseconds with:
linux-master/Documentation/networking/device_drivers/can/can327.rst
265: then be mistaken for something else.
linux-master/Documentation/networking/device_drivers/can/ctu/ctucanfd-driver.rst
207:#. **Error condition**. If something goes wrong (e.g., the device goes
linux-master/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/overview.rst
202:enqueue/dequeue packets. To enqueue something a descriptor is written
240: A DPNI must be connected to something such as a DPMAC,
linux-master/Documentation/networking/devlink/devlink-health.rst
11:order to know when something bad happened to a PCI device.
linux-master/Documentation/networking/dsa/dsa.rst
76:all contain something which:
linux-master/Documentation/networking/eql.rst
72: Unpack a recent kernel (something after 1.1.92) someplace convenient
188: make sure you have asyncmap set to something so that control
linux-master/Documentation/networking/ethtool-netlink.rst
297:netlink code which are only sent if something actually changed, notifications
linux-master/Documentation/networking/generic-hdlc.rst
46:Usually you want something like::
linux-master/Documentation/networking/ieee802154.rst
86:submits skb to qdisc), so if you need something from that cb later, you should
linux-master/Documentation/networking/ip-sysctl.rst
676: something is wrong due to unacknowledged RTO retransmissions,
linux-master/Documentation/networking/j1939.rst
30:Given the fact there's something like SocketCAN with an API similar to BSD
linux-master/Documentation/networking/phy.rst
181:The name will look something like, "0:00", where the first number is the
linux-master/Documentation/networking/pktgen.rst
81:device@something
linux-master/Documentation/networking/radiotap-headers.rst
118: /* see if this argument is something we can use */
linux-master/Documentation/networking/rxrpc.rst
788: (3) Request the use of something other than GFP_KERNEL to allocate memory.
linux-master/Documentation/networking/tc-actions-env-rules.rst
29:Post on netdev if something is unclear.
linux-master/Documentation/networking/tcp_ao.rst
268: | | to perform | something like |
linux-master/Documentation/networking/tls.rst
193: // Do something with record_type, and control message data in
linux-master/Documentation/networking/xfrm_device.rst
36:be handy when experimenting. An example command might look something
linux-master/Documentation/power/freezing-of-tasks.rst
129: processes, but if any of the kernel threads may cause something like this
linux-master/Documentation/power/opp.rst
197: /* do something when we can't satisfy the req */
217: implementation might choose to do something as follows::
227: goto try_something_else;
234: choose to do something as follows::
244: goto try_something_else;
linux-master/Documentation/power/powercap/dtpm.rst
14:performance is capped while a big CPU is processing something else. Or
linux-master/Documentation/power/regulator/machine.rst
52:The name field should be set to something that is usefully descriptive
linux-master/Documentation/power/swsusp-dmcrypt.rst
57:named "swapkey". /etc/fstab of your initrd contains something
linux-master/Documentation/power/swsusp.rst
22: between suspend and resume, it may do something wrong. If you change
98:to interrupt our programs so processes that are calculating something for a long
147: Maybe I'm missing something, but why don't the regular I/O paths work?
388: Well, last messages on the screen are always useful. If something
linux-master/Documentation/power/tricks.rst
14:* use ext2. At least it has working fsck. [If something seems to go
linux-master/Documentation/power/video.rst
77:Now, if you pass acpi_sleep=something, and it does not work with your
linux-master/Documentation/process/2.Process.rst
473:to test the waters with something smaller first. This is the point where
linux-master/Documentation/process/4.Coding.rst
197:change (which may bring big improvements) which causes something to break
423:something that kernel developers need to be worried about, but we also do
linux-master/Documentation/process/5.Posting.rst
339:something like:
linux-master/Documentation/process/6.Followthrough.rst
77:that you don't realize that something is fundamentally wrong or, perhaps,
211:On very rare occasion, you may see something completely different: another
linux-master/Documentation/process/adding-syscalls.rst
27: userspace that something has happened, then returning a new file
linux-master/Documentation/process/applying-patches.rst
121:If patch encounters something that doesn't look quite right it has two
125:One example of something that's not 'quite right' that patch will attempt to
219:This will let you move from something like 5.7.2 to 5.7.3 in a single
linux-master/Documentation/process/backporting.rst
187:This can also be a handy way to quickly find when something (e.g. a
256:something like::
266:output would look something like this::
395:As a first pass, you can try something like this, which will lower the
442:go wrong during backports is that something else in the function changed
linux-master/Documentation/process/botching-up-ioctls.rst
21:something every GPU driver has to do on its own.
154: Especially if your reference clock is something really slow like the display
linux-master/Documentation/process/clang-format.rst
52:To do so, you can run something like::
linux-master/Documentation/process/coding-style.rst
65:something to hide:
70: do_something_everytime;
231: do_something();
402: Again - there needs to be a **reason** for this. If something is
465:shouldn't exceed 5-10, or you're doing something wrong. Re-think the
610:small comments to note or warn about something particularly clever (or
784:because they slept or did something else for a while.
926:so prefer to use dev_dbg/pr_debug unless something is wrong.
1011:something it would have done anyway.
linux-master/Documentation/process/deprecated.rst
185:If you are debugging something where "%p" hashing is causing problems,
211: do_something();
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;
358: struct something {
368: struct something {
linux-master/Documentation/process/email-clients.rst
330: :menuselection:`Main Menu-->Account Settings-->[email protected]>Composition & Addressing`!
linux-master/Documentation/process/handling-regressions.rst
161: * Do not consider regressions from the current cycle as something that can wait
181: regression is something people can live with easily for a while -- like a
340:sure to do something that was expected long before regzbot came to light: add
356:Ideally yes: we are all humans and easily forget problems when something more
358:kernel or something in real life that's keeping us away from keyboards for a
516: But if something actually breaks, then the change must get fixed or
545: up". Whoever broke something gets to fix it too.
568: And obviously, if users take years to even notice that something
575: code was in staging or because the man-page said something else) is
625: Guys, whether something was buggy or not DOES NOT MATTER.
630: something because we were fixing a bug" is completely insane. We fix
632: we can break something is simply NOT TRUE.
653: It's basically saying "I took something that worked, and I broke it,
663: MUCH BIGGER bug by "fixing" something that the user clearly didn't
772: something breaks existing users' workflow.
linux-master/Documentation/process/howto.rst
195:first, before asking something that has already been answered in the
538: proportional to the size of the patch, or something).
540: Small patches also make it very easy to debug when something goes
543: something).
linux-master/Documentation/process/magic-number.rst
46: something will change before 2.2.x. The entries are
linux-master/Documentation/process/maintainer-pgp-guide.rst
213:more reasons you have to create a backup version that lives on something
310:The output will be something like this::
706:The merge message will contain something like this::
839:that the key used to sign something belongs to the actual kernel
linux-master/Documentation/process/maintainer-tip.rst
616: do_something();
623: do_something(foo[i]);
629: do_something(foo[i]);
linux-master/Documentation/process/management-style.rst
130:something wrong with both projects, and the reason the people involved
203:second version in particular is a great way to either learn something
204:new about "xxx" or seem **extra** managerial by pointing out something the
212:are doing something irreversible when you **do** prod them in some
linux-master/Documentation/process/stable-api-nonsense.rst
20: will not break. I have old programs that were built on a pre 0.9something
196:proven type of development model must be doing something right :)
linux-master/Documentation/process/submitting-patches.rst
117:result of some earlier mailing list discussions or something documented on the
linux-master/Documentation/process/volatile-considered-harmful.rst
31: do_something_on(&shared_data);
32: do_something_else_with(&shared_data);
linux-master/Documentation/scheduler/completion.rst
15:yield() or some quirky msleep(1) loop to allow something else to proceed,
linux-master/Documentation/scheduler/sched-bwc.rst
30:Traditional (UP-EDF) bandwidth control is something like:
linux-master/Documentation/scheduler/sched-deadline.rst
733: Thread parameters can be specified from the command line, with something like
744: can be passed as input to rt-app with something like this::
linux-master/Documentation/scsi/ChangeLog.megaraid
301: to something here. Let each driver add files as such:"
362: without putting code something like this into the driver."
linux-master/Documentation/scsi/ChangeLog.ncr53c8xx
151: Basically the BARs have been changed to something more complex
383: - Fix something that looks like an old bug in the nego SIR
linux-master/Documentation/scsi/ChangeLog.sym53c8xx
276: Basically the BARs have been changed to something more complex
linux-master/Documentation/scsi/advansys.rst
144: Increasing LOG_BUF_LEN in kernel/printk.c to something like
linux-master/Documentation/scsi/dc395x.rst
110:Note: The GNU GPL says also something about warranty and liability.
linux-master/Documentation/scsi/ncr53c8xx.rst
378:and you will get something like the following text::
683: to something other than the default order or "reverse probe" order.
1801:types of cards are scanned in, something "reverse probe" cannot do.
linux-master/Documentation/scsi/qlogicfas.rst
52:command or something. It comes up faster if this is set to zero, and
linux-master/Documentation/scsi/scsi_fc_transport.rst
96: allow the parent of the vport to be something other than the scsi_host.
linux-master/Documentation/scsi/scsi_mid_low_api.rst
325: * ERR_PTR(-ENODEV) (or some other bent pointer) if something is
linux-master/Documentation/scsi/st.rst
116:tape in the drive (commands trying to write something return error if
665:waiting for something. The field WCHAN tells where the driver is
linux-master/Documentation/security/credentials.rst
492:A typical credentials alteration function would look something like this::
linux-master/Documentation/security/keys/core.rst
506: Only the superuser can change a key's owner to something other than the
508: group ID to something other than the calling process's group ID or one of
1555: and may attach something to the preparsed pointer for use by ``(*cmp)()``.
1618: key's payload into something a blob of data for userspace to deal with.
linux-master/Documentation/security/siphash.rst
48:If you pass the generic siphash function something of a constant length, it
167:If you pass the generic hsiphash function something of a constant length, it
linux-master/Documentation/security/tpm/tpm_event_log.rst
14:time something gets hashed by it to any of the PCR registers. The events
linux-master/Documentation/sound/cards/multisound.sh
355:# There is something to note about using the S/PDIF port. Digital
linux-master/Documentation/sound/hd-audio/notes.rst
114:it means that something is really wrong. Most likely you are
linux-master/Documentation/sound/kernel-api/writing-an-alsa-driver.rst
411:When something goes wrong, the probe function needs to deal with the
1256: /* do something to start the PCM engine */
1260: /* do something to stop the PCM engine */
1943: /* do something to start the PCM engine */
1946: /* do something to stop the PCM engine */
linux-master/Documentation/sphinx/automarkup.py
286: # validity. (Maybe we can do something in the future to warn about
linux-master/Documentation/spi/butterfly.rst
14:can come up with something fancier, providing circuit protection to the
linux-master/Documentation/spi/spi-summary.rst
242:And SOC-specific utility code might look something like::
linux-master/Documentation/staging/remoteproc.rst
95: * something went wrong. handle it and leave.
300:do something (e.g. allocate a system resource). Sometimes a negotiation
linux-master/Documentation/staging/xz.rst
121:kernel-related mailing lists, so if there's something I should know,
linux-master/Documentation/target/tcmu-design.rst
74:with the LIO loopback fabric to become something similar to FUSE
linux-master/Documentation/timers/no_hz.rst
205:something else is in the way? This section helps answer this question
linux-master/Documentation/timers/timers-howto.rst
71: it is something to be aware of.
linux-master/Documentation/trace/ftrace-design.rst
41:running something like::
354:Every arch has an init callback function. If you need to do something early on
linux-master/Documentation/trace/ftrace.rst
2026:That is the longest latency it takes for something to happen,
2398:something like following code snippet can be used::
2450:something like this simple program.
3377: something, and want to dump the trace when a certain function
linux-master/Documentation/trace/histogram-design.rst
859:Adding onto the previous example, we will now do something with that
875:trace event. Since this is something that almost every trace() and
linux-master/Documentation/trace/histogram.rst
1014: paused state, then unpause it and do something you want to measure,
1192: Displaying the 'hist' file should show something similar to what you
1698:it is set to something else by a subsequent event. The one exception
2537:and after it wakes up, something like this::
2548:And later add something like::
linux-master/Documentation/trace/kprobetrace.rst
264: Open something...
linux-master/Documentation/trace/tracepoint-analysis.rst
60:to page allocation would look something like::
linux-master/Documentation/trace/user_events.rst
231:writev() calls when something is actively attached to the event.
235:to see if something is attached or not.
linux-master/Documentation/translations/it_IT/process/coding-style.rst
76: do_something_everytime;
243: do_something();
linux-master/Documentation/translations/it_IT/process/deprecated.rst
231: do_something();
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 {
403: struct something {
linux-master/Documentation/translations/it_IT/process/volatile-considered-harmful.rst
38: do_something_on(&shared_data);
39: do_something_else_with(&shared_data);
linux-master/Documentation/translations/ko_KR/memory-barriers.txt
751: do_something();
755: do_something_else();
766: do_something();
769: do_something_else();
781: do_something();
784: do_something_else();
793: do_something();
796: do_something_else();
809: do_something();
812: do_something_else();
820: do_something_else();
832: do_something();
835: do_something_else();
1559: do_something_with(tmp);
1566: do_something_with(tmp);
1571: do_something_with(tmp);
1578: do_something_with(tmp);
1584: do_something_with(a);
1587: do_something_with() 호출 사이에 바뀌어 do_something_with() 에 0을 넘길
1593: do_something_with(tmp);
1605: do_something_with(tmp);
1619: do_something_with(tmp);
1626: do_something_with(tmp);
2229: do_something(my_data);
2245: do_something(my_data);
linux-master/Documentation/translations/sp_SP/process/deprecated.rst
231: do_something();
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-master/Documentation/translations/sp_SP/process/email-clients.rst
351: :menuselection:`Main Menu-->Account Settings-->[email protected]>Composition & Addressing`!
linux-master/Documentation/translations/zh_CN/admin-guide/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-master/Documentation/translations/zh_CN/core-api/protection-keys.rst
64: *ptr = foo; // assign something
81: something(ptr);
87: something(ptr);
89:无论something()是否是对'ptr'的直接访问，这都应该为真。
linux-master/Documentation/translations/zh_CN/cpu-freq/cpu-drivers.rst
252: /* Do something with pos */
linux-master/Documentation/translations/zh_CN/power/opp.rst
201: goto try_something_else;
217: goto try_something_else;
linux-master/Documentation/translations/zh_CN/process/coding-style.rst
76: do_something_everytime;
linux-master/Documentation/translations/zh_CN/process/volatile-considered-harmful.rst
40: do_something_on(&shared_data);
41: do_something_else_with(&shared_data);
linux-master/Documentation/translations/zh_TW/admin-guide/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-master/Documentation/translations/zh_TW/cpu-freq/cpu-drivers.rst
252: /* Do something with pos */
linux-master/Documentation/translations/zh_TW/process/coding-style.rst
79: do_something_everytime;
linux-master/Documentation/translations/zh_TW/process/volatile-considered-harmful.rst
43: do_something_on(&shared_data);
44: do_something_else_with(&shared_data);
linux-master/Documentation/usb/authorization.rst
65:checking if the class, type and protocol match something is the worse
67:to break it). If you need something secure, use crypto and Certificate
linux-master/Documentation/usb/dwc3.rst
9:Please pick something while reading :)
42: handed something to thread so we don't process event X prio Y
linux-master/Documentation/usb/gadget-testing.rst
782:actually hear something at the device side, a command similar
972:actually hear something at the device side, a command similar
linux-master/Documentation/usb/gadget_hid.rst
21:HID function descriptors you want to use - E.G. something
linux-master/Documentation/usb/gadget_serial.rst
197:should show something like this:::
229:should show something like this:::
252:system log saying something like "Gadget Serial converter now
linux-master/Documentation/usb/usbmon.rst
94:This is where you do something that creates the traffic: plug in a flash key,
167: If they find something else, like a letter, they read the setup packet before
linux-master/Documentation/userspace-api/gpio/error-codes.rst
30: returned when an ioctl attempts something that would require the
linux-master/Documentation/userspace-api/iommufd.rst
136:- In-kernel user - refers to something like a VFIO mdev that is using the
linux-master/Documentation/userspace-api/media/gen-errors.rst
36: change something that would affect the stream, or would require
linux-master/Documentation/userspace-api/media/rc/rc-sysfs-nodes.rst
37:Reading this file returns a list of available protocols, something like::
93:wakeup filter, something like::
linux-master/Documentation/userspace-api/media/v4l/colorspaces-details.rst
729: information. So if something other than sRGB is used, then the driver
linux-master/Documentation/userspace-api/media/v4l/dev-mem2mem.rst
29:properties are global to the device (i.e. changing something through one
linux-master/Documentation/userspace-api/media/v4l/dv-timings.rst
55:event so you know when something changed.
linux-master/Documentation/userspace-api/media/v4l/vidioc-reqbufs.rst
105: free any previously allocated buffers, so this is typically something
linux-master/Documentation/userspace-api/media/videodev2.h.rst.exceptions
11:# having something not documented at the uAPI.
linux-master/Documentation/userspace-api/netlink/intro.rst
37:something like:
linux-master/Documentation/userspace-api/no_new_privs.rst
56: fcap-using binaries; it will need to compromise something without the
linux-master/Documentation/userspace-api/seccomp_filter.rst
112: dependent value -- if resuming execution, set it to something
340:something like ``acpi_pm``.
linux-master/Documentation/virt/kvm/halt-polling.rst
12:before giving up the cpu to the scheduler in order to let something else run.
linux-master/Documentation/virt/kvm/ppc-pv.rst
116:of something. This is what we call "flags".
linux-master/Documentation/virt/kvm/vcpu-requests.rst
238:sending kick also change the VCPU mode to something !IN_GUEST_MODE. The
linux-master/Documentation/virt/kvm/x86/msr.rst
232: something that can generate normal page fault.
linux-master/Documentation/virt/uml/user_mode_linux_howto_v2.rst
30:concepts which map onto something provided by the host - files, sockets,
83: new processes and threads (something most Unix/Linux applications
346:is a privilege which is offered only to something which can hook up
484:easier (and less verbose) ways to connect a UML instance to something.
595:in order to do something useful.
646:console to use something different from the default xterm.
1035:something which is being worked on at present.
1076:Not an issue with UML. At the same time, this is something which
1081:If you have something to contribute such as a patch, a bugfix, a
linux-master/Documentation/watchdog/convert_drivers_to_kernel_api.rst
183:by adding a module parameter. The conversion for this would be something like::
linux-master/Documentation/watchdog/watchdog-parameters.rst
23: fallback logic in the bootloader to try something else.
linux-master/LICENSES/deprecated/GPL-1.0
245:commands you use may be called something other than `show w' and `show
linux-master/LICENSES/preferred/GPL-2.0
342:be called something other than `show w' and `show c'; they could even be
linux-master/arch/Kconfig
1340: - If the stack overflows into a guard page, something reasonable
linux-master/arch/alpha/Kconfig
494: SRM is something like a BIOS for Alpha machines. There are some
linux-master/arch/alpha/include/asm/core_cia.h
319: * See p 6-17 of the specification but it looks something like this:
linux-master/arch/alpha/include/asm/core_mcpcia.h
227: * See p 6-17 of the specification but it looks something like this:
linux-master/arch/alpha/include/asm/core_t2.h
419: * See p 6-17 of the specification but it looks something like this:
linux-master/arch/alpha/include/asm/elf.h
75: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/alpha/include/asm/pgtable.h
168: * a safe thing to do. Come the first core logic that does put something
linux-master/arch/alpha/include/asm/xchg.h
102: if something tries to do an invalid xchg(). */
225: if something tries to do an invalid cmpxchg(). */
linux-master/arch/alpha/kernel/entry.S
841: /* Special because it needs to do something opposite to
linux-master/arch/alpha/kernel/irq_alpha.c
28: * do something useful.
linux-master/arch/alpha/kernel/pci_iommu.c
180: The chip specific bits will fill this in with something
linux-master/arch/alpha/kernel/smp.c
303: /* Initialize the CPU's HWPCB to something just good enough for
linux-master/arch/alpha/kernel/sys_cabriolet.c
125: Cabriolet based systems. However, something got screwed up late
linux-master/arch/alpha/kernel/traps.c
338: and if we don't put something on the entry point we'll oops. */
359: * on a gp-register unaligned load/store, something is _very_ wrong
linux-master/arch/arc/include/asm/elf.h
33: * -we don't load something for the wrong architecture.
linux-master/arch/arc/include/asm/smp.h
89: * guaranteed by the platform (not something which core handles).
linux-master/arch/arc/net/bpf_jit.h
34: * the underlying "arc_*(buf, ...)" ends up as NULL instead of something
linux-master/arch/arc/net/bpf_jit_arcv2.c
1396: * not known, the BPF instruction may look something like:
1406: * to the resolved address and looks something like:
linux-master/arch/arc/net/bpf_jit_core.c
731: * If the "ret" value is negative, something has went wrong. Else,
linux-master/arch/arm/boot/dts/marvell/kirkwood-b3.dts
88: * There is something on the bus at address 0x64.
linux-master/arch/arm/boot/dts/nvidia/tegra114-asus-tf701t.dts
197: /* XXX make this something more sensible */
linux-master/arch/arm/boot/dts/rockchip/rk3288-veyron.dtsi
269: * we just refer to vcc33_io every time something is
linux-master/arch/arm/crypto/aes-ce-glue.c
429: * to do something else.
linux-master/arch/arm/crypto/aes-neonbs-glue.c
278: * to do something else.
linux-master/arch/arm/include/asm/elf.h
106: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/arm/include/asm/ptrace.h
76: * Force CPSR to something logical...
linux-master/arch/arm/include/asm/vdso/gettimeofday.h
124: * update. Return something. Core will do another round and then
linux-master/arch/arm/include/debug/ux500.S
16: * built, so that there's some hint during the build that something is wrong.
linux-master/arch/arm/kernel/head-common.S
26: * If CONFIG_DEBUG_LL is set we try to print out something about the error
linux-master/arch/arm/kernel/irq.c
112: * than crashing, do something sensible.
linux-master/arch/arm/kernel/traps.c
631: * is defined to be something else. For now we ignore it, but may
673: * something catastrophic has happened
linux-master/arch/arm/kernel/vmlinux-xip.lds.S
187: * something which doesn't cover reprogramming code itself, so as soon
linux-master/arch/arm/mach-exynos/pm.c
237: * Set the boot vector to something non-zero
linux-master/arch/arm/mach-mstar/mstarv7.c
19: * for something in the same area called "AXI".
linux-master/arch/arm/mach-nomadik/Makefile
7:# unless it's something special (ie not a .c file).
linux-master/arch/arm/mach-omap1/hardware.h
112: * or something similar.. -- PFM.
linux-master/arch/arm/mach-omap1/serial.c
167: /* Need to do something with serial port right after wake-up? */
linux-master/arch/arm/mach-omap2/display.c
56: * reset before deciding that something has gone wrong
linux-master/arch/arm/mach-omap2/omap_hwmod.c
848: * to do something meaningful. Today its just a no-op.
890: * to do something meaningful. Today its just a no-op.
927: * to do something meaningful. Today its just a no-op.
1657: * Since integration code might still be doing something, only
3822: * If the callback function returns something other than
linux-master/arch/arm/mach-omap2/omap_hwmod.h
160: * @name should be something short, e.g., "cpu0" or "rst". It is defined
422: * this is really true -- we're probably not configuring something
linux-master/arch/arm/mach-omap2/powerdomains2xxx_3xxx_data.c
24: * The 2420 also has something called the IVA, which is a separate ARM
linux-master/arch/arm/mach-omap2/sdrc.h
178: * will result in something which you can switch between.
linux-master/arch/arm/mach-omap2/sr_device.c
67: * ES3.something.
linux-master/arch/arm/mach-pxa/am200epd.c
149: /* rough check if this is our desired fb and not something else */
linux-master/arch/arm/mach-rpc/ecard.c
527: * something seriously wrong. Disable the expansion card
linux-master/arch/arm/mach-sa1100/assabet.c
703: * isn't compiled in so the user will still get something on
linux-master/arch/arm/mach-sa1100/neponset.c
342: * something on the Neponset activates this IRQ on sleep (eth?)
linux-master/arch/arm/probes/kprobes/test-core.c
106: * The above would expand to assembler looking something like:
linux-master/arch/arm/vfp/vfpmodule.c
651: * software assistance to complete, something which is not currently
654: * is properly preceded by a call to kernel_neon_begin(), something has
linux-master/arch/arm64/boot/dts/qcom/sm8350-sony-xperia-sagami.dtsi
20: * shortly after closing UEFI boot services.. Perhaps that has something
linux-master/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi
570: * mux them to something else.
798: * to avoid getting access to JTAG just by sticking something
linux-master/arch/arm64/include/asm/elf.h
95: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/arm64/include/asm/vdso/compat_gettimeofday.h
113: * update. Return something. Core will do another round and then
linux-master/arch/arm64/include/asm/vdso/gettimeofday.h
76: * update. Return something. Core will do another round and then
linux-master/arch/arm64/kernel/acpi.c
347: * that memory and use it for something else. We never
linux-master/arch/arm64/kernel/fpsimd.c
96: * For a certain task, the sequence may look something like this:
1166: * If something went wrong, at least try to patch it up:
1435: * If this not a trap due to SME being disabled then something
1479: * When FPSIMD is enabled, we should never take a trap unless something
1991: * either doing something wrong or you need to propose some refactoring.
linux-master/arch/arm64/kernel/hyp-stub.S
218: * something else went wrong... in such cases, trying to install a new
222: * so you will need to set that to something sensible at the new hypervisor's
linux-master/arch/arm64/kernel/pi/map_kernel.c
61: * those instructions into something else.
linux-master/arch/arm64/kernel/proton-pack.c
15: * "If there's something strange in your neighbourhood, who you gonna call?"
linux-master/arch/arm64/kernel/suspend.c
123: * something like raw_local_daif_save().
linux-master/arch/arm64/kernel/sys_compat.c
79: * is defined to be something else. For now we ignore it, but may
linux-master/arch/arm64/kernel/syscall.c
89: * doing something stupid, such as setting PROT_BTI on a page
linux-master/arch/arm64/kernel/traps.c
1077: * This is something that might be fixed at some point in the future.
linux-master/arch/arm64/kvm/arm.c
2029: * If the cpucaps haven't been finalized yet, something has gone very
2795: * FIXME: Do something reasonable if kvm_init() fails after pKVM
linux-master/arch/arm64/kvm/emulate-nested.c
384: * to generate something that is in the E2H=1 format, and live with
linux-master/arch/arm64/kvm/hyp/nvhe/ffa.c
540: * check that we end up with something that doesn't look _completely_
linux-master/arch/arm64/kvm/hyp/nvhe/page_alloc.c
43: * something else and may not be mapped in hyp_vmemmap.
linux-master/arch/arm64/kvm/vgic/vgic-its.c
1516: * programming a bogus value in CBASER or something else going
linux-master/arch/arm64/kvm/vgic/vgic.c
364: * Did something change behind our backs?
linux-master/arch/arm64/lib/insn.c
770: /* If we have something in the top 12 bits... */
linux-master/arch/arm64/tools/sysreg
49:# item ACCDATA) though it may be more taseful to do something else.
linux-master/arch/csky/include/asm/elf.h
44: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/hexagon/include/asm/elf.h
151: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/hexagon/include/asm/io.h
194: * inb - read byte from I/O port or something
linux-master/arch/hexagon/kernel/module.c
61: * @symindex - symbol index offset or something?
linux-master/arch/hexagon/kernel/setup.c
93: * Probably should move to kernel/proc.c or something.
linux-master/arch/hexagon/mm/init.c
107: * Start of high memory area. Will probably need something more
linux-master/arch/loongarch/include/asm/elf.h
163: * This is used to ensure we don't load something for the wrong architecture.
179: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/loongarch/kernel/machine_kexec.c
168: * wrong, but we need something to keep from crashing again.
linux-master/arch/m68k/coldfire/reset.c
21: * have something completely special to them, and we let their specific
linux-master/arch/m68k/ifpsp060/TEST.DOC
96:itest.sa data and execute something similar to:
linux-master/arch/m68k/ifpsp060/fpsp.doc
101:(vector #11), the operating system should execute something similar to:
linux-master/arch/m68k/ifpsp060/isp.doc
109:exception (vector #61), the operating system should execute something
linux-master/arch/m68k/include/asm/elf.h
47: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/m68k/include/asm/io_no.h
31: * definitions so we can figure out if need to do something special.
45: * applies just the same of there is no MMU but something like a PCI bus
linux-master/arch/m68k/include/asm/machines.h
73: * something if the value in the ARCH field is SM_SUN4M, if it is
linux-master/arch/m68k/mac/macints.c
86: * The current interrupt logic looks something like this:
linux-master/arch/m68k/math-emu/fp_util.S
49: * something here. %d0 and %d1 is always usable, sometimes %d2 (or
linux-master/arch/m68k/q40/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.
53:preceded by the booter signature. This is a trace just in case something
linux-master/arch/m68k/q40/q40ints.c
322: /* disable ISA iqs : only do something if the driver has been
linux-master/arch/m68k/sun3/config.c
96:/* Without this, Bad Things happen when something calls arch_reset. */
linux-master/arch/m68k/sun3/mmu_emu.c
147: used for something, and we probably shouldn't risk it */
linux-master/arch/microblaze/include/uapi/asm/elf.h
26: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/mips/alchemy/common/dbdma.c
643: /* Return something non-zero. */
706: /* Return something non-zero. */
751: /* Return something non-zero. */
978: /* Return something non-zero. */
linux-master/arch/mips/cavium-octeon/setup.c
887: * To do: switch parsing to new style, something like:
linux-master/arch/mips/generic/board-sead3.c
168: /* if this isn't SEAD3, something went wrong */
linux-master/arch/mips/include/asm/elf.h
219: * This is used to ensure we don't load something for the wrong architecture.
235: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/mips/include/asm/ip32/mace.h
172: /* 1 - Dma engine is enabled and processing something */
linux-master/arch/mips/include/asm/sn/sn0/hubio.h
436: * this is not something that can be done easily. So, AVOID updating
linux-master/arch/mips/include/asm/vdso/gettimeofday.h
199: * update. Return something. Core will do another round see the
linux-master/arch/mips/include/asm/vpe.h
72: /* the list of who wants to know when something major happens */
linux-master/arch/mips/kernel/cps-vec-ns16550.S
165: * will only be run if something goes horribly wrong very early during
linux-master/arch/mips/kernel/crash.c
29: * wrong, but we need something to keep from crashing again.
linux-master/arch/mips/kernel/process.c
580: * something within the stack of the current task
842: * process may be running on to schedule something else - in this case
linux-master/arch/mips/kernel/smp.c
367: * to an option instead of something based on .cputype
linux-master/arch/mips/kernel/traps.c
629: return -1; /* Must be something else ... */
706: return -1; /* Must be something else ... */
linux-master/arch/mips/kernel/unaligned.c
451: /* Signal if something went wrong. */
972: /* If something went wrong, signal */
linux-master/arch/mips/kvm/entry.c
524: * does something that causes a trap to kernel mode.
linux-master/arch/mips/math-emu/dsemul.c
49: * - The instruction in @emul may be something entirely invalid for a
51: * in a delay slot, or a kernel mode instruction, or something else
189: * then something is amiss & the user has branched into some other area
linux-master/arch/mips/mm/c-r4k.c
387: * These caches are inclusive caches, that is, if something
1656: * silly idea of putting something else there ...
linux-master/arch/mips/mm/tlbex.c
2099: * Warn if something may race with us & replace the TLB entry
2165: * Warn if something may race with us & replace the TLB entry
linux-master/arch/mips/pci/fixup-cobalt.c
115: * something sensible when using the new Galileo.
linux-master/arch/mips/sgi-ip30/ip30-irq.c
66: * If we also have a cause value, then something happened, so loop
linux-master/arch/mips/sni/rm200.c
231: * is something bad going on ...
linux-master/arch/mips/tools/generic-board-config.sh
60: # If we require something =y then we check that a line
65: # If we require something =n then we just invert that
linux-master/arch/nios2/include/asm/elf.h
12: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/openrisc/include/asm/cmpxchg.h
116: * if something tries to do an invalid cmpxchg().
145: * something tries to do an invalidly-sized xchg().
linux-master/arch/openrisc/include/asm/elf.h
22: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/openrisc/include/asm/thread_info.h
27: * normally, the stack is found by doing something like p + THREAD_SIZE
linux-master/arch/openrisc/kernel/head.S
1490: * only if you need to debug something that goes wrong
linux-master/arch/openrisc/kernel/ptrace.c
204: * error, but leave the original number in <something>.
linux-master/arch/openrisc/kernel/unwinder.c
49: * The OpenRISC stack frame looks something like the following. The
linux-master/arch/openrisc/mm/init.c
59: * something else then this needs to change.
135: /* make sure the current pgd table points to something sane
linux-master/arch/parisc/include/asm/elf.h
339: (2 * TASK_SIZE / 3) turns into something undefined when run through a
linux-master/arch/parisc/include/asm/hugetlb.h
16: * If the arch doesn't supply something else, assume that hugepage
linux-master/arch/parisc/kernel/drivers.c
200: * Formula is something like memsize/(num_iommu * entry_size).
linux-master/arch/parisc/kernel/firmware.c
35: * something useful even if the call failed) unless you are sure
linux-master/arch/parisc/kernel/head.S
221: ** %r2 in case rfi target decides it didn't like something
linux-master/arch/parisc/kernel/pdc_chassis.c
138: /* Let see if we have something to handle... */
linux-master/arch/parisc/kernel/perf_images.h
350: * ctr1 : counts cycles where something retired
linux-master/arch/parisc/kernel/ptrace.c
88: parent know something happened. */
linux-master/arch/parisc/kernel/syscall.S
47: * something that will kill the kernel or a
linux-master/arch/parisc/kernel/traps.c
487: * then the user is attempting something in a space
linux-master/arch/parisc/math-emu/fpudispatch.c
715: /* If we get here, something is really wrong! */
1145: /* If we get here, something is really wrong! */
linux-master/arch/powerpc/boot/util.S
25: * with code something like this:
linux-master/arch/powerpc/include/asm/cputhreads.h
70: * architected, is not something a hypervisor could emulate and a future
linux-master/arch/powerpc/include/asm/elf.h
14: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/powerpc/include/asm/exception-64e.h
31: * WARNING: Some of these SPRGs are user readable. We need to do something
120: * fault, not the initial level 0 (basically, we got a bogus PGF or something
linux-master/arch/powerpc/include/asm/head-64.h
51: * CLOSE_FIXED_SECTION() or elsewhere, there may be something
linux-master/arch/powerpc/include/asm/kvm_book3s_64.h
84: * do_something(rmap);
linux-master/arch/powerpc/include/asm/kvm_ppc.h
43: EMULATE_AGAIN, /* something went wrong. go again */
linux-master/arch/powerpc/include/asm/lppaca.h
105: * we will have to transition to something better.
linux-master/arch/powerpc/include/asm/mmu.h
356: * point where I wonder if we should replace it with something different,
linux-master/arch/powerpc/include/asm/page.h
75: * If you want to know something's offset from the start of the kernel you
78: * If you want to test if something's a kernel address, use is_kernel_addr().
linux-master/arch/powerpc/include/asm/word-at-a-time.h
112: * optimal byte mask counting is probably going to be something
linux-master/arch/powerpc/kernel/eeh.c
1031: * the pci_dev's refcount drops to zero so if something is
linux-master/arch/powerpc/kernel/eeh_driver.c
898: * something to recover.
linux-master/arch/powerpc/kernel/eeh_pe.c
209: * callback returns something other than NULL, or no more PEs
linux-master/arch/powerpc/kernel/exceptions-64s.S
2808: * remains off. It is used for recovery when something has corrupted the
linux-master/arch/powerpc/kernel/idle_64e.S
47: /* Interrupts will make use return to LR, so get something we want
linux-master/arch/powerpc/kernel/isa-bridge.c
212: * we should probably do something about it. But do we ever really
linux-master/arch/powerpc/kernel/mce_power.c
748: * to do anything in terms of servicing it. If there is something that
linux-master/arch/powerpc/kernel/pci_64.c
235: * G5 machines... So when something asks for bus 0 io base
linux-master/arch/powerpc/kernel/process.c
196: * there is something wrong if a stopped child appears
1527: * This only prints something if at least one of the TM bit is set.
linux-master/arch/powerpc/kernel/prom_init.c
1753: * Since 768MB is plenty of room, and we need to cap to something
2113: * smp_boot_cpus tells them to do something. The holding pattern
linux-master/arch/powerpc/kernel/prom_init_check.sh
13:# If you really need to reference something from prom_init.o add
linux-master/arch/powerpc/kernel/ptrace/ptrace.c
216: * something else in r3 (via SECCOMP_RET_ERRNO/TRACE).
linux-master/arch/powerpc/kernel/rtasd.c
297: * Next we'll sit and wait for something else to log.
linux-master/arch/powerpc/kernel/security.c
661: * something vaguely sane.
linux-master/arch/powerpc/kernel/setup-common.c
913: /* Set a half-reasonable default so udelay does something sensible */
linux-master/arch/powerpc/kernel/signal_32.c
1036: * we are passed something we understand
1248: the user is really doing something wrong. */
linux-master/arch/powerpc/kernel/swsusp_32.S
216: * be replaced by something more cache efficient */
linux-master/arch/powerpc/kernel/swsusp_85xx.S
117: * be replaced by something more cache efficient */
linux-master/arch/powerpc/kernel/traps.c
1536: * If usermode caused this, it's done something illegal and
2140: * something smarter
linux-master/arch/powerpc/kernel/vector.S
63: * altivec unavailable exception we must set VRSAVE to something non
linux-master/arch/powerpc/kernel/watchdog.c
168: * hard lockup messages being delayed (indefinitely, until something
linux-master/arch/powerpc/kexec/crash.c
58: * offline CPU wakes up due to something like an HMI (malfunction error),
linux-master/arch/powerpc/kexec/ranges.c
294: /* This range means something, only if initrd was retained */
linux-master/arch/powerpc/kvm/book3s_64_entry.S
352: * run the Linux interrupt handler (SRESET or MCE) to print something useful.
linux-master/arch/powerpc/kvm/book3s_64_mmu_hv.c
305: ret = H_RESOURCE; /* or something */
linux-master/arch/powerpc/kvm/book3s_hv.c
258: * is preempted or sleeping, or when the vcpu needs something done
1914: * This occurs if the guest (kernel or userspace), does something that
4363: * wake us up when we need to handle something in the host.
4674: /* Let something else run */
linux-master/arch/powerpc/kvm/book3s_hv_builtin.c
447: /* We found something in the ICP...
linux-master/arch/powerpc/kvm/book3s_hv_interrupts.S
84: * with something that we can't handle in real mode.
linux-master/arch/powerpc/kvm/book3s_hv_rmhandlers.S
333: /* Set HSTATE_DSCR(r13) to something sensible */
1605: * Check whether an HDSI is an HPTE not found fault or something else.
2354: * 1 if something happened that needs to be handled by the host
linux-master/arch/powerpc/kvm/book3s_xics.h
72: /* Real mode might find something too hard, here's the action
linux-master/arch/powerpc/kvm/book3s_xive.c
1534: * Now saved XIRR is "interesting". It means there's something in
2203: * So to properly save the state into something that looks like a
2222: /* Convert saved state into something compatible with xics */
linux-master/arch/powerpc/kvm/mpic.c
502: * try to make it do something sane rather than
linux-master/arch/powerpc/lib/locks.c
36: return; /* something has changed */
62: return; /* something has changed */
linux-master/arch/powerpc/mm/book3s64/hash_utils.c
1581: * hugetlb disabled, something is really wrong.
linux-master/arch/powerpc/mm/book3s64/radix_tlb.c
1193: * if page size is not something we understand, do a full mm flush
linux-master/arch/powerpc/mm/book3s64/slice.c
537: /* Now let's see if we can find something in the existing
584: /* Now let's see if we can find something in the existing slices
linux-master/arch/powerpc/net/bpf_jit_comp.c
140: /* We hit something illegal or unsupported. */
linux-master/arch/powerpc/net/bpf_jit_comp32.c
1373: * The filter contains something cruel & unusual.
linux-master/arch/powerpc/net/bpf_jit_comp64.c
1269: * The filter contains something cruel & unusual.
linux-master/arch/powerpc/perf/core-book3s.c
171: * is something random.
583: * use bit 63 of the event code for something else if they wish.
1894: * An event can only go on a limited PMC if it counts something
2535: return -EBUSY; /* something's already registered */
linux-master/arch/powerpc/perf/core-fsl-emb.c
685: return -EBUSY; /* something's already registered */
linux-master/arch/powerpc/platforms/4xx/pci.c
1942: * that with something akin to kmap_atomic instead. We set aside 1 bus
linux-master/arch/powerpc/platforms/512x/clock-commonclk.c
1111: * but just something to keep in mind when doing compatibility
linux-master/arch/powerpc/platforms/512x/mpc512x_shared.c
313: * in case the boot rom changed something on us.
linux-master/arch/powerpc/platforms/52xx/mpc52xx_gpt.c
261: * already in use for something. */
linux-master/arch/powerpc/platforms/83xx/misc.c
90: * in case the boot rom changed something on us.
linux-master/arch/powerpc/platforms/cell/iommu.c
531: * node's iommu. We -might- do something smarter later though it may
linux-master/arch/powerpc/platforms/cell/spu_base.c
93:/* The hack below stinks... try to do something better one of
246: * assume that the mappings are smaller that one segment - if not, something
linux-master/arch/powerpc/platforms/cell/spufs/file.c
695: * read something.
828: * write something.
linux-master/arch/powerpc/platforms/powermac/low_i2c.c
1184: * something special about those later.
linux-master/arch/powerpc/platforms/powermac/pci.c
891: * safe assumptions for now. We should do something better in the
linux-master/arch/powerpc/platforms/powermac/smp.c
210: * force the data bus to change to something else, and we read it again.
823: * instead wait for the entry code to set something for me. Well,
linux-master/arch/powerpc/platforms/powernv/eeh-powernv.c
1107: * poorly designed or something...
linux-master/arch/powerpc/platforms/powernv/opal-fadump.c
413: * saved by the kernel in the PT_NOTE, to have something to work with in
linux-master/arch/powerpc/platforms/powernv/opal-irqchip.c
5: * that Linux needs to do something about. These basically look like
linux-master/arch/powerpc/platforms/powernv/pci-ioda.c
1012: * If we can't setup the IODA PE something has gone horribly
1681: * Returns true iff chip is something that we could call
linux-master/arch/powerpc/platforms/ps3/spu.c
367: /* need something better here!!! */
linux-master/arch/powerpc/platforms/pseries/io_event_irq.c
76: * we do get called for another type then something went wrong so
linux-master/arch/powerpc/platforms/pseries/papr-vpd.c
395: * should be a transient condition, not something that happens
linux-master/arch/powerpc/sysdev/cpm2.c
106: * The baud rate clock is the system clock divided by something.
linux-master/arch/powerpc/sysdev/cpm2_pic.c
255: * in case the boot rom changed something on us.
linux-master/arch/powerpc/sysdev/mpic.c
1152: * as their bit 1 means something else.
1868: /* make sure we're sending something that translates to an IPI */
linux-master/arch/powerpc/sysdev/xive/common.c
166: /* Found something ? That's it */
351: * as a "replay" because EOI decided there was still something
linux-master/arch/riscv/include/asm/clint.h
20: * memory layout). Thus, this is called "clint_time_val" instead of something
linux-master/arch/riscv/include/asm/elf.h
35: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/riscv/kernel/acpi.c
285: * that memory and use it for something else. We never
linux-master/arch/riscv/kernel/probes/uprobes.c
184: * architecture needs to do something different it can define
linux-master/arch/riscv/kernel/traps_misaligned.c
545: * when hotplugging the new cpu, this is something we don't handle.
linux-master/arch/riscv/kernel/vdso/hwprobe.c
34: /* This is something we can handle, fill out the pairs. */
linux-master/arch/s390/include/asm/elf.h
176: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/s390/include/asm/hugetlb.h
27: * If the arch doesn't supply something else, assume that hugepage
linux-master/arch/s390/include/asm/pgtable.h
1223: * If something went wrong and the page could not be destroyed, or
linux-master/arch/s390/include/asm/uv.h
437: * not page aligned, we assume something went wrong. If
linux-master/arch/s390/kernel/debug.c
339: /* has something changed in the meantime ? */
linux-master/arch/s390/kernel/dumpstack.c
117: * If it comes up a second time then there's something wrong going on:
linux-master/arch/s390/kvm/interrupt.c
2268: * so we need to use something else for this case
linux-master/arch/s390/kvm/pv.c
79: /* Intended memory leak for something that should never happen. */
linux-master/arch/s390/kvm/vsie.c
1056: * Either everything went well, or something non-critical went wrong
linux-master/arch/s390/mm/fault.c
507: * When this happens, userspace did something that it
linux-master/arch/sh/drivers/dma/dma-g2.c
129: * bit 2 - ??? something to do with suspend?
linux-master/arch/sh/drivers/pci/ops-dreamcast.c
32: * something to take into consideration. However, due to the cost of the BBA,
linux-master/arch/sh/include/asm/cmpxchg.h
52: * if something tries to do an invalid cmpxchg(). */
linux-master/arch/sh/include/asm/elf.h
94: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/sh/include/asm/hugetlb.h
9: * If the arch doesn't supply something else, assume that hugepage
linux-master/arch/sh/include/asm/watchdog.h
38: * something a little more reasonable, and really can't deal with anything
linux-master/arch/sh/kernel/cpu/sh3/entry.S
479: * We got here as a result of taking the INTEVT path for something
linux-master/arch/sh/kernel/cpu/sh4/probe.c
221: * Verify that it really has something hooked up, this
linux-master/arch/sh/kernel/cpu/sh4a/setup-shx3.c
24: * As this overlap is something that never should have made it in to
linux-master/arch/sh/kernel/perf_event.c
44: * Stub these out for now, do something more profound later.
linux-master/arch/sh/kernel/traps_32.c
529: /* bad PC is not something we can fix */
linux-master/arch/sparc/include/asm/backoff.h
25: * condition code register. Each read blocks the strand for something
linux-master/arch/sparc/include/asm/cmpxchg_64.h
153: if something tries to do an invalid cmpxchg(). */
linux-master/arch/sparc/include/asm/elf_32.h
97: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/sparc/include/asm/elf_64.h
177: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/sparc/include/asm/machines.h
38: * something if the value in the ARCH field is SM_SUN4M, if it is
linux-master/arch/sparc/include/asm/parport_64.h
20: * While sparc64 doesn't have an ISA DMA API, we provide something that looks
linux-master/arch/sparc/include/asm/pgtable_32.h
263: /* Just return something that will cause
linux-master/arch/sparc/include/asm/smp_32.h
114: * contains something other than one of these then the ipi is from
linux-master/arch/sparc/include/asm/tsb.h
11: * TLB miss trap handler software does the actual lookup via something
linux-master/arch/sparc/include/asm/uaccess_64.h
23: * doing something queer and tricking us into poking kernel memory.
linux-master/arch/sparc/kernel/head_32.S
546: * But first make current_set[boot_cpu_id] point to something useful.
linux-master/arch/sparc/kernel/ioport.c
11: * <rth> zait: as long as pci_alloc_consistent produces something addressable,
linux-master/arch/sparc/kernel/kprobes.c
425: * Sequences usually look something like this
linux-master/arch/sparc/kernel/sun4d_irq.c
361: * lacks a "board#" property, something is very wrong.
linux-master/arch/sparc/kernel/sun4v_tlb_miss.S
29: /* Create TSB pointer. This is something like:
linux-master/arch/sparc/kernel/traps_64.c
1076: * something palatable to the memory controller driver get_unumber
linux-master/arch/sparc/lib/checksum_32.S
353:ccte: bne cc_end_cruft ! something left, handle it out of band
linux-master/arch/sparc/mm/srmmu.c
1446: /* Just in case PROM does something funny. */
linux-master/arch/sparc/net/bpf_jit_comp_32.c
354: /* no prologue/epilogue for trivial filters (RET something) */
linux-master/arch/sparc/net/bpf_jit_comp_64.c
543: /* We may be able to do something quick
linux-master/arch/sparc/vdso/vdso2c.c
11: * If we ever need to do something fancier than what objcopy provides,
linux-master/arch/um/drivers/virtio_uml.c
652: * shared memory file, or write something there that we can never
667: * something that you typically encounter with virtio drivers, so
linux-master/arch/um/kernel/irq.c
383: * that would cause a pointless shutdown hang if something hadn't
linux-master/arch/um/kernel/um_arch.c
168:" devices and want to boot off something other than ubd0, you \n"
169:" would use something like:\n"
504: * up on something we actually want to wake up on. All
linux-master/arch/um/os-Linux/execvp.c
117: something went wrong executing it; return the error to our
linux-master/arch/um/os-Linux/mem.c
65: * Choose the tempdir to use. We want something on tmpfs so that our memory is
linux-master/arch/um/os-Linux/umid.c
130: * something other than UML sticking stuff in the directory
linux-master/arch/um/os-Linux/util.c
148: * it's something else. Tell os_kill_ptraced_process not to
linux-master/arch/x86/Kconfig
814: spinlock implementation with something virtualization-friendly
linux-master/arch/x86/boot/cpucheck.c
140: get_cpuflags(); /* Make sure it really did something */
linux-master/arch/x86/boot/header.S
249: # in case something decided to "use" it
linux-master/arch/x86/coco/tdx/tdx-shared.c
83: * mechanism itself and that something has gone horribly wrong with
linux-master/arch/x86/entry/common.c
332: * Subtlety here: if ptrace pokes something larger than 2^31-1 into
linux-master/arch/x86/entry/vdso/vdso2c.c
11: * If we ever need to do something fancier than what objcopy provides,
linux-master/arch/x86/entry/vdso/vsgx.S
65: /* EEXIT jumps here unless the enclave is doing something fancy. */
linux-master/arch/x86/include/asm/desc.h
336: * If you do something evil that corrupts the cached TSS limit (I'm looking
linux-master/arch/x86/include/asm/elf.h
86: * This is used to ensure we don't load something for the wrong architecture.
147: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/x86/include/asm/hw_breakpoint.h
10: * The name should probably be something dealt in
linux-master/arch/x86/include/asm/io.h
171: * The default ioremap() behavior is non-cached; if you need something
linux-master/arch/x86/include/asm/irq.h
17: * something moves a C function into the __irq_entry section.
linux-master/arch/x86/include/asm/kvm_para.h
25: * instruction. The hypervisor may replace it with something else but only the
linux-master/arch/x86/include/asm/segment.h
299: * Load a segment. Fall back on loading the zero segment if something goes
linux-master/arch/x86/include/asm/uaccess.h
74: * the base register for something that ends up being a pair.
linux-master/arch/x86/include/asm/vdso/gettimeofday.h
32: * If we ever reintroduce something like direct access to an MMIO clock like
linux-master/arch/x86/include/asm/word-at-a-time.h
10: * optimal byte mask counting is probably going to be something
linux-master/arch/x86/include/asm/xor_32.h
242: Clobber them just to be sure nobody does something stupid
515: Clobber them just to be sure nobody does something stupid
linux-master/arch/x86/kernel/acpi/wakeup_64.S
85: /* in case something went wrong, restore the machine status and go on */
linux-master/arch/x86/kernel/alternative.c
1663: * MCEs only happen when something got corrupted and in this
1664: * case we must do something about the corruption.
1869: * If something went wrong, crash and burn since recovery paths are not
1937: * If the text does not match what we just wrote then something is
linux-master/arch/x86/kernel/apm_32.c
1336: * sending a SUSPEND event until something else
2221: * In short, if something bad happens, at least we have a choice
linux-master/arch/x86/kernel/cpu/aperfmperf.c
73: * (freq_curr/freq_max would rarely reach 1) and something close to freq_base,
linux-master/arch/x86/kernel/cpu/mce/core.c
1434: * something got corrupted coming in through int 18.
1563: * something new. Check again to see if we found a
linux-master/arch/x86/kernel/cpu/mce/severity.c
84: /* When MCIP is not set something is very confused */
linux-master/arch/x86/kernel/dumpstack.c
439: * This is gone through when something in the kernel has done something bad
linux-master/arch/x86/kernel/dumpstack_32.c
139: * If it comes up a second time then there's something wrong going on:
linux-master/arch/x86/kernel/dumpstack_64.c
204: * If it comes up a second time then there's something wrong going on:
linux-master/arch/x86/kernel/e820.c
235: * number of valid entries (something no more than max_nr_entries).
linux-master/arch/x86/kernel/fpu/context.h
22: * Invalidate a resource you control: CPU if using the CPU for something else
linux-master/arch/x86/kernel/fpu/init.c
170: * see if something got added to the end.
linux-master/arch/x86/kernel/fpu/xstate.c
717: * We enabled the XSAVE hardware, but something went wrong and
782: * This indicates that something really unexpected happened
873: * Paranoia check whether something in the setup modified the
897: /* something went wrong, try to boot without any XSAVE support */
linux-master/arch/x86/kernel/fred.c
14: * #DF is the highest level because a #DF means "something went wrong
linux-master/arch/x86/kernel/i8259.c
172: * is something bad going on ...
linux-master/arch/x86/kernel/jump_label.c
68: * Something went wrong. Crash the box, as something could be
linux-master/arch/x86/kernel/setup.c
541: /* Assume no if something weird is going on with PCI */
linux-master/arch/x86/kernel/traps.c
460: * something else.
600: * If so, the #GP must be from something else.
962: * If something gets miswired and we end up here for a user mode
1004: * So if we get here with DR_STEP set, something is wonky.
1023: * If something gets miswired and we end up here for a kernel mode
linux-master/arch/x86/kvm/cpuid.c
1419: * userspace in case we want to use it for something in the future.
linux-master/arch/x86/kvm/hyperv.c
2067: * while also expecting us to flush something and crashing if
linux-master/arch/x86/kvm/kvm_onhyperv.h
16: * Partition assist page is something which Hyper-V running in L0
linux-master/arch/x86/kvm/mmu/mmu.c
2829: * before the page had been marked as unsync-ed, something like the
5921: * explicitly shadowing L1's page tables, i.e. unprotecting something
linux-master/arch/x86/kvm/pmu.c
505: * The reprogramming bitmap can be written asynchronously by something
linux-master/arch/x86/kvm/vmx/nested.c
4809: * do that when something is forcing L2->L1 exit prior to
linux-master/arch/x86/kvm/vmx/vmx.c
6442: * If KVM is dumping the VMCS, then something has gone wrong
6491: * PML full exit occurs as something is horribly wrong.
linux-master/arch/x86/kvm/x86.c
1861: * value, and that something deterministic happens if the guest
9740: * the PAT bits in SPTEs. Bail if PAT[0] is programmed to something
12995: * other flag is LOG_DIRTY_PAGES, i.e. something is wrong if dirty
linux-master/arch/x86/lib/retpoline.S
374: * 'JMP __x86_return_thunk' sites are changed to something else by
linux-master/arch/x86/math-emu/reg_ld_str.c
782: /* Produce something like QNaN "indefinite" */
829: /* Produce something like QNaN "indefinite" */
875: /* Produce something like QNaN "indefinite" */
linux-master/arch/x86/mm/kmmio.c
253: * per cpu, so ensure that we finish it before something else
342: * something external causing them (f.e. using a debugger while
linux-master/arch/x86/mm/numa_emulation.c
44: * something went wrong, 0 otherwise.
linux-master/arch/x86/mm/pat/set_memory.c
1896: * Check whether we really changed something:
linux-master/arch/x86/mm/pti.c
152: * EFI runtime mapping or something similar, and the kernel
linux-master/arch/x86/mm/tlb.c
185: * We get here when we do something requiring a TLB invalidation
521: * does something like write_cr3(read_cr3_pa()).
536: * Architecturally, the CPU could prefetch something
linux-master/arch/x86/pci/fixup.c
511: * ID, but the PM register 0x55 does something different
linux-master/arch/x86/pci/mmconfig-shared.c
810: * pci_mmconfig_lookup() finds something
linux-master/arch/x86/realmode/rm/reboot.S
84: * something else should be done for other chips.
linux-master/arch/x86/um/asm/elf.h
27: * This is used to ensure we don't load something for the wrong architecture.
122: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/x86/um/asm/required-features.h
5: * Nothing to see, just need something for the i386 and x86_64 asm
linux-master/arch/x86/xen/mmu_pv.c
1027: /* In case we did something silly, we should crash in this function
linux-master/arch/x86/xen/multicalls.c
67: something in the middle */
linux-master/arch/x86/xen/smp_pv.c
389: /* make sure we're not pinning something down */
linux-master/arch/xtensa/include/asm/cmpxchg.h
69: * if something tries to do an invalid cmpxchg(). */
linux-master/arch/xtensa/include/asm/elf.h
90: * This is used to ensure we don't load something for the wrong architecture.
linux-master/arch/xtensa/platforms/xtfpga/Makefile
6:# unless it's something special (ie not a .c file).
linux-master/arch/xtensa/variants/csp/include/variant/tie.h
99: * registers used by the compiler, you can do something like this:
linux-master/arch/xtensa/variants/dc232b/include/variant/tie.h
80: * registers used by the compiler, you can do something like this:
linux-master/arch/xtensa/variants/dc233c/include/variant/tie.h
99: * registers used by the compiler, you can do something like this:
linux-master/arch/xtensa/variants/de212/include/variant/tie.h
76: * registers used by the compiler, you can do something like this:
linux-master/arch/xtensa/variants/test_kc705_be/include/variant/tie.h
102: * registers used by the compiler, you can do something like this:
linux-master/arch/xtensa/variants/test_kc705_hifi/include/variant/tie.h
102: * registers used by the compiler, you can do something like this:
linux-master/arch/xtensa/variants/test_mmuhifi_c3/include/variant/tie.h
79: * registers used by the compiler, you can do something like this:
linux-master/block/bfq-iosched.c
6076: * something we should do about it.
6986: * whether bfqq is in service before doing something on it. If
7097: * (1U<<(bt->sb.shift - something)), to be robust against
7099: * limit 'something'.
linux-master/block/blk-cgroup.c
1911: * delay, and we want userspace to be able to do _something_ so cap the
linux-master/block/blk-iocost.c
1636: /* did something get issued this period? */
1641: /* is something in flight? */
linux-master/block/blk-map.c
341: /* couldn't stuff something into bio? */
linux-master/block/blk-mq.c
967: * size, something has gone terribly wrong.
linux-master/block/blk-timeout.c
161: * will be X + something.
linux-master/block/blk-wbt.c
4: * packets for IO scheduling, so the logic is something like this:
linux-master/block/blk-zoned.c
1416: * We failed to get the zone information, meaning that something
linux-master/block/early-lookup.c
240: * block_class is used to check if something is a disk name. If the disk
linux-master/crypto/Kconfig
382: are evicted when the CPU is interrupted to do something else.
linux-master/crypto/aes_ti.c
27: * evicted when the CPU is interrupted to do something else.
43: * evicted when the CPU is interrupted to do something else.
linux-master/crypto/algif_aead.c
124: * information to the data sender that something is wrong, but they are
linux-master/crypto/ansi_cprng.c
79: * returns 0 if generation succeeded, <0 if something went wrong
linux-master/crypto/asymmetric_keys/asymmetric_type.c
389: /* put something here to indicate the key's capabilities */
linux-master/crypto/asymmetric_keys/verify_pefile.c
120: * remnant looks something like PKCS#7.
linux-master/crypto/deflate.c
16: * The default winbits of 11 should suit most packets, and it may be something
linux-master/crypto/jitterentropy-kcapi.c
123: * The main reason for this loop is to execute something over which we
linux-master/crypto/skcipher.c
851: * Make sure we do not allocate something that might get used with
linux-master/drivers/accel/habanalabs/common/device.c
1789: "%s kernel ctx was alive during hard reset, something is terribly wrong\n",
linux-master/drivers/accel/habanalabs/common/firmware_if.c
1475: /* If we read all FF, then something is totally wrong, no point
linux-master/drivers/accel/habanalabs/common/memory.c
2769: * Clearly something went wrong on hard reset so no point in printing
linux-master/drivers/accel/qaic/qaic_data.c
1412: * the same thing - the queue has something to process.
linux-master/drivers/accessibility/speakup/buffers.c
80: /* We have written something to the speech synthesis, so we are not
linux-master/drivers/acpi/acpi_pnp.c
306: {"GIM0100"}, /* Guillemot Turtlebeach something appears to be cs4232 compatible */
linux-master/drivers/acpi/acpica/exnames.c
168: * so we are looking at something other than a name.
linux-master/drivers/acpi/acpica/exoparg3.c
92: * AML interpreters never see the opcode. Thus, something is
linux-master/drivers/acpi/acpica/exsystem.c
174: * accidental deep sleeps, limit the sleep time to something reasonable.
linux-master/drivers/acpi/acpica/nsaccess.c
72: * This namespace looks like something similar to this:
linux-master/drivers/acpi/acpica/nsxfeval.c
465: * last resort effort to return something useful. Also, provides compatibility
linux-master/drivers/acpi/acpica/psobject.c
593: * There was something that went wrong while executing code at the
linux-master/drivers/acpi/acpica/utstring.c
158: * Replace a bad character with something printable, yet technically
linux-master/drivers/acpi/apei/erst.c
873: * else if return value < 0, something goes wrong,
linux-master/drivers/acpi/dock.c
357: * if we are in the middle of doing something.
linux-master/drivers/acpi/osl.c
1423: * get a system message that something might go wrong...
linux-master/drivers/acpi/processor_idle.c
545: * Dummy wait op - must do something useless after P_LVL2 read
linux-master/drivers/ata/ata_piix.c
1001: * cycles and power trying to do something to the sleeping
linux-master/drivers/ata/libahci_platform.c
547: * Too many sub-nodes most likely means having something wrong with
linux-master/drivers/ata/libata-core.c
4749: * in case something prevents using it.
linux-master/drivers/ata/libata-pmp.c
721: /* something weird is going on, request full PMP recovery */
linux-master/drivers/ata/libata-sff.c
962: * when it finds something wrong.
1016: * when it finds something wrong.
1235: * or something. Snooze for a couple msecs, then
linux-master/drivers/ata/pata_amd.c
299: /* be optimistic, EH can take care of things if something goes wrong */
linux-master/drivers/ata/pata_macio.c
257: * to calculate / snoop timing values for something else than the
linux-master/drivers/ata/sata_inic162x.c
20: * This controller is eccentric and easily locks up if something isn't
linux-master/drivers/ata/sata_mv.c
2547: * If it did, then something is wrong elsewhere,
2559: * If it did not, then something is wrong elsewhere,
2815: * even if something we call of our routines changes it.
linux-master/drivers/ata/sata_nv.c
1074: something even though we are only clearing on one */
linux-master/drivers/atm/fore200e.c
2372: /* the i960 monitor doesn't accept any new character if it has something to say */
linux-master/drivers/atm/iphase.c
1222: /* do something */
1548: space or something similar.
2239: /* do something */
2251: /* do something */
linux-master/drivers/atm/lanai.c
325: * if we can't allocate that we'll settle for something smaller
linux-master/drivers/atm/midway.h
85:#define MID_SERVICE 0x00000004 /* something in service list */
linux-master/drivers/auxdisplay/arm-charlcd.c
254: /* Put something useful in the display */
linux-master/drivers/base/attribute_container.c
197: * simply done via device_unregister (note that if something
linux-master/drivers/base/cpu.c
321: * something as foolish as this. However, at this point in time, it is
linux-master/drivers/base/swnode.c
447: /* Guess something if prefix was NULL. */
linux-master/drivers/block/drbd/drbd_actlog.c
699: * something outside the resync lru_cache in sync.
1047: * if the next requested one is something else, we do
linux-master/drivers/block/drbd/drbd_int.h
381: /* has this been submitted, or does it still wait for something else? */
linux-master/drivers/block/drbd/drbd_main.c
3207: * something goes wrong.
linux-master/drivers/block/drbd/drbd_receiver.c
1395: * something to count pending connection packets in. */
2882: then we would do something smarter here than reading
3079: /* Well, then use something else. */
3780: * ERR_PTR(error) if something goes wrong
6022: /* If the data socket received something meanwhile,
linux-master/drivers/block/drbd/drbd_req.c
665: /* assert something? */
725: /* assert something? */
1576: * we already have something to commit.
1758: /* do we have something to evaluate? */
linux-master/drivers/block/drbd/drbd_state.c
1953: /* In case we want to get something to stable storage still,
linux-master/drivers/block/floppy.c
419: * 'stretch' should probably be renamed to something more general, like
linux-master/drivers/block/loop.c
1242: * <dev>/do something like mkfs/losetup -d <dev> causing the losetup -d
linux-master/drivers/block/nbd.c
668: * however if we have sent something we need to make
769:/* NULL returned = something went wrong, inform userspace */
linux-master/drivers/block/pktcdvd.c
1428: * Wait until there is something to do
linux-master/drivers/block/rbd.c
1941: * This function needs snap_id (or more precisely just something to
5344: * doing something similar to dm (dm-builtin.c) is overkill.
linux-master/drivers/block/rnbd/rnbd-clt.c
240: * always return the first CPU with something on the queue list when the
241: * value stored on the var is greater than the last CPU with something
660: * if something goes wrong (failing of outstanding requests
linux-master/drivers/block/ublk_drv.c
1691: /* there is pending io cmd, something must be wrong */
linux-master/drivers/block/xen-blkfront.c
1082: /* this is above the extended range; something is wrong */
linux-master/drivers/block/zram/zcomp.c
128: * is not something that ZRAM wants to see. We can handle the
linux-master/drivers/bluetooth/btintel.c
1926: * since something went wrong.
linux-master/drivers/bluetooth/hci_intel.c
813: * since something went wrong.
linux-master/drivers/bluetooth/hci_ldisc.c
521: * Called when the line discipline is changed to something
linux-master/drivers/bus/intel-ixp4xx-eb.c
189: * something is explicitly defined.
linux-master/drivers/bus/qcom-ebi2.c
88: * this is something just used on the FAST chip selects. There is also a "byte
linux-master/drivers/cdrom/gdrom.c
424: /* even if something is pending try to get
linux-master/drivers/char/Kconfig
183: time with "insmod button reboot_count=<something>".
linux-master/drivers/char/agp/isoch.c
444: dev_info(&td->dev, "something bad happened setting "
linux-master/drivers/char/dsp56k.c
17: * Hmm... there must be something here :)
linux-master/drivers/char/hangcheck-timer.c
125: tsc_diff = (cur_tsc + (~0ULL - hangcheck_tsc)); /* or something */
linux-master/drivers/char/ipmi/ipmi_devintf.c
210: users getting something from the queue at a time.
213: user will grab something from the queue, too. Then
214: the messages might get out of order if something
linux-master/drivers/char/ipmi/ipmi_msghandler.c
568: * If we are doing maintenance on something on IPMB, extend
3499: /* In case something came in */
linux-master/drivers/char/ipmi/ipmi_si_intf.c
630: * lock and something else can mess with the
668: * lock and something else can mess with the
760: * we just run until the state machine tells us something
801: * We got an ATTN, but we are doing something else.
941: * looking for something and not delaying between checks
990: * If the driver is doing something, there is a possible
992: * and the thread here sees something else, the timer
linux-master/drivers/char/ipmi/ipmi_ssif.c
481: /* Wait for something to do */
linux-master/drivers/char/mem.c
207: /* Hmm. Do something? */
linux-master/drivers/char/virtio_console.c
633: * console driver writes something out.
linux-master/drivers/char/xillybus/xillybus_core.c
1034: * an error, just something to dismiss.
linux-master/drivers/clk/bcm/clk-iproc-armpll.c
77: /* something is seriously wrong */
linux-master/drivers/clk/bcm/clk-kona-setup.c
408: * where we need something from the ccu, so we do these
linux-master/drivers/clk/clk.c
136: * prepare_lock for something like clk_prepare_enable() while
961: * if there is something wrong with this consumer protect count, stop
3885: * 'req_rate' is set to something non-zero so that
linux-master/drivers/clk/clk_test.c
117: * requested rate. If we get something lower, it thus considers
linux-master/drivers/clk/meson/clk-regmap.c
69: /* Gives a hint that something is wrong */
linux-master/drivers/clk/sunxi/clk-a20-gmac.c
32: * This clock looks something like this
linux-master/drivers/clk/sunxi/clk-sunxi.c
935: * These clocks look something like this
linux-master/drivers/clk/sunxi-ng/ccu-sun50i-a64.c
161: * The output function can be changed to something more complex that
linux-master/drivers/clocksource/timer-atmel-tcb.c
434: /* How fast will we be counting? Pick something over 5 MHz. */
linux-master/drivers/clocksource/timer-clint.c
223: * will die in favor of something cleaner.
linux-master/drivers/comedi/drivers/amplc_pci230.c
2114: * start conversion source to point to something at a high logic
linux-master/drivers/comedi/drivers/daqboard2000.c
28: * pinouts, plug and pray has something to catch up with yet).
42: * guess that it has something to do with pacer clocks, but the source
linux-master/drivers/comedi/drivers/ni_660x.c
897: /* cannot disconnect something not connected */
linux-master/drivers/comedi/drivers/ni_mio_common.c
2960: * add something like ".has_individual_dacs = 0" to ni_board_struct
3763: /* XXX just guessing this is needed and does something useful */
5810: /* cannot disconnect something not connected */
linux-master/drivers/comedi/drivers/ni_routing/ni_route_values/ni_660x.c
23: * these routes, rather one might indicate that something is used as the source
linux-master/drivers/comedi/drivers/ni_routing/ni_route_values/ni_eseries.c
23: * these routes, rather one might indicate that something is used as the source
linux-master/drivers/comedi/drivers/ni_routing/ni_route_values/ni_mseries.c
23: * these routes, rather one might indicate that something is used as the source
linux-master/drivers/comedi/drivers/ni_routing/ni_route_values.c
23: * explicitly make these routes, rather one might indicate that something is
linux-master/drivers/comedi/drivers/ni_routing/ni_route_values.h
29: * explicitly make these routes, rather one might indicate that something is
linux-master/drivers/comedi/drivers/ni_routing/tools/convert_csv_to_c.py
319: * explicitly make these routes, rather one might indicate that something is
393: * these routes, rather one might indicate that something is used as the source
linux-master/drivers/cpufreq/acpi-cpufreq.c
883: * writing something to the appropriate registers.
linux-master/drivers/cpufreq/e_powersaver.c
308: /* Change mV to something hardware can use */
linux-master/drivers/cpufreq/longhaul.c
192: /* Dummy op - must do something useless after P_LVL3
210: /* Dummy op - must do something useless after P_LVL3 read */
229: /* Dummy op - must do something useless after P_LVL3
680:/* VIA don't support PM2 reg, but have something similar */
linux-master/drivers/cpufreq/powernow-k7.c
141: /* Check we can actually do something before we say anything.*/
linux-master/drivers/crypto/caam/ctrl.c
323: * something went wrong. No need to try the next state
linux-master/drivers/crypto/ccp/ccp-dmaengine.c
606: /* If there was something active, re-start */
linux-master/drivers/crypto/ccp/sev-dev.c
956: * failure in case the caller wants to glean something from the error.
linux-master/drivers/crypto/inside-secure/safexcel.c
928: * something wrong with the input!
linux-master/drivers/cxl/core/port.c
1595: * something to the caller, so translate it.
linux-master/drivers/dma/amba-pl08x.c
2519: /* Trying to get a slave channel from something with no slave support */
linux-master/drivers/dma/at_hdmac.c
1631: * This is only called when something went wrong elsewhere, so
linux-master/drivers/dma/dw/core.c
318: * Otherwise something is really wrong.
linux-master/drivers/dma/fsl_raid.c
216: * need to do something more than just crashing
linux-master/drivers/dma/ioat/dca.c
13:/* either a kernel change is needed, or we need something like this in kernel */
linux-master/drivers/dma/ppc4xx/adma.c
730: /* If previous next is overwritten something is wrong.
1120: /* is there something new to append */
linux-master/drivers/dma/ptdma/ptdma-dmaengine.c
295: /* If there was something active, re-start */
linux-master/drivers/dma/ste_dma40.c
1699: * No error because this can happen if something else
linux-master/drivers/dma/sun4i-dma.c
352: "processing something to this endpoint already\n");
1070: * - There's always something we can dispatch
1116: * If a pchan was freed, we may be able to schedule something else,
linux-master/drivers/dma/ti/k3-udma.c
3770: /* If we have something pending and no active descriptor, then */
linux-master/drivers/edac/i5000_edac.c
508: * specified middle point. Since this is something the BIOS
linux-master/drivers/edac/i5400_edac.c
176: * Names to translate bit error into something useful
linux-master/drivers/edac/i7core_edac.c
1000: * This is something undocumented, based on my tests
linux-master/drivers/eisa/Kconfig
47:# Using EISA_VIRTUAL_ROOT on something other than an X86 may lead
linux-master/drivers/eisa/eisa-bus.c
264: * id, now we can display something in /proc/ioports.
linux-master/drivers/firewire/sbp2.c
1367: * If the orb completes with status == NULL, something
1455: /* Initialize rcode to something not RCODE_COMPLETE. */
1542: * Called by scsi stack when something has really gone wrong. Usually
linux-master/drivers/firmware/arm_scmi/raw_mode.c
1350: * if this is not happening something is seriously broken and
linux-master/drivers/firmware/arm_scmi/virtio.c
649: * this means that it is possible to poll the virtqueues waiting for something
654: * As a consequence it can happen to dequeue something different from the buffer
659: * So, basically, once something new is spotted we proceed to de-queue all the
770: * When the polling loop has successfully terminated if something
linux-master/drivers/firmware/efi/dev-path-parser.c
129: * // do something with dev
linux-master/drivers/fpga/zynq-fpga.c
218: * control back to zynq_fpga_ops_write, something went wrong,
442: * something went wrong we are relying on the hardware to have halted
linux-master/drivers/fsi/fsi-master-gpio.c
331: * for other situations. It will be converted to something else
linux-master/drivers/fsi/fsi-sbefifo.c
506: /* As long as there's something to send */
linux-master/drivers/gpio/gpio-thunderx.c
501: * If something has already programmed the pin, use
linux-master/drivers/gpio/gpio-winbond.c
505: pr_warn("GPIO1 pins were connected to something else (%.2x), fixing\n",
linux-master/drivers/gpio/gpiolib-of.c
635: * we allow looking something up that is not named "foo-gpios".
linux-master/drivers/gpio/gpiolib.c
1391: /* Just pick something */
1557: * really need something other than 1:1 translation for translate()
3646: * If it's fast: flush the direction setting if something changed
linux-master/drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
893: /* version, increment each time something is added */
linux-master/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
3116: * after all of the have been initialized or something that needs to happen
linux-master/drivers/gpu/drm/amd/amdgpu/amdgpu_display.c
1527: /* No: Fake something reasonable which gives at least ok results. */
linux-master/drivers/gpu/drm/amd/amdgpu/amdgpu_ras_eeprom.c
127: * offset off of RAS_TABLE_START. That is, this is something you can
linux-master/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
1224: * but in case of something, we filter the flags in first place
linux-master/drivers/gpu/drm/amd/amdgpu/amdgpu_vm_pt.c
936: /* We need all PDs and PTs for mapping something, */
940: /* but unmapping something can happen at a higher
linux-master/drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c
522: /* Assign the pt base to something valid for now; the pts used for
linux-master/drivers/gpu/drm/amd/amdgpu/si.c
1725: /* Start off with something large */
linux-master/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c
1004: /* TODO: something */
linux-master/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_irq.c
37: * already provides. This is something that could be cleaned up, and is a
linux-master/drivers/gpu/drm/amd/display/dc/basics/dce_calcs.c
39: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/core/dc.c
4439: * Return false if something is wrong in the transition state.
linux-master/drivers/gpu/drm/amd/display/dc/dce/dce_stream_encoder.c
91: * something wrong. clear GPS memory access and notify?
linux-master/drivers/gpu/drm/amd/display/dc/dcn10/dcn10_stream_encoder.c
84: * something wrong. clear GPS memory access and notify?
813: * something wrong. clear GPS memory access and notify?
linux-master/drivers/gpu/drm/amd/display/dc/dcn30/dcn30_vpg.c
76: * something wrong. clear GPS memory access and notify?
linux-master/drivers/gpu/drm/amd/display/dc/dml/calcs/dcn_calc_auto.c
35: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/dml/calcs/dcn_calc_math.c
36: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/dml/calcs/dcn_calcs.c
53: * ways. Unless there is something clearly wrong with it the code should
159: .dcfclk_cstate_latency = 10 /*TODO clone of something else? sr_enter_plus_exit_time?*/
linux-master/drivers/gpu/drm/amd/display/dc/dml/dcn20/display_mode_vba_20.c
35: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/dml/dcn20/display_mode_vba_20v2.c
35: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/dml/dcn20/display_rq_dlg_calc_20.c
61: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/dml/dcn20/display_rq_dlg_calc_20v2.c
61: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/dml/dcn21/display_mode_vba_21.c
38: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/dml/dcn21/display_rq_dlg_calc_21.c
37: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/dml/dcn30/dcn30_fpu.c
718: * something is severely wrong.
linux-master/drivers/gpu/drm/amd/display/dc/dml/dcn30/display_mode_vba_30.c
37: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/dml/dcn31/display_mode_vba_31.c
37: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/dml/dcn314/display_mode_vba_314.c
40: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/dml/dcn32/dcn32_fpu.c
311: * something is severely wrong.
linux-master/drivers/gpu/drm/amd/display/dc/dml/dcn32/display_mode_vba_util_32.c
1227: // FIXME check ODMUse == "" condition does it mean bypass or Gabriel means something like don't care??
linux-master/drivers/gpu/drm/amd/display/dc/dml/display_mode_structs.h
178: * these values from VBIOS; if something goes wrong, we use some hard-coded
linux-master/drivers/gpu/drm/amd/display/dc/dml/display_mode_vba.c
36: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/dml/dml1_display_rq_dlg_calc.c
36: * ways. Unless there is something clearly wrong with it the code should
linux-master/drivers/gpu/drm/amd/display/dc/link/link_detection.c
632: * something is terribly wrong if time out is > 200ms. (5Hz)
linux-master/drivers/gpu/drm/amd/display/dc/link/link_factory.c
270: * responsibility to link service or something doesn't belong to link
linux-master/drivers/gpu/drm/amd/display/include/link_service_types.h
240: * state calculations in DM, or you will break something.
linux-master/drivers/gpu/drm/amd/pm/swsmu/smu11/sienna_cichlid_ppt.c
3882: /* XXX ideally this would be something in a vbios data table */
linux-master/drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0_0_ppt.c
2717: /* XXX ideally this would be something in a vbios data table */
linux-master/drivers/gpu/drm/amd/pm/swsmu/smu14/smu_v14_0_2_ppt.c
1579: /* XXX ideally this would be something in a vbios data table */
linux-master/drivers/gpu/drm/armada/armada_crtc.c
214: * something we don't support.
linux-master/drivers/gpu/drm/armada/armada_gem.c
110: * We could grab something from DMA if it's enabled, but that
linux-master/drivers/gpu/drm/bridge/parade-ps8622.c
401: * This doesn't matter if the regulators are turned off, but something
linux-master/drivers/gpu/drm/bridge/parade-ps8640.c
165: * Apparently something about the firmware in the chip signals that
linux-master/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
3110: * load - in other words, there's something listening on the
linux-master/drivers/gpu/drm/bridge/ti-sn65dsi86.c
1692: * Also note that if something else is keeping the chip powered the
linux-master/drivers/gpu/drm/ci/gitlab-ci.yml
150:# something like a nightly run should include this rule.
linux-master/drivers/gpu/drm/display/drm_dp_mst_topology.c
191: /* TODO: Eventually add something to printk so we can format the rad
3048: * If something changed, make sure we send a
linux-master/drivers/gpu/drm/drm_atomic.c
385: * layer covering entire screen, since that is something we want
linux-master/drivers/gpu/drm/drm_bridge.c
1098: * happening at the board level, but that's something drivers can deal
linux-master/drivers/gpu/drm/drm_connector.c
895: * Note you could abuse this and return something out of bounds, but that
1219: * default value of link-status is "GOOD". If something fails during or
2402: * "GOOD". If something fails during or after a mode set, the kernel driver
linux-master/drivers/gpu/drm/drm_crtc_helper.c
962: * force-restore the mode setting configuration e.g. on resume or when something
linux-master/drivers/gpu/drm/drm_gem.c
553: * driver author is doing something really wrong:
624: * driver author is doing something really wrong:
linux-master/drivers/gpu/drm/drm_gem_vram_helper.c
44: * buffer are used for drawing the current frame, typically something like
linux-master/drivers/gpu/drm/drm_gpuvm.c
738: * ret = do_something_with_vm_bo(..., vm_bo);
linux-master/drivers/gpu/drm/drm_mipi_dbi.c
1063: * FIXME: implement something like mipi_dbi_spi1e_transfer() but
linux-master/drivers/gpu/drm/drm_mm.c
78: * something better would be fairly complex and since gfx thrashing is a fairly
linux-master/drivers/gpu/drm/drm_modes.c
2103: /* Make sure we have parsed something */
linux-master/drivers/gpu/drm/drm_panel.c
403: * drm_panel_add_follower() - Register something to follow panel state.
linux-master/drivers/gpu/drm/etnaviv/etnaviv_gem.c
124: /* when we start tracking the pin count, then do something here */
174: * something from beneath our feet. Note that vmf_insert_page() is
linux-master/drivers/gpu/drm/etnaviv/etnaviv_mmu.c
65: /* unroll mapping in case something went wrong */
linux-master/drivers/gpu/drm/gma500/gem.c
273: something from beneath our feet */
linux-master/drivers/gpu/drm/gma500/opregion.c
216: use the bit for something different altogether */
linux-master/drivers/gpu/drm/i915/display/g4x_dp.c
266: /* must initialize pipe to something for the asserts */
linux-master/drivers/gpu/drm/i915/display/i9xx_wm.c
446: * The FIFO level vs. time graph might look something like:
493: * The FIFO level vs. time graph might look something like:
linux-master/drivers/gpu/drm/i915/display/intel_cdclk.c
2900: * This only really does something on DISPLA_VER >= 11 but can be
3422: * available? PCI ID, VTB, something else?
linux-master/drivers/gpu/drm/i915/display/intel_cursor.c
479: * There's something wrong with the cursor on CHV pipe C.
linux-master/drivers/gpu/drm/i915/display/intel_ddi.c
1621: * If we fail this, something went very wrong: first 2 PLLs should be
linux-master/drivers/gpu/drm/i915/display/intel_display.c
1867: * default, change to something else for debugging. */
linux-master/drivers/gpu/drm/i915/display/intel_display_irq.c
1141: * Like on previous PCH there seems to be something
linux-master/drivers/gpu/drm/i915/display/intel_display_power.c
1176: * something is wrong. Don't even try to turn it on.
linux-master/drivers/gpu/drm/i915/display/intel_dp.c
628: /* Paranoia, there should always be something in common. */
2934: * that fails assume the user might know something we don't.
linux-master/drivers/gpu/drm/i915/display/intel_dpio_phy.c
1053: * on something when the channel is otherwise unused.
linux-master/drivers/gpu/drm/i915/display/intel_fb_pin.c
198: * something and try to run the system in a "less than optimal"
linux-master/drivers/gpu/drm/i915/display/intel_fbc.c
119: * something different in the struct. The genx_fbc_activate functions
linux-master/drivers/gpu/drm/i915/display/intel_hdmi.c
2327: * that fails assume the user might know something we don't.
linux-master/drivers/gpu/drm/i915/display/intel_panel.c
69: /* we want to always return something */
linux-master/drivers/gpu/drm/i915/display/intel_pps.c
1569: * BIOS did something nasty with it.
linux-master/drivers/gpu/drm/i915/display/intel_psr.c
1624: * fix it. Presumably something related to the fact that
linux-master/drivers/gpu/drm/i915/display/intel_tv.c
187: * s-video cable to the sky... or something.
linux-master/drivers/gpu/drm/i915/gem/i915_gem_context.c
12: * something like a context does exist for the media ring, the code only
linux-master/drivers/gpu/drm/i915/gem/i915_gem_context_types.h
152: * to do something which the proto-context can't handle at which point the
linux-master/drivers/gpu/drm/i915/gem/i915_gem_dmabuf.c
254: * XXX: Consider doing a vmap flush or something, where possible.
linux-master/drivers/gpu/drm/i915/gem/i915_gem_domain.c
565: * Having something in the write domain implies it's in the read
linux-master/drivers/gpu/drm/i915/gem/i915_gem_lmem.c
86: * useful if we need something bigger than the regions min_page_size due to some
linux-master/drivers/gpu/drm/i915/gem/i915_gem_mman.c
807: * (since it may have been evicted to make room for something), allocating
linux-master/drivers/gpu/drm/i915/gem/i915_gem_stolen.c
160: * kernel. So if the region is already marked as busy, something
linux-master/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
951: * already unpinned it, which should give us something more like an LRU.
linux-master/drivers/gpu/drm/i915/gem/selftests/huge_pages.c
405: * GTT pages. If we don't then something might be wrong in our
1494: * testing the most obvious cases that might make something blow up.
linux-master/drivers/gpu/drm/i915/gem/selftests/i915_gem_dmabuf.c
274: * If the exported object is not in system memory, something
linux-master/drivers/gpu/drm/i915/gt/intel_engine_cs.c
673: * to or read from a page being used for something else causes no end
linux-master/drivers/gpu/drm/i915/gt/intel_execlists_submission.c
3408: * If the engine is executing something at the moment
linux-master/drivers/gpu/drm/i915/gt/intel_gt.c
548: /* We must be able to switch to something! */
809: * an error message in dmesg, which is something we want to avoid as
linux-master/drivers/gpu/drm/i915/gt/intel_gtt.c
616: GEN8_PPAT(1, GEN8_PPAT_WC | GEN8_PPAT_LLCELLC) | /* for something pointing to ptes? */
linux-master/drivers/gpu/drm/i915/gt/intel_migrate.c
868: * sure we overwrite it with something.
linux-master/drivers/gpu/drm/i915/gt/intel_reset.c
548: * gen11_lock_sfc to make sure that we clean properly if something
1424: * so userspace knows something bad happened (should trigger collection
linux-master/drivers/gpu/drm/i915/gt/selftest_engine_heartbeat.c
264: * Ideally, the upper bound on min work delay would be something like
linux-master/drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c
541: * once there is something available to put there.
873: /* Fudge something chunky for now: */
linux-master/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
110: * is defined in the protocol or something has died and requires a reset).
linux-master/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
76: * time to resubmit something on the context before doing this costly operation.
linux-master/drivers/gpu/drm/i915/gt/uc/intel_huc.c
65: * on when the kernel schedules it. Unless something goes terribly wrong, we're
linux-master/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
922: * No more options! But set the path back to something
linux-master/drivers/gpu/drm/i915/gvt/scheduler.c
1120: * has occurred GPU hang or something wrong with i915/GVT,
linux-master/drivers/gpu/drm/i915/i915_active.c
1073: * something else, depending on the timing of other threads and/or
linux-master/drivers/gpu/drm/i915/i915_file_private.h
57: * right up until the point where we attempt to do something which
linux-master/drivers/gpu/drm/i915/i915_gem_evict.c
124: * i915_gem_evict_something - Evict vmas to make room for binding a new one
148:i915_gem_evict_something(struct i915_address_space *vm,
419: * iterator and as with i915_gem_evict_something() we employ
linux-master/drivers/gpu/drm/i915/i915_gem_evict.h
16:int __must_check i915_gem_evict_something(struct i915_address_space *vm,
linux-master/drivers/gpu/drm/i915/i915_gem_gtt.c
184: * searching for an eviction candidate. See i915_gem_evict_something() for
285: err = i915_gem_evict_something(vm, ww, size, alignment, color,
linux-master/drivers/gpu/drm/i915/i915_irq.c
443: * it, we'll get an interrupt if SDEIIR still has something to process
linux-master/drivers/gpu/drm/i915/i915_perf.c
974: * that something has gone quite badly wrong.
3551: /* Note: we don't explicitly check whether there's something to read
linux-master/drivers/gpu/drm/i915/i915_perf_types.h
120: * once there is something ready to read() for the stream
128: * something to ready to read() for the stream. E.g. wait on the same
linux-master/drivers/gpu/drm/i915/i915_scheduler_types.h
59: * something waiting on a user semaphore [VkEvent]) from denying service to
linux-master/drivers/gpu/drm/i915/i915_ttm_buddy_manager.c
168: * If we just want something mappable then we can quickly check
linux-master/drivers/gpu/drm/i915/i915_vma.c
363: * something went wrong at that stage then the object should have
linux-master/drivers/gpu/drm/i915/i915_vma_types.h
57: * view which could look something like this:
linux-master/drivers/gpu/drm/i915/intel_uncore.c
2629: * safe in case something unexpected happens
linux-master/drivers/gpu/drm/i915/selftests/i915_gem_evict.c
107:static int igt_evict_something(void *arg)
122: err = i915_gem_evict_something(&ggtt->vm, NULL,
128: pr_err("i915_gem_evict_something failed on a full GGTT with err=%d\n",
135: /* Everything is unpinned, we should be able to evict something */
137: err = i915_gem_evict_something(&ggtt->vm, NULL,
143: pr_err("i915_gem_evict_something failed on a full GGTT with err=%d\n",
540: SUBTEST(igt_evict_something),
linux-master/drivers/gpu/drm/i915/selftests/intel_memory_region.c
479: ps = SZ_64K; /* For something like DG2 */
571: ps = SZ_64K; /* For something like DG2 */
linux-master/drivers/gpu/drm/i915/selftests/intel_scheduler_helpers.c
49: * Also, reduce the preemption timeout to something
linux-master/drivers/gpu/drm/imagination/pvr_ccb.c
619: * Should only be called if something failed after the
linux-master/drivers/gpu/drm/imagination/pvr_queue.c
612: * otherwise we might miss the FW event informing us that something
1069: * * An error code if something failed.
1109: * we do multi-job submission, and something failed when creating/initializing
linux-master/drivers/gpu/drm/imagination/pvr_rogue_fwif.h
1964: * some work), so as long as the GPU is doing something and one of these
linux-master/drivers/gpu/drm/imagination/pvr_sync.c
225: * entries without doing anything when something failed.
linux-master/drivers/gpu/drm/imagination/pvr_vm.c
199: * This shouldn't happen unless something went wrong
linux-master/drivers/gpu/drm/loongson/lsdc_crtc.c
84: * something if it happens.
111: * something if it happens.
linux-master/drivers/gpu/drm/mcde/mcde_drv.c
389: /* Create something that will match the subdrivers when we bind */
linux-master/drivers/gpu/drm/mcde/mcde_dsi.c
785: * Enable clocking: 0x0f (something?) between each burst,
linux-master/drivers/gpu/drm/msm/adreno/a5xx_gpu.c
1714: * to set something with dev_pm_opp_set_supported_hw() or the table
linux-master/drivers/gpu/drm/msm/adreno/a5xx_preempt.c
55:/* Return the highest priority ringbuffer with something in it */
linux-master/drivers/gpu/drm/msm/adreno/adreno_gpu.c
580: * to scribble something invalid, we don't want that to confuse
linux-master/drivers/gpu/drm/msm/disp/mdp4/mdp4_kms.c
108: /* if we had >1 encoder, we'd need something more clever: */
linux-master/drivers/gpu/drm/msm/msm_gem.c
649: * purged until something else (shrinker, mm_notifier, destroy, etc) decides
linux-master/drivers/gpu/drm/msm/msm_gpu_devfreq.c
28: * to something that actually is in the opp table:
linux-master/drivers/gpu/drm/msm/registers/adreno/a3xx.xml
991: something?? ie. 39 becomes 40, 78 becomes 80.. 75 becomes
1335: something with a mediump/lowp uniform.
linux-master/drivers/gpu/drm/msm/registers/adreno/a4xx.xml
1070: something?? ie. 39 becomes 40, 78 becomes 80.. 75 becomes
linux-master/drivers/gpu/drm/msm/registers/adreno/a5xx.xml
2586: <!-- e5f9 something compute related.. seems to change when HLSQ_CS_CNTL_1 changes -->
2891:different border-color states per texture.. Looks something like:
linux-master/drivers/gpu/drm/msm/registers/adreno/a6xx.xml
1128: 8b unorm: 10 (sometimes 0, is the high bit part of something else?)
2621: <!-- maybe something in low bits since alignment of 1 doesn't make sense? -->
3059: <!-- TODO: first 16 bits are valid so something is wrong or missing here -->
4617: <!-- Note: these only do something when HLSQ_SHARED_CONSTS is set to 1 -->
linux-master/drivers/gpu/drm/msm/registers/adreno/adreno_pm4.xml
282: recycled for something new on a7xx
318: <value name="CP_DRAW_INDX_2" value="0x36" variants="A2XX-A4XX"/> <!-- this is something different on a6xx and unused on a5xx -->
linux-master/drivers/gpu/drm/msm/registers/display/mdp4.xml
127: <reg32 offset="0x0004c" name="READ_CNFG"/> <!-- something about # of pending requests.. -->
linux-master/drivers/gpu/drm/nouveau/dispnv04/crtc.c
113: * bits 20-23: (mpll) something to do with post divider?
linux-master/drivers/gpu/drm/nouveau/dispnv04/dac.c
320: /* bios does something more complex for restoring, but I think this is good enough */
linux-master/drivers/gpu/drm/nouveau/nouveau_bios.c
490: * bytes 40-43 are something to do with PWM
linux-master/drivers/gpu/drm/nouveau/nouveau_connector.c
1348: * figure out something suitable ourselves
linux-master/drivers/gpu/drm/nouveau/nouveau_dma.c
184: * discard these values until something sensible is seen.
linux-master/drivers/gpu/drm/nouveau/nouveau_svm.c
158: * Ok we are ask to do something sane, for now we only support migrate
545: * to an eventual DMA map in something like gp100_vmm_pgt_pfn()
linux-master/drivers/gpu/drm/nouveau/nvkm/engine/disp/gf119.c
1174: * something similar.
1200: /* steal display away from vbios, or something like that */
linux-master/drivers/gpu/drm/nouveau/nvkm/engine/disp/nv50.c
1525: * something similar. NFI what the 0x614004 caps are for..
1560: /* steal display away from vbios, or something like that */
linux-master/drivers/gpu/drm/nouveau/nvkm/engine/fifo/gf100.c
70: /*TODO: Is this cargo-culted, or necessary? RM does *something* here... Why? */
linux-master/drivers/gpu/drm/nouveau/nvkm/engine/fifo/runl.c
116: /*TODO: can we do something less of a potential catastrophe on failure? */
linux-master/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/hub.fuc
222: // sleep until we have something to do
linux-master/drivers/gpu/drm/nouveau/nvkm/engine/gr/nv50.c
411: * in DISPATCH and you need to do something about it. */
linux-master/drivers/gpu/drm/nouveau/nvkm/subdev/fb/nv50.c
158: /* decode status bits into something more useful */
linux-master/drivers/gpu/drm/omapdrm/dss/dsi.c
3271: * Send NOP between the frames. If we don't send something here, the
linux-master/drivers/gpu/drm/omapdrm/omap_gem.c
506: * something from beneath our feet
968: /* do something here if we dynamically attach/detach pages.. at
linux-master/drivers/gpu/drm/panel/panel-ilitek-ili9322.c
15: * present to the system is something else than what comes out on the
linux-master/drivers/gpu/drm/panfrost/panfrost_drv.c
428: * We could do something smarter and mark the BO purgeable only
linux-master/drivers/gpu/drm/panthor/panthor_device.c
546: /* If something failed and we have to revert back to an
linux-master/drivers/gpu/drm/panthor/panthor_drv.c
1334: * specific. This converts a user MMIO offset into something the kernel
linux-master/drivers/gpu/drm/panthor/panthor_mmu.c
363: * @unusable: True if the VM has turned unusable because something
958: /* If something failed, unmap what we've already mapped before
linux-master/drivers/gpu/drm/panthor/panthor_sched.c
114: * all its queues, or when queues are blocked waiting for something
234: * When a group has queues that want to execute something,
linux-master/drivers/gpu/drm/pl111/pl111_drv.c
22: * cursors. While one could imagine trying to hack something together
115: /* Continue, maybe something else is working */
linux-master/drivers/gpu/drm/pl111/pl111_nomadik.c
18: * multiplatform on something else than Nomadik.
linux-master/drivers/gpu/drm/radeon/cik_sdma.c
271: /* FIXME use something else than big hammer but after few days can not
linux-master/drivers/gpu/drm/radeon/evergreen.c
1191: /* start off with something large */
linux-master/drivers/gpu/drm/radeon/ni.c
1293: /* Assign the pt base to something valid for now; the pts used for
linux-master/drivers/gpu/drm/radeon/r100.c
646: /* TODO: can we do somethings here ? */
875: * CPU might read something from VRAM. */
linux-master/drivers/gpu/drm/radeon/r300_reg.h
407: * (or something closely related to that).
linux-master/drivers/gpu/drm/radeon/radeon_combios.c
806: rdev->clock.max_pixel_clock = 35000; /* might need something asic specific */
3250: /* something like this???? */
3271: /* should do something smarter here I guess... */
linux-master/drivers/gpu/drm/radeon/radeon_display.c
1924: /* No: Fake something reasonable which gives at least ok results. */
linux-master/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
1562: /* don't probe if the encoder is being used for something else not CRT related */
linux-master/drivers/gpu/drm/radeon/radeon_uvd.c
960: /* start off with something large */
linux-master/drivers/gpu/drm/radeon/si.c
4313: /* Assign the pt base to something valid for now; the pts used for
linux-master/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
1505: * something goes really wrong. The wait will only happen in the very
linux-master/drivers/gpu/drm/sun4i/sun4i_backend.c
889: * Clear the registers here to have something predictable.
linux-master/drivers/gpu/drm/sun4i/sun4i_rgb.c
115: * That shouldn't ever happen unless something is really wrong, but it
linux-master/drivers/gpu/drm/tegra/drm.c
1108: * SG table representing these buffers. This is fine for something
linux-master/drivers/gpu/drm/tiny/cirrus.c
94: * be something that can be correctly programmed and displayed
linux-master/drivers/gpu/drm/vc4/vc4_bo.c
644: * Luckily the BO hasn't been purged yet, but something wrong
linux-master/drivers/gpu/drm/vc4/vc4_hdmi.c
2830: * means we cannot use it for something else. The hdmi back-pointer is
linux-master/drivers/gpu/drm/vc4/vc4_kms.c
836: * we will need to have something smarter, but it works so far.
linux-master/drivers/gpu/drm/vc4/vc4_validate.c
124: DRM_DEBUG("Trying to use shader BO as something other than "
linux-master/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
115: /* Make sure we always show something. */
linux-master/drivers/gpu/drm/xe/abi/guc_klvs_abi.h
198: * something else, it might never take effect if the VF is running an
215: * something else, it might never take effect if the VF is running an
linux-master/drivers/gpu/drm/xe/xe_device.c
350: * safe in case something unexpected happens
linux-master/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
421: * see something later in the timeline we can be sure that anything
linux-master/drivers/gpu/drm/xe/xe_guc_ct.c
1284: * here. If we ever need something stronger than get_if_ongoing() then
linux-master/drivers/gpu/drm/xe/xe_guc_submit.c
936: * somethings has gone wrong and the GT needs a reset
linux-master/drivers/gpu/drm/xe/xe_lrc.c
801: /* While this appears to have something about privileged batches or
linux-master/drivers/gpu/drm/xe/xe_pm.c
286: * the extent that something else re-uses the task written in
linux-master/drivers/gpu/ipu-v3/ipu-image-convert.c
1537: * something went wrong with start, add the run
linux-master/drivers/greybus/operation.c
127: * done something fundamentally wrong. It is an error to try to set
1023: * supplied data buffer will be reused (so unless we do something
linux-master/drivers/greybus/svc_watchdog.c
83: "SVC ping has returned %d, something is wrong!!!\n",
linux-master/drivers/hid/bpf/hid_bpf_dispatch.c
633: * is probably not something we want. So we log an error and return success.
linux-master/drivers/hid/hid-core.c
2323: * This is usually called from remove function or from probe when something
linux-master/drivers/hid/hid-cp2112.c
616: * because something is seriously wrong and
linux-master/drivers/hid/hid-logitech-hidpp.c
336: * hidpp_send_message_sync() returns 0 in case of success, and something else
365: * hidpp_send_fap_command_sync() returns 0 in case of success, and something else
404: * hidpp_send_rap_command_sync() returns 0 in case of success, and something else
linux-master/drivers/hid/hid-multitouch.c
1275: * something wrong happens, either the touchscreen forgets to send
linux-master/drivers/hid/hid-ntrig.c
944: * something reasonable.
linux-master/drivers/hid/hid-roccat-kone.c
126: * value of 3 seems to mean something like
linux-master/drivers/hid/intel-ish-hid/ipc/pci-ish.c
285: * If the flag is not cleared, something is wrong with ISH FW.
linux-master/drivers/hv/ring_buffer.c
401: /* Make sure there is something to read */
linux-master/drivers/hwmon/ads7871.c
7: * You need to have something like this in struct spi_board_info
linux-master/drivers/hwmon/hwmon-vid.c
232: * Note: something similar might be needed for model A, I'm not sure.
291:/* and now for something completely different for the non-x86 world */
linux-master/drivers/hwmon/it87.c
3688: * connected to a fan, but to something else. One user
linux-master/drivers/hwmon/lm93.c
291: * The two PWM CTL2 registers can read something other than what was
linux-master/drivers/hwmon/nct6775-i2c.c
72: * something this driver shouldn't be doing.
linux-master/drivers/hwmon/pc87427.c
197: * The 2 LSB of fan speed registers are used for something different.
linux-master/drivers/hwmon/pmbus/delta-ahe50dc-fan.c
92: * it doesn't support something (and if we enable I2C_CLIENT_PEC on seeing bit
linux-master/drivers/hwmon/pmbus/pmbus_core.c
3611: * If there are no attributes, something is wrong.
linux-master/drivers/hwtracing/coresight/coresight-core.c
184: * and has manipulated it. Or something else has seriously
811: /* look past LINKSINK for something better */
linux-master/drivers/hwtracing/coresight/coresight-etm3x-sysfs.c
1057: * namespace won't be what the kernel sees, something that makes the
linux-master/drivers/hwtracing/coresight/coresight-etm4x-sysfs.c
1929: * namespace won't be what the kernel sees, something that makes the
linux-master/drivers/hwtracing/intel_th/msu.c
365: * something like 2, in which case we're good
linux-master/drivers/i2c/algos/i2c-algo-bit.c
362: * something about the data it saw. For example, maybe
linux-master/drivers/i2c/busses/i2c-ali15x3.c
25: on the PCI bus. An output of lspci will show something similar
linux-master/drivers/i2c/busses/i2c-amd756.c
15: 2002-12-28: Rewritten into something that resembles a Linux driver (hch)
linux-master/drivers/i2c/busses/i2c-aspeed.c
295: /* Slave was sent something. */
linux-master/drivers/i2c/busses/i2c-gpio.c
372: * device tree then this means that something outside of our control is
linux-master/drivers/i2c/busses/i2c-ibm_iic.c
591: /* Usually it means something serious has happened.
linux-master/drivers/i2c/busses/i2c-img-scb.c
829: * Timer function to check if something has gone wrong in automatic mode (so we
linux-master/drivers/i2c/busses/i2c-mlxcpld.c
410: * Usually it means something serious has happened.
linux-master/drivers/i2c/busses/i2c-ocores.c
256: * ocores_wait() - Wait until something change in a given register
315: * so if after 1ms we timeout then something is broken.
linux-master/drivers/i2c/busses/i2c-pnx.c
238: /* We still have something to talk about... */
linux-master/drivers/i2c/busses/i2c-pxa.c
894: * something more serious happened. If we were NAK'd
linux-master/drivers/i2c/busses/i2c-s3c2410.c
500: * something with it, and then work out whether we are
839: * range of frequencies until something is found
linux-master/drivers/i2c/i2c-core-base.c
2450: /* Make sure there is something at this address */
linux-master/drivers/i3c/master/mipi-i3c-hci/dma.c
527: /* TODO: do something about it? */
linux-master/drivers/i3c/master/mipi-i3c-hci/pio.c
660: /* return true if we actually unqueued something */
linux-master/drivers/iio/adc/ad7949.c
136: * at the next xfer, so we bail out now, otherwise we write something
149: /* 3: write something and read actual data */
linux-master/drivers/iio/adc/at91-sama5d2_adc.c
1464: * the buffer to start with a mixed mask (voltage and something
1641: * from our IRQ context. Which is something we better avoid.
linux-master/drivers/iio/adc/bcm_iproc_adc.c
324: * We never got the interrupt, something went wrong.
linux-master/drivers/iio/adc/ti_am335x_adc.c
496: * something went wrong we left empty handed (-EAGAIN previously) and
linux-master/drivers/iio/buffer/industrialio-buffer-dma.c
421: * out of memory or something similar.
424: * notify consumers that something went wrong and the buffer
linux-master/drivers/iio/gyro/mpu3050-core.c
584: * check if something new appeared.
linux-master/drivers/iio/resolver/ad2s1210.c
282: * something else there.
linux-master/drivers/infiniband/core/addr.c
190: * we will have something.
linux-master/drivers/infiniband/core/device.c
1700: * something, so disassociation is mandatory.
linux-master/drivers/infiniband/core/ib_core_uverbs.c
62: * wish to send something like PCI-E BAR memory to userspace.
linux-master/drivers/infiniband/core/nldev.c
1609: * FIXME: if the skip ahead is something common this loop should
linux-master/drivers/infiniband/core/rdma_core.c
320: * The idr_find is guaranteed to return a pointer to something that
linux-master/drivers/infiniband/hw/cxgb4/qp.c
2373: /* Make sure we still have something left to do */
linux-master/drivers/infiniband/hw/hfi1/chip.c
5878: * If the handler loops too many times, assume that something is wrong
7190: * Only do something if the link is currently up.
linux-master/drivers/infiniband/hw/hfi1/driver.c
769: * the range of valid indexes. If so something is really
linux-master/drivers/infiniband/hw/hfi1/firmware.c
16: * editing the following. This may be something we do while in development
17: * but not necessarily something a user would ever need to use.
560: * something that holds for 30 seconds. If we do that twice
linux-master/drivers/infiniband/hw/hfi1/hfi.h
329: * if something is used one time to derive some value, store that something in
linux-master/drivers/infiniband/hw/hfi1/mad.c
1462: /* only set and apply if something changed */
linux-master/drivers/infiniband/hw/hfi1/rc.c
2796: * packet sequence number will be for something in the send work
linux-master/drivers/infiniband/hw/hfi1/user_sdma.c
866: * tididx points to something sane.
linux-master/drivers/infiniband/hw/mthca/mthca_cmd.c
252: * We use writel (instead of something like memcpy_toio)
linux-master/drivers/infiniband/hw/qib/qib_common.h
304: * Define the driver version number. This is something that refers only
linux-master/drivers/infiniband/hw/qib/qib_driver.c
235: * If the link isn't ARMED, then something else happened
linux-master/drivers/infiniband/hw/qib/qib_iba6120.c
1422: * we can. Green indicates physical link state is OK (something is
1429: * visible overhead, so not something we will do.
3058: * a read on another, and because the old code did something like
linux-master/drivers/infiniband/hw/qib/qib_iba7220.c
1715: * we can. Green indicates physical link state is OK (something is
1722: * visible overhead, so not something we will do.
3773: * a read on another, and because the old code did something like
linux-master/drivers/infiniband/hw/qib/qib_iba7322.c
2583: * we can. Green indicates physical link state is OK (something is
2590: * visible overhead, so not something we will do.
3633: * it ourselves. There is some risk something could change it,
5695: * a read on another, and because the old code did something like
linux-master/drivers/infiniband/hw/qib/qib_init.c
549: * case something went wrong with abort, but mostly to get the
linux-master/drivers/infiniband/hw/qib/qib_intr.c
229: /* disable interrupt delivery, something is very wrong */
linux-master/drivers/infiniband/hw/qib/qib_mad.c
517: default: /* something is wrong; fall through */
linux-master/drivers/infiniband/hw/qib/qib_pcie.c
205: /* set up something... */
linux-master/drivers/infiniband/hw/qib/qib_rc.c
1748: * packet sequence number will be for something in the send work
linux-master/drivers/infiniband/hw/qib/qib_twsi.c
271: * is something wrong.
linux-master/drivers/infiniband/sw/rxe/rxe_comp.c
465: * we completed something so let req run again
linux-master/drivers/infiniband/ulp/ipoib/ipoib_multicast.c
81: * We will be scheduling *something*, so cancel whatever is
linux-master/drivers/infiniband/ulp/rtrs/rtrs-clt.c
404: * 2. something totally bad happened and
2083: * for waiting two possible cases: cm_err has something meaningful
2194: * something is wrong, here we will stuck for exactly timeout ms,
2908: * execution, so do the flush if we have queued something
linux-master/drivers/input/ff-memless.c
259: * If in future any driver wants something else than x and y
260: * in s8, this should be changed to something more generic
linux-master/drivers/input/joystick/Kconfig
10: weapon control system or something like that you can say Y here
linux-master/drivers/input/keyboard/cros_ec_keyb.c
334: * unmarshalling and different version nonsense into something simple.
linux-master/drivers/input/misc/soc_button_array.c
99: * Lenovo Yoga Tab2 1051F/1051L, something messes with the home-button
linux-master/drivers/input/mouse/cyapa.c
1258: /* Make sure there is something at this address */
linux-master/drivers/input/mouse/elan_i2c_core.c
1240: /* Make sure there is something at this address */
linux-master/drivers/input/mouse/focaltech.c
52: * something here.
linux-master/drivers/input/mouse/rpcmouse.c
14: * the complete state and then work out if something has changed.
linux-master/drivers/input/mouse/synaptics.c
1608: * Because version is __u16 we have to drop something.
linux-master/drivers/input/tablet/aiptek.c
1733: * us something...
linux-master/drivers/input/touchscreen/Kconfig
1414: or something similar enough.
linux-master/drivers/input/touchscreen/edt-ft5x06.c
874: /* Probe content for something consistent.
linux-master/drivers/input/touchscreen/elants_i2c.c
1476: /* Make sure there is something at this address */
linux-master/drivers/input/touchscreen/goodix.c
324: * Userspace wants something here though, so just set it to 10 units/mm.
linux-master/drivers/input/touchscreen/melfas_mip4.c
253: * Make sure there is something at this address as we do not
linux-master/drivers/input/touchscreen/raydium_i2c_ts.c
1114: /* Make sure there is something at this address */
linux-master/drivers/iommu/arm/arm-smmu/arm-smmu.c
2221: * it's really going to do something useful - pm_runtime_enabled()
linux-master/drivers/iommu/iommu.c
391: /* FSL_PAMU does something weird */
2309: * either new_domain or group->domain, never something else.
2482: /* unroll mapping in case something went wrong */
linux-master/drivers/iommu/iommufd/device.c
973: * The driver must be doing something wrong if it calls this before an
linux-master/drivers/iommu/iommufd/io_pagetable.h
19: * the iova that are backed by something. iova not covered by areas is not
linux-master/drivers/iommu/iommufd/iova_bitmap.c
18: * For example, for something recording dirty IOVAs, it will be provided a
linux-master/drivers/iommu/iommufd/pages.c
229: * something other than exactly as requested. This implies that the
1085: * pages->last_pinned, for instance something like unmapping a domain must only
1271: * For security we must not unpin something that is still DMA mapped,
linux-master/drivers/ipack/devices/ipoctal.c
78: * there is something to send
linux-master/drivers/irqchip/irq-bcm7120-l2.c
127: * This is typically something needed on BCM7xxx (STB chips).
linux-master/drivers/irqchip/irq-gic-v3-its.c
3903: * indication that the vcpu has something pending, not one
5399: * result in something even worse.
5617: * result in something even worse.
linux-master/drivers/irqchip/irq-gic-v3.c
845: * would then be taken in NMI context, something that nobody
linux-master/drivers/irqchip/irq-gic.c
1315: * the second was *something*. Let's trust it
1565:/* The things you have to do to just *count* something... */
linux-master/drivers/irqchip/irq-i8259.c
154: * is something bad going on ...
linux-master/drivers/leds/TODO
7:make it into typedef or something.
linux-master/drivers/macintosh/Kconfig
43:# we want to change this to something like CONFIG_SYSCTRL_CUDA/PMU
linux-master/drivers/macintosh/macio_asic.c
414: 0, /* NuBus may want to do something better here */
linux-master/drivers/macintosh/mediabay.c
699: * register is always set when there is something in the media bay.
linux-master/drivers/mailbox/mailbox-mpfs.c
165: * still in the busy state. If we do, something has gone badly
linux-master/drivers/mailbox/pcc.c
386: * Return: Err if something failed else 0 for success.
409: * Return: Err if something failed else 0 for success.
linux-master/drivers/md/bcache/bcache.h
53: * of each bucket. It could be used to implement something more sophisticated,
linux-master/drivers/md/bcache/journal.c
885: * bch_keylist_realloc() - but something to think about.
linux-master/drivers/md/bcache/request.c
261: * we might be starving btree writes for gc or something.
linux-master/drivers/md/bcache/writeback.h
25: * 14 (16384ths) is chosen here as something that each backing device
linux-master/drivers/md/dm-bufio.c
252: ER_STOP, /* stop looking for something to evict */
linux-master/drivers/md/dm-cache-policy.h
64: * so it knows to do something different with the bio.
linux-master/drivers/md/dm-clone-metadata.c
958: /* If something went wrong we can neither write nor read the metadata */
linux-master/drivers/md/dm-mpath.c
1562: * Probably doing something like FW upgrade on the
linux-master/drivers/md/dm-table.c
1519: * capable of something.
1525: * capable of something. So: return !dm_table_any_dev_attr(t, anti_func, data);
linux-master/drivers/md/dm-vdo/errors.c
250: /* Translate an unexpected error into something generic. */
linux-master/drivers/md/dm-vdo/status-codes.c
65: * code (such as EIO), or a UDS or VDO status code; the result must be something the rest of the OS
linux-master/drivers/md/dm-writecache.c
884: bool discarded_something = false;
894: if (!discarded_something) {
899: discarded_something = true;
912: if (discarded_something)
linux-master/drivers/md/dm-zone.c
174: /* Revalidate only if something changed. */
linux-master/drivers/md/dm.c
1276: * here, something is wrong.
linux-master/drivers/md/md-autodetect.c
54: * a hex number or something like /dev/hda1 /dev/sdb
linux-master/drivers/md/md-bitmap.c
1849: /* need to kick something here to make sure I/O goes? */
linux-master/drivers/md/md-cluster.c
985: /* wake up recv thread in case something need to be handled */
linux-master/drivers/md/md.c
4421:* something is wrong.
linux-master/drivers/md/persistent-data/dm-btree-remove.c
308: * in right, then rebalance2. This wastes some cpu, but I want something
linux-master/drivers/md/persistent-data/dm-space-map-disk.c
143: * We search before smd->begin in case something has been freed.
linux-master/drivers/md/persistent-data/dm-space-map-metadata.c
462: * We search before smm->begin in case something has been freed.
linux-master/drivers/md/raid1.c
495: * to user-side. So if something waits for IO, then it
940: * Sometimes we need to suspend IO while we do something else,
2846: * If a read fails, we try reading from something else for which READ
linux-master/drivers/md/raid10.c
397: * user-side. So if something waits for IO, then it will
516: * user-side. So if something waits for IO, then it will
903: * Sometimes we need to suspend IO while we do something else,
4602: * or we hit a bad block or something.
linux-master/drivers/md/raid5.c
3831: * This can only be a problem when we need to write something,
linux-master/drivers/media/cec/core/cec-adap.c
427: * If something went wrong and this counter isn't what it should
477: /* Otherwise we just wait for something to happen. */
1339: * we assume that something is really weird and that it is not a
linux-master/drivers/media/cec/core/cec-core.c
27: * finish before that time something is really wrong and we
30: * This is a sign that something it really wrong and a warning
linux-master/drivers/media/common/saa7146/saa7146_core.c
304: /* only wake up if we expect something */
linux-master/drivers/media/common/saa7146/saa7146_fops.c
172: then something is seriously broken before, so no need to buffer the
linux-master/drivers/media/common/videobuf2/videobuf2-v4l2.c
622: * Maybe something more efficient will be needed in this case.
linux-master/drivers/media/dvb-core/dvb_ca_en50221.c
1825: /* if there is something, return now */
linux-master/drivers/media/dvb-frontends/cx24113.c
217: return 1; /* did something */
linux-master/drivers/media/dvb-frontends/dib3000mb.c
326: /* something has to be auto searched */
linux-master/drivers/media/dvb-frontends/dib8000.c
3743: dprintk("strange callback time something went wrong\n");
linux-master/drivers/media/dvb-frontends/dib9000.c
436: !(cmd & 0x80 && m->size < 67)) /* and we do not want to read something with less than 67 bytes looping - working around a bug in the memory controller */
1504: switch (i) { /* something happened */
linux-master/drivers/media/dvb-frontends/drx39xyj/drxj.c
8902: timeout_ofs += DRXJ_QAM_DEMOD_LOCK_EXT_WAITTIME; /* see something, waiting longer */
9047: timeout_ofs += DRXJ_QAM_DEMOD_LOCK_EXT_WAITTIME; /* see something, wait longer */
linux-master/drivers/media/dvb-frontends/dvb_dummy_fe.c
60: * Should only be implemented if it actually reads something from the hardware.
linux-master/drivers/media/dvb-frontends/or51132.c
171: /* Once upon a time, this command might have had something
linux-master/drivers/media/dvb-frontends/stv090x.c
2771: * something is really wrong at the car_loop table.
linux-master/drivers/media/i2c/ccs/ccs-core.c
956: /* Exposure limits will be updated soon, use just something here. */
linux-master/drivers/media/i2c/cx25840/cx25840-core.c
2397: * those addresses do something else entirely on the cx2388x and
linux-master/drivers/media/i2c/cx25840/cx25840-ir.c
548: * If there was something in the tx_kfifo, check the tx_kfifo
linux-master/drivers/media/i2c/st-vgxy61.c
951: /* If this happens, something is wrong with formulas */
1451: * Then fill remaining slots for every physical slot to have something
linux-master/drivers/media/pci/bt8xx/bttv-audio-hook.c
53:/* connect something to the GPIO pins */
linux-master/drivers/media/pci/bt8xx/bttv-cards.c
3599: found is really something else (e.g. a tea6300). */
linux-master/drivers/media/pci/bt8xx/bttv-driver.c
2698: * until something else causes a field to be
linux-master/drivers/media/pci/cx18/cx18-fileops.c
38: CX18_WARN("MPEG Index stream cannot be claimed directly, but something tried.\n");
linux-master/drivers/media/pci/cx18/cx18-vbi.c
179: * 0x3fffffff [4 bytes of something] [4 byte presentation time stamp]
linux-master/drivers/media/pci/cx23885/cx23888-ir.c
548: * If there was something in the tx_kfifo, check the tx_kfifo
linux-master/drivers/media/pci/cx25821/cx25821-medusa-video.c
672: * likely that it really should be something else, but due to the
linux-master/drivers/media/pci/ddbridge/ddbridge-dummy-fe.c
58: * Should only be implemented if it actually reads something from the hardware.
linux-master/drivers/media/pci/intel/ipu6/ipu6-fw-isys.h
466: * @error: error code if something went wrong
501: * @error: error code if something went wrong
linux-master/drivers/media/pci/intel/ipu6/ipu6-mmu.c
738: /* unroll mapping in case something went wrong */
linux-master/drivers/media/pci/ivtv/ivtv-firmware.c
364: /* If something failed & currently idle, try to reload */
linux-master/drivers/media/pci/ivtv/ivtv-gpio.c
107: /* We could use something else for smaller time */
linux-master/drivers/media/pci/ivtv/ivtv-streams.c
392: The '- 1' byte is probably an unused U or V byte. Or something...
linux-master/drivers/media/pci/saa7134/saa7134-input.c
892: respond to probes unless we read something from
912: * respond to probes unless we read something from
928: respond to probes unless we read something from
linux-master/drivers/media/pci/zoran/zoran.h
302: * There was something called _ALPHA_BUZ that used the PCI address instead of
linux-master/drivers/media/pci/zoran/zoran_device.c
111: /* wait for something to happen */
linux-master/drivers/media/pci/zoran/zr36016.c
38: /* just in case something is wrong... */
55: // just in case something is wrong...
73: /* just in case something is wrong... */
93: /* just in case something is wrong... */
402: pr_debug("zr36016: something's wrong - %d codecs left somehow.\n",
linux-master/drivers/media/pci/zoran/zr36050.c
46: /* just in case something is wrong... */
63: /* just in case something is wrong... */
104: if (i++ > 200000) { // 200ms, there is for sure something wrong!!!
435: return; // something is wrong, its timed out!!!!
504: return; // something is wrong, its timed out!!!!
813: pr_debug("zr36050: something's wrong - %d codecs left somehow.\n",
linux-master/drivers/media/pci/zoran/zr36060.c
46: // just in case something is wrong...
61: // just in case something is wrong...
102: if (i++ > 200000) { // 200ms, there is for sure something wrong!!!
453: return; // something is wrong, its timed out!!!!
864: pr_debug("zr36060: something's wrong - %d codecs left somehow.\n",
linux-master/drivers/media/platform/intel/pxa_camera.c
1407: * the buffer with something
linux-master/drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_h264_req_common.c
293: * something is buggy.
linux-master/drivers/media/platform/microchip/microchip-csi2dc.c
270: /* in case we could not find the desired format, default to something */
linux-master/drivers/media/platform/renesas/rcar-vin/rcar-dma.c
1477: * If this happens something have gone horribly wrong.
1481: vin_err(vin, "Failed stop HW, something is seriously broken\n");
1487: /* If something went wrong, free buffers with an error. */
linux-master/drivers/media/platform/renesas/rzg2l-cru/rzg2l-video.c
376: dev_err(cru->dev, "Failed stop HW, something is seriously broken\n");
linux-master/drivers/media/platform/st/sti/c8sectpfe/c8sectpfe-core.c
652: * and ideally do something about them!
linux-master/drivers/media/platform/verisilicon/hantro_h264.c
344: * something is buggy.
linux-master/drivers/media/radio/radio-cadet.c
585: * io should only be set if the user has used something like
linux-master/drivers/media/radio/radio-tea5764.c
339: be replaced with something better, but changing this
linux-master/drivers/media/rc/Kconfig
157: Output should include ENE0100 ENE0200 or something similar.
linux-master/drivers/media/rc/imon.c
1114: * prodding or by something like ir-keytable. In the rc_register_device case,
linux-master/drivers/media/rc/keymaps/rc-ati-x10.c
90: { 0x28, KEY_STOPCD }, /* ([]) Stop (KEY_STOP is something else!) */
linux-master/drivers/media/rc/mceusb.c
246: * remotes, but we should have something handy,
linux-master/drivers/media/rc/nuvoton-cir.c
701: * followed by a series of 0x7f packets, then either 0x7<something> or 0x80
703: * sample data in the raw event kfifo until we see 0x7<something> (except f)
linux-master/drivers/media/spi/gs1662.c
306: * Check if the component detect a line, a frame or something else
374: * Check if the component detect a line, a frame or something else
linux-master/drivers/media/test-drivers/vidtv/vidtv_demod.c
185: * and make them different, as we want to have something closer
252: * Should only be implemented if it actually reads something from the hardware.
linux-master/drivers/media/test-drivers/vidtv/vidtv_pes.c
263: * vidtv_pes_h_get_len(). If something went wrong, print a warning
linux-master/drivers/media/test-drivers/vidtv/vidtv_psi.c
1326: * This can be changed to something more useful, when support for
linux-master/drivers/media/test-drivers/vivid/vivid-vid-cap.c
464:/* Map the field to something that is valid for the current input */
linux-master/drivers/media/test-drivers/vivid/vivid-vid-out.c
278:/* Map the field to something that is valid for the current output */
471: * purposes, and it is something that HDMI transmitters are able
linux-master/drivers/media/usb/as102/as102_usb_drv.c
382: /* something prevented us from registering this driver */
linux-master/drivers/media/usb/au0828/au0828-video.c
1284: * FIXME: when we support something other than 60Hz standards,
linux-master/drivers/media/usb/dvb-usb/dib0700_core.c
603: * rather than enabling something or not */
linux-master/drivers/media/usb/dvb-usb/digitv.c
256: /* if something is inside the buffer, simulate key press */
linux-master/drivers/media/usb/dvb-usb/dvb-usb-init.c
291: deb_err("something went very wrong, device was not found in current device list - let's see what comes next.\n");
linux-master/drivers/media/usb/dvb-usb/technisat-usb2.c
349: *cold = 0; /* by default do not download a firmware - just in case something is wrong */
linux-master/drivers/media/usb/dvb-usb-v2/af9035.c
1508: * XXX: there seems to be something on gpioh8 too, but on my
linux-master/drivers/media/usb/gspca/gspca.c
866: /* something when wrong
linux-master/drivers/media/usb/gspca/m5602/m5602_ov9650.c
44: /* Do something out of spec with the power */
74: /* Do something out of spec with the power */
linux-master/drivers/media/usb/gspca/spca508.c
585: * does something like the previous section,
linux-master/drivers/media/usb/gspca/t613.c
11: * * Gamma table, is there, but its really doing something?
linux-master/drivers/media/usb/gspca/touptek.c
41: * Want to do something similar to mt9v011.c's set_balance
linux-master/drivers/media/usb/gspca/xirlink_cit.c
1828: * do something.
linux-master/drivers/media/usb/msi2500/msi2500.c
264: * someday if there is something rational...
linux-master/drivers/media/usb/pvrusb2/pvrusb2-dvb.c
52: /* Since we know we did something to a buffer,
linux-master/drivers/media/usb/pvrusb2/pvrusb2-hdw.c
49: where we can't do something until we know that the encoder has been run
2171: are, but I set them to something usable in the Chicago area just
4268: something to a state bit and must also
4283: quiet interval before doing something to
4491: /* We don't do something about the
linux-master/drivers/media/usb/pvrusb2/pvrusb2-i2c-core.c
227: /* Mangle the results into something that looks like the real IR
236: /* Mash the FX2 firmware-provided IR code into something
linux-master/drivers/media/v4l2-core/v4l2-ctrls-api.c
176: * willing to spend on trying to make something atomic that really isn't.
200: * EBUSY. That usually means that something started streaming just when you
linux-master/drivers/media/v4l2-core/v4l2-i2c.c
110: * If we have a client but no subdev, then something went wrong and
linux-master/drivers/media/v4l2-core/v4l2-spi.c
70: * If we have a client but no subdev, then something went wrong and
linux-master/drivers/memory/tegra/tegra210-emc-cc-r21021.c
922: * something for the form: f_ceil(N + .5) = N + 1;
linux-master/drivers/memstick/core/ms_block.c
471: * device refuses to take the command or something else
linux-master/drivers/message/fusion/mptbase.c
514: /* non-TURBO reply! Hmmm, something may be up...
linux-master/drivers/mfd/mcp-sa11x0.c
71: * We really should try doing something more productive while we
98: * We really should try doing something more productive while we
linux-master/drivers/mfd/sm501.c
1493: * either by something attempting setup, power loss,
linux-master/drivers/mfd/tps65010.c
326: /* may need to shut something down ... */
linux-master/drivers/mfd/wm8994-core.c
135: * don't know that something will be driving them. */
linux-master/drivers/misc/apds990x.c
1101: /* Set something to start with */
linux-master/drivers/misc/bcm-vk/bcm_vk_dev.c
973: * if something is pending download already. This could only happen
linux-master/drivers/misc/bcm-vk/bcm_vk_msg.c
450: * something is wrong
linux-master/drivers/misc/bcm-vk/bcm_vk_tty.c
133: /* initialize the pointer in case something fails */
linux-master/drivers/misc/cxl/pci.c
1858: * If we reflash, we could come back as something entirely
linux-master/drivers/misc/echo/echo.c
284: * need this, but something like a $10 X100P card does. Any DC really
linux-master/drivers/misc/echo/echo.h
69:If the adaption is performed while transmitting noise (or something fairly
71:performed while transmitting something highly correlative (typically narrow
linux-master/drivers/misc/enclosure.c
197: * In odd circumstances, like multipath devices, something else may
linux-master/drivers/misc/genwqe/card_ddcb.c
1376: * ... so I take something large.
linux-master/drivers/misc/genwqe/genwqe_driver.h
35: * something dynamic.
linux-master/drivers/misc/lkdtm/heap.c
25: * let us overflow into the second allocation without overwriting something real.
linux-master/drivers/misc/lkdtm/stackleak.c
43: * STACK_END_MAGIC, and in either casee something is seriously wrong.
linux-master/drivers/misc/mei/client.c
1184: /* timeout or something went really wrong */
2094: /* clean all queue on timeout as something fatal happened */
linux-master/drivers/misc/ocxl/config.c
606: * when trying to configure something too big.
linux-master/drivers/misc/ocxl/core.c
403: * - probably something like:
linux-master/drivers/misc/sgi-xp/xpc_uv.c
222: /* something went wrong */
linux-master/drivers/misc/vmw_balloon.c
1124: * If an error indicates that something serious went wrong,
linux-master/drivers/misc/vmw_vmci/vmci_context.c
406: * reference count of something that is in the
linux-master/drivers/mmc/core/sdio_bus.c
182: /* Set the default block size so the driver is sure it's something
linux-master/drivers/mmc/host/au1xmmc.c
573: /* Start the DBDMA as soon as the buffer gets something in it */
linux-master/drivers/mmc/host/cb710-mmc.c
378: * hardware can do something special about this
linux-master/drivers/mmc/host/mmci.c
1628: * SDIO especially may want to send something that is
1673: * SDIO especially may want to send something that is
linux-master/drivers/mmc/host/omap.c
1223: /* On insanely high arm_per frequencies something sometimes
linux-master/drivers/mmc/host/sdhci-esdhc-imx.c
1440: * level setting to something insane. Change it back here.
linux-master/drivers/mmc/host/sdhci-of-arasan.c
324: * are required then caller needs to do something special
487: * actually if we force to enable 1V8. That's something
linux-master/drivers/mmc/host/sunplus-mmc.c
788: * or a negative errno value when something bad happened
linux-master/drivers/mmc/host/toshsd.c
147: /* Write something to end the command */
linux-master/drivers/mtd/devices/Kconfig
70: flipped accidentally due to device wear or something else.
linux-master/drivers/mtd/devices/pmc551.c
450: * Oops .. something went wrong
linux-master/drivers/mtd/inftlcore.c
540: * Hopefully we free something, lets try again.
553: * routine is missing something.
linux-master/drivers/mtd/inftlmount.c
690: * this loop if we find something newer.
linux-master/drivers/mtd/lpddr/lpddr_cmds.c
320: /* Oops. something got wrong. */
linux-master/drivers/mtd/maps/ck804xrom.c
72: * Please set win_size_bits to 0x7fffffff if you actually want to do something
linux-master/drivers/mtd/maps/vmu-flash.c
250: /* wait until the device is not busy doing something else
linux-master/drivers/mtd/mtdchar.c
1386: replaced with something that uses the mtd_get_unmapped_area()
linux-master/drivers/mtd/mtdpstore.c
493: * something to ensure log file removed. If the whole block is no longer used,
linux-master/drivers/mtd/nand/onenand/Kconfig
18: flipped accidentally due to device wear or something else.
linux-master/drivers/mtd/nand/raw/cafe_nand.c
97:/* Hrm. Why isn't this already conditional on something in the struct device? */
linux-master/drivers/mtd/nand/raw/lpc32xx_slc.c
578: /* Something is left in the FIFO, something is wrong */
linux-master/drivers/mtd/nand/raw/marvell_nand.c
753: * check if the ISR was not served or if something went actually wrong.
linux-master/drivers/mtd/nand/raw/nand_base.c
688: * use this as polling delay before doing something smarter (ie.
linux-master/drivers/mtd/nand/raw/nandsim.c
1970: * We are in situation when something else (not command)
linux-master/drivers/mtd/nftlcore.c
616: routine is missing something.
linux-master/drivers/mtd/nftlmount.c
366: * not updated according (due to power failure or something) which leaves the block
linux-master/drivers/mtd/sm_ftl.c
526: /* If we found three different LBAs, something is fishy */
linux-master/drivers/mtd/spi-nor/core.c
101: * something like 4S-4D-4D, but SPI NOR can't. So, set all 4
linux-master/drivers/mtd/spi-nor/core.h
369: * @convert_addr: converts an absolute address into something the flash
linux-master/drivers/mtd/ubi/eba.c
938: * In case of error, it is possible that something was still written to the
1009: * of failure. In case of error, it is possible that something was still
1252: * something nasty and unexpected happened. Switch to read-only
1276: * something which suggests there was a real read problem. E.g., %-EIO. Or a
linux-master/drivers/mtd/ubi/io.c
231: * Note, in case of an error, it is possible that something was still written
432: * physical eraseblock which means something is wrong with it.
linux-master/drivers/mtd/ubi/kapi.c
528: * something was still written to the flash media, but that may be some
linux-master/drivers/mtd/ubi/misc.c
132: * something else was also found.
linux-master/drivers/mtd/ubi/ubi-media.h
130: * version, the image is rejected. This may be useful in future if something
linux-master/drivers/mtd/ubi/wl.c
932: * something else. @e1 was not changed, so return it back. @e2 might
linux-master/drivers/net/arcnet/arcnet.c
511: * non-reboot way to recover if something goes wrong.
858: int recbuf, status, diagstatus, didsomething, boguscount;
895: didsomething = 0;
915: /* RX is inhibited - we must have received something.
935: didsomething++;
947: didsomething++;
995: didsomething++;
1029: didsomething++;
1097: if (didsomething)
1099: } while (--boguscount && didsomething);
linux-master/drivers/net/arcnet/com90xx.c
277: /* Stage 4: something of a dummy, to report the shmems that are
linux-master/drivers/net/bonding/bond_3ad.c
1382: /* check if there is something to send */
linux-master/drivers/net/bonding/bond_alb.c
326: /* we didn't find anything after the current or we have something
linux-master/drivers/net/bonding/bond_main.c
2805: * inspection, then (if inspection indicates something needs to be done)
3477: * in something like xor mode, there is nothing we can
linux-master/drivers/net/can/grcan.c
744: /* Pass on error frame if something to report,
linux-master/drivers/net/can/sja1000/peak_pcmcia.c
354: /* real write only if something has changed in ccr */
linux-master/drivers/net/dsa/lan9303-core.c
499: * and the IDs are 0-1-2, else it contains something different from
1321: /* On this device, we are only interested in doing something here if
linux-master/drivers/net/dsa/microchip/ksz9477_acl.c
288: /* we have something linked without a valid matching
754: /* create a backup of the ACL entries, if something goes wrong
linux-master/drivers/net/dsa/mv88e6xxx/chip.c
1843: * regular ATU move operation. Until we have something
linux-master/drivers/net/dsa/mv88e6xxx/devlink.c
511: * @resvd: Reserved. In case we forgot something.
linux-master/drivers/net/dsa/realtek/rtl8366rb.c
1206: * connected to something exotic such as fiber, then this might
linux-master/drivers/net/dsa/sja1105/sja1105_main.c
1709: * found something.
linux-master/drivers/net/dsa/sja1105/sja1105_vl.c
264: * In TTEthernet, routing is something that needs to be done manually for each
linux-master/drivers/net/eql.c
96: * scheduler was torn out and replaced with something smarter
linux-master/drivers/net/ethernet/3com/3c589_cs.c
400:/* Set transceiver type, perhaps to something other than what the user
linux-master/drivers/net/ethernet/3com/3c59x.c
978: * initialized yet). So we blindly assume something was
linux-master/drivers/net/ethernet/8390/axnet_cs.c
756: you have found something that needs changing. -- PG
938: /* Try to restart the card. Perhaps the user has fixed something. */
linux-master/drivers/net/ethernet/8390/etherh.c
450: * there is non-reboot way to recover if something goes wrong.
linux-master/drivers/net/ethernet/8390/lib8390.c
23: you have found something that needs changing. -- PG
285: /* Try to restart the card. Perhaps the user has fixed something. */
linux-master/drivers/net/ethernet/8390/stnic.c
282:/* This function resets the STNIC if something screws up. */
linux-master/drivers/net/ethernet/8390/wd.c
399: /* Set up the ASIC registers, just in case something changed them. */
linux-master/drivers/net/ethernet/adaptec/starfire.c
1510: * Maybe I missed something -- corrections are welcome.
linux-master/drivers/net/ethernet/agere/et131x.c
566: * something is broken).
2440: /* If there is something in this element, lets get a
3473: * something bad has occurred. A reset might be the thing to do.
3484: * should never see this, if it does, something serious is
linux-master/drivers/net/ethernet/alteon/acenic.c
1433: * *something* even before the CPU is started.
2080: * We are guaranteed that there is something in ring, so that
linux-master/drivers/net/ethernet/amd/nmclan_cs.c
1220: card's SRAM fast enough. If this happens, something is
linux-master/drivers/net/ethernet/amd/pds_core/auxbus.c
233: * VF, it just means something else needs to happen with it.
linux-master/drivers/net/ethernet/atheros/alx/main.c
88: * When DMA RX address is set to something like
linux-master/drivers/net/ethernet/atheros/atl1c/atl1c_main.c
1769: /* When DMA RX address is set to something like
linux-master/drivers/net/ethernet/atheros/atlx/atl1.c
2453: * something scheduled or not.
linux-master/drivers/net/ethernet/atheros/atlx/atl2.c
1226: * (if interval smaller than 5 seconds, something strange) */
linux-master/drivers/net/ethernet/broadcom/asp2/bcmasp_intf.c
1015: * something that the PHY driver will interpret and act on such
linux-master/drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c
5727: /* if status is non zero then perhaps something went wrong */
5732: /* ack status block only if something was actually handled */
9447: /* If SP settings didn't get completed so far - something
linux-master/drivers/net/ethernet/broadcom/genet/bcmmii.c
325: * meaning of the phy_interface_mode values to something that the PHY
linux-master/drivers/net/ethernet/broadcom/sb1250-mac.c
2278: * map/route interrupt (clear status first, in case something
2407: * something changed, restart the channel
linux-master/drivers/net/ethernet/broadcom/tg3.c
2963: /* The GPIOs do something completely different on 57765. */
linux-master/drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c
5408: * FW does not operate within its spec or something catastrophic
linux-master/drivers/net/ethernet/chelsio/cxgb4/l2t.c
115: * family, something made trivial by the separation of IP and IPv6 hash chains
linux-master/drivers/net/ethernet/chelsio/cxgb4/sge.c
98: * something to do only when the system experiences severe memory shortage.
1908: * do something else here.
4502: * a lot easier to fix in one place ... For now we do something very
linux-master/drivers/net/ethernet/chelsio/cxgb4/t4_hw.c
7381: * This is something of a crock since we're using fixed indices into
8679: /* something changed */
linux-master/drivers/net/ethernet/chelsio/cxgb4vf/sge.c
85: * has something to do only when the system experiences severe memory
1260: * do something else here.
linux-master/drivers/net/ethernet/chelsio/cxgb4vf/t4vf_hw.c
2018: /* something changed */
linux-master/drivers/net/ethernet/cirrus/cs89x0.c
822: there is non-reboot way to recover if something goes wrong.
1382: * the EEPROM the driver will always do *something* instead of
linux-master/drivers/net/ethernet/cirrus/mac89x0.c
282: there is non-reboot way to recover if something goes wrong.
linux-master/drivers/net/ethernet/faraday/ftgmac100.c
1255: * to re-check if there's something to process
1499: * something else if needed.
linux-master/drivers/net/ethernet/fealnx.c
1657: } else /* RXLSD did not find, something error */
linux-master/drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
602: * allocation procedure; if something failed before the mapping, the bp
1453: * If the current protocol is not something we support in this regard
linux-master/drivers/net/ethernet/freescale/gianfar.c
2902:/* Called when something needs to use the ethernet device
linux-master/drivers/net/ethernet/freescale/ucc_geth.c
3278:/* Called when something needs to use the ethernet device */
linux-master/drivers/net/ethernet/ibm/emac/core.c
92: * XXX This is something that needs to be reworked as we can have multiple
linux-master/drivers/net/ethernet/ibm/emac/core.h
329: * most optimal way as we don't have a way to say something like
linux-master/drivers/net/ethernet/ibm/emac/mal.c
412: * We _might_ need something more smart here to enforce polling
linux-master/drivers/net/ethernet/ibm/ibmveth.c
1028: /* if something goes wrong, free everything we just allocated */
linux-master/drivers/net/ethernet/intel/e100.c
1365: /* ack any interrupts, something could have been set */
linux-master/drivers/net/ethernet/intel/e1000/e1000_param.c
110: * Tx interrupt delay needs to typically be set to something non zero
linux-master/drivers/net/ethernet/intel/e1000e/netdev.c
1630: /* eth type trans needs skb->data to point to something */
linux-master/drivers/net/ethernet/intel/e1000e/param.c
37: * Tx interrupt delay needs to typically be set to something non-zero
linux-master/drivers/net/ethernet/intel/fm10k/fm10k_ethtool.c
832: /* If something changed we need to update the MRQC register. Note that
linux-master/drivers/net/ethernet/intel/fm10k/fm10k_mbx.c
233: * FIFO. In order to get something into a location other than just
linux-master/drivers/net/ethernet/intel/i40e/i40e_ethtool.c
989: /* if we got here and link is up something bad is afoot */
1289: * trying to set something that we do not support.
2191: /* this is to allow wr32 to have something to write to
linux-master/drivers/net/ethernet/intel/i40e/i40e_lan_hmc.c
333: * the full 2M memory but something smaller. By not filling out any
linux-master/drivers/net/ethernet/intel/i40e/i40e_main.c
2856: /* if something went wrong then set the changed flag so we try again */
12458: /* If the firmware does something weird during VSI init, we
15677: /* Select something other than the 802.1ad ethertype for the
16167: /* Unwind what we've done if something failed in the setup */
16473: * i40e_pci_error_detected - warning that something funky happened in PCI land
16477: * Called to warn that something happened and the error handling steps
linux-master/drivers/net/ethernet/intel/i40e/i40e_txrx.h
373: bool arm_wb; /* do something to arm write back */
linux-master/drivers/net/ethernet/intel/ice/ice_ethtool.c
2345: * trying to set something that we do not support.
3010: /* this is to allow wr32 to have something to write to
linux-master/drivers/net/ethernet/intel/ice/ice_main.c
472: /* if something went wrong then set the changed flag so we try again */
5670: * Called to warn that something happened on the PCI bus and the error handling
linux-master/drivers/net/ethernet/intel/ice/ice_switch.c
6024: /* Check if there is something to do */
linux-master/drivers/net/ethernet/intel/ice/ice_vf_lib.c
136: * active again. Similarly, if the VF has been disabled, this means something
linux-master/drivers/net/ethernet/intel/idpf/idpf_singleq_txrx.c
533: /* update budget only if we did something */
linux-master/drivers/net/ethernet/intel/idpf/idpf_virtchnl.c
472: * remain functional even though something really bad is
3495: /* if success we're done, we're only here if something bad happened */
linux-master/drivers/net/ethernet/intel/igb/igb_ethtool.c
2653: /* if we changed something we need to update flags */
linux-master/drivers/net/ethernet/intel/igc/igc_base.c
167: * firmware leaving the PHY's page select register set to something
169: * access something other than the intended register.
linux-master/drivers/net/ethernet/intel/igc/igc_ethtool.c
1183: /* if we changed something we need to update flags */
linux-master/drivers/net/ethernet/intel/igc/igc_ptp.c
915: * to something related to the system clocks (right now, only
linux-master/drivers/net/ethernet/intel/ixgbe/ixgbe_dcb_nl.c
134: /* verify there is something to do, if not then exit */
linux-master/drivers/net/ethernet/intel/ixgbe/ixgbe_ethtool.c
3023: /* if we changed something we need to update flags */
linux-master/drivers/net/ethernet/marvell/prestera/prestera_counter.c
415: * So pay attention when something changing.
linux-master/drivers/net/ethernet/marvell/prestera/prestera_router.c
833: /* Do hw update only if something changed to prevent nh flap */
linux-master/drivers/net/ethernet/mellanox/mlx4/cmd.c
477: * We use writel (instead of something like memcpy_toio)
linux-master/drivers/net/ethernet/mellanox/mlx4/main.c
3023: * write something like (i + 1) % eqs_per_port == 0.
linux-master/drivers/net/ethernet/mellanox/mlx5/core/en/xsk/tx.c
89: /* TX will get stuck until something wakes it up by
linux-master/drivers/net/ethernet/mellanox/mlxsw/core.c
3341: * MLXSW_RESOURCES_TABLE_END_ID, something went bad in the FW.
linux-master/drivers/net/ethernet/micrel/ks8851_common.c
89: * not currently specify the exact sequence, we have chosen something
376: /* if something stopped the rx process, probably due to wanting
377: * to change the rx settings, then do something about restarting
linux-master/drivers/net/ethernet/microchip/enc28j60.c
1330: * there is non-reboot way to recover if something goes wrong.
linux-master/drivers/net/ethernet/microchip/lan966x/lan966x_main.h
139: * FDMA_ERROR, something went wrong, stop getting more frames
linux-master/drivers/net/ethernet/microchip/sparx5/sparx5_qos.c
561: * Also convert the weight to something the hardware
linux-master/drivers/net/ethernet/mscc/ocelot.c
2602: * something else which is no longer current.
linux-master/drivers/net/ethernet/natsemi/natsemi.c
1154: /* renegotiate if something changed */
1361: /* found something! */
linux-master/drivers/net/ethernet/natsemi/sonic.c
94: * there is non-reboot way to recover if something goes wrong.
linux-master/drivers/net/ethernet/netronome/nfp/bpf/jit.c
331: /* NFP shift instruction has something special. If shift direction is
3905: /* Return as soon as something doesn't match */
linux-master/drivers/net/ethernet/netronome/nfp/bpf/main.h
503: * @error: error code if something went wrong
linux-master/drivers/net/ethernet/netronome/nfp/bpf/offload.c
270: * and we didn't byte swap something non-byte swap neutral.
linux-master/drivers/net/ethernet/netronome/nfp/flower/action.c
1157: /* csum action requests recalc of something we have not fixed */
linux-master/drivers/net/ethernet/netronome/nfp/flower/offload.c
782: /* Reject merge if sub_flow2 matches on something that is not matched
linux-master/drivers/net/ethernet/netronome/nfp/nfp_net.h
820:/* Flush posted PCI writes by reading something without side effects */
linux-master/drivers/net/ethernet/netronome/nfp/nfp_net_ethtool.c
1281: /* Only refresh if we did something */
2281: /* Only refresh if we did something */
linux-master/drivers/net/ethernet/packetengines/hamachi.c
1046: /* We could do something here... nah. */
linux-master/drivers/net/ethernet/pensando/ionic/ionic_lif.c
3612: * device address, it was set by something earlier and we're
linux-master/drivers/net/ethernet/qlogic/qed/qed_dev.c
1491: /* Make sure after we reserve there's something left */
4498: cdev->num_ports_in_engine = 1; /* Default to something */
linux-master/drivers/net/ethernet/qlogic/qed/qed_iwarp.c
2167: if (!fpdu) { /* something corrupt with cid, post rx back */
linux-master/drivers/net/ethernet/qlogic/qed/qed_sriov.c
5144: * flip so that we'll end up configuring something that's not
linux-master/drivers/net/ethernet/qlogic/qede/qede_filter.c
2055: /* Translate the flow specification into something fittign our DB */
linux-master/drivers/net/ethernet/qualcomm/emac/emac-sgmii.c
162: * decode errors in a row, then assume that something
linux-master/drivers/net/ethernet/realtek/atp.c
425: there is non-reboot way to recover if something goes wrong.
linux-master/drivers/net/ethernet/seeq/ether3.c
395: * there is non-reboot way to recover if something goes wrong.
linux-master/drivers/net/ethernet/seeq/ether3.h
166: int broken; /* 0 = ok, 1 = something went wrong */
linux-master/drivers/net/ethernet/seeq/sgiseeq.c
33: * If you want speed, you do something silly, it always has worked for me. So,
520: /* Only check for tx acks if we have something queued. */
linux-master/drivers/net/ethernet/sfc/ef100_tx.c
503: /* If we're not expecting another transmit and we had something to push
linux-master/drivers/net/ethernet/sfc/efx_common.c
1311: * think we can't offload something that we maybe could have.
linux-master/drivers/net/ethernet/sfc/falcon/farch.c
1758:/* Hard maximum search limit. Hardware will time-out beyond 200-something.
linux-master/drivers/net/ethernet/sfc/siena/efx_common.c
1328: * think we can't offload something that we maybe could have.
linux-master/drivers/net/ethernet/sfc/siena/farch.c
1827:/* Hard maximum search limit. Hardware will time-out beyond 200-something.
linux-master/drivers/net/ethernet/sfc/siena/tx.c
192: /* If we're not expecting another transmit and we had something to push
334: /* If we're not expecting another transmit and we had something to push
linux-master/drivers/net/ethernet/sfc/tx.c
405: /* If we're not expecting another transmit and we had something to push
542: /* If we're not expecting another transmit and we had something to push
linux-master/drivers/net/ethernet/sgi/ioc3-eth.c
489: * with such error interrupts if something really goes wrong, so we might
linux-master/drivers/net/ethernet/sis/sis900.c
1705: /* something strange happened !!! */
linux-master/drivers/net/ethernet/smsc/smc9194.c
897: /* check if the revision register is something that I recognize.
linux-master/drivers/net/ethernet/smsc/smc91c92_cs.c
1612: Set transceiver type, perhaps to something other than what the user
linux-master/drivers/net/ethernet/smsc/smc91x.c
299: * This seems to be undocumented, but something the original
358: * to something else than bank 2 without proper locking against
1899: * check if the revision register is something that I
linux-master/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
362: * described assume this is the case since there must be something
linux-master/drivers/net/ethernet/sun/sungem.c
2544: * advertise set, we need to return something sensible so
linux-master/drivers/net/ethernet/sun/sunhme.c
766: /* Ooops, something bad happened, go to force
1626: /* Driver error, tried to transmit something larger
1753: * condition is triggered, the happy meal expects you to do something reasonable
linux-master/drivers/net/ethernet/toshiba/spider_net.c
1848: * to generate spider_fw.bin, if you have sequencer programs with something
linux-master/drivers/net/ethernet/toshiba/tc35815.c
1214: * there is non-reboot way to recover if something goes wrong.
linux-master/drivers/net/ethernet/tundra/tsi108_eth.c
1647: * something changes, or to have the Tsi108 automatically communicate
linux-master/drivers/net/ethernet/xilinx/ll_temac_main.c
715: /* hash together the state values to decide if something has changed */
linux-master/drivers/net/ethernet/xilinx/xilinx_emaclite.c
890: /* hash together the state values to decide if something has changed */
linux-master/drivers/net/ethernet/xircom/xirc2ps_cs.c
983: * is this something to worry about?
linux-master/drivers/net/geneve.c
1205: /* MTU range: 68 - (something less than 65535) */
linux-master/drivers/net/hamradio/6pack.c
859: prio command. If DCD has not been set before, something in the
linux-master/drivers/net/hamradio/baycom_epp.c
812: * there is non-reboot way to recover if something goes wrong.
linux-master/drivers/net/hamradio/hdlcdrv.c
430: * there is non-reboot way to recover if something goes wrong.
linux-master/drivers/net/hamradio/scc.c
113: NB -- if you find errors, change something, please let me know
350: if(scc->rx_buff != NULL) /* did we receive something? */
590: /* CRC okay, frame ends on 8 bit boundary and received something ? */
linux-master/drivers/net/hippi/rrunner.c
83: * stack will need to know about I/O vectors or something similar.
linux-master/drivers/net/ifb.c
396: * Prefer something like : ip link add ifb10 numtxqueues 8 type ifb
linux-master/drivers/net/ipa/gsi_reg.h
25: * Each register type is duplicated for a number of instances of something.
linux-master/drivers/net/ipa/gsi_trans.c
728: * it to something a little less than that). By allocating a
linux-master/drivers/net/ipa/ipa_cmd.c
26: * An immediate command is generally used to request the IPA do something
linux-master/drivers/net/ipa/ipa_reg.h
25: * instances of something. For example, each IPA endpoint has an set of
linux-master/drivers/net/phy/adin.c
788: /* If we get a read error something may be wrong */
linux-master/drivers/net/phy/fixed_phy.c
107: * If something weird is required to be done with link/speed,
linux-master/drivers/net/phy/phy_device.c
368: * that something went wrong and we should most likely be using
2424: /* Only restart aneg if we are advertising something different
linux-master/drivers/net/phy/phylink.c
1257: * and then restart AN if it indicates something changed. Otherwise, we do
linux-master/drivers/net/phy/qsemi.c
63: * ...or something. The current value sets three
linux-master/drivers/net/ppp/ppp_generic.c
140: int nxchan; /* next channel to send something on */
linux-master/drivers/net/pse-pd/pd692x0.c
795: /* Read until we get something */
linux-master/drivers/net/slip/slip.c
1428: /* I think we need not something else */
linux-master/drivers/net/vmxnet3/vmxnet3_ethtool.c
1002: /* if we changed something we need to update flags */
linux-master/drivers/net/wan/farsync.c
506:/* Most common debug activity is to print something if the corresponding bit
1314: /* There is something to send
2298: * firmware detects something different later (should never happen)
linux-master/drivers/net/wireguard/selftest/allowedips.c
597: * if something goes wrong.
linux-master/drivers/net/wireguard/send.c
410: /* If we're exiting because there's something wrong with the key, it
linux-master/drivers/net/wireguard/socket.c
278: * CPUs wind up writing the same thing or something slightly different,
linux-master/drivers/net/wireless/ath/ath10k/htt_rx.c
453: * refill the rx ring with 1 PPDU's worth of rx buffers (something
455: * (something like 3 buffers). Consequently, we'll rely on the txrx
3329: * better to report something than nothing though. This
linux-master/drivers/net/wireless/ath/ath10k/mac.c
10176: * something that vdev_ids can't reach so that we don't stop the queue
linux-master/drivers/net/wireless/ath/ath10k/spectral.h
26: * something else.
linux-master/drivers/net/wireless/ath/ath11k/ahb.c
25: /* TODO: Should we change the compatible string to something similar
linux-master/drivers/net/wireless/ath/ath11k/spectral.h
17: * something else.
linux-master/drivers/net/wireless/ath/ath5k/attach.c
101: * -ENODEV if the device is not supported or prints an error msg if something
linux-master/drivers/net/wireless/ath/ath5k/pcu.c
772: * at any time - this is something we can't avoid. If the TSF jumps to a
linux-master/drivers/net/wireless/ath/ath5k/phy.c
2021: * window or something, it's 2 for the middle
linux-master/drivers/net/wireless/ath/ath6kl/sdio.c
158: /* FIXME: looks like ugly workaround for something */
linux-master/drivers/net/wireless/ath/ath6kl/txrx.c
596: * Under normal WMI if this is getting full, then something
1180: * Is the cur frame duplicate or something beyond our window(hold_q
linux-master/drivers/net/wireless/ath/ath9k/common-spectral.c
67: /* Don't try to read something outside the read buffer
109: /* Don't try to read something outside the read buffer
linux-master/drivers/net/wireless/ath/ath9k/common-spectral.h
26: * something else.
linux-master/drivers/net/wireless/ath/carl9170/rx.c
458: /* TODO: we could do something with phy_errors */
linux-master/drivers/net/wireless/ath/wil6210/rx_reorder.c
195: * If it is first but there's something stored, we may be able
linux-master/drivers/net/wireless/broadcom/b43/Kconfig
12: Check "lspci" for something like
linux-master/drivers/net/wireless/broadcom/b43/main.c
2737: * until it turns out to be in major conflict with something new. */
linux-master/drivers/net/wireless/broadcom/b43/phy_g.c
1926: /* This does something with the Analog... */
2973: /* So do we finally need to adjust something in hardware? */
linux-master/drivers/net/wireless/broadcom/b43/phy_lcn.c
305: /* TODO: something more? */
linux-master/drivers/net/wireless/broadcom/brcm80211/brcmfmac/firmware.c
608: /* something fishy here so bail out early */
linux-master/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c
3695: /* If there is something, make like the ISR and
linux-master/drivers/net/wireless/broadcom/brcm80211/brcmsmac/main.c
1422: /* something changed, cache the new value */
3587: * BMAC_NOTE: This is something that should be fixed
linux-master/drivers/net/wireless/intel/ipw2x00/ipw2100.c
2901: "something else: ids %d=%d.\n",
2937: "something else: ids %d=%d.\n",
6042: * those values that need to be something else */
linux-master/drivers/net/wireless/intel/iwlegacy/4965-mac.c
2516: if (sh < 0) /* tbw something is wrong with indices */
linux-master/drivers/net/wireless/intel/iwlegacy/4965.h
430: * something is wrong ... just use 0.
linux-master/drivers/net/wireless/intel/iwlegacy/common.c
2199: * which stations are active in the ucode. Call when something
5410: * To do that, remove code from il_set_rate() and put something
5490: * If we have something to service, the tasklet will re-enable ints.
5491: * If we *don't* have something, we'll re-enable before leaving here. */
linux-master/drivers/net/wireless/intel/iwlwifi/dvm/main.c
1917: * If firmware keep reloading, then it indicate something
linux-master/drivers/net/wireless/intel/iwlwifi/dvm/sta.c
603: * which stations are active in the ucode. Call when something
linux-master/drivers/net/wireless/intel/iwlwifi/iwl-dbg-tlv.c
558: * something. Because of DIV_ROUND_UP(), pages will never go
linux-master/drivers/net/wireless/intel/iwlwifi/iwl-drv.c
1641: * Someone is trying to debug something and he won't
linux-master/drivers/net/wireless/intel/iwlwifi/iwl-trans.h
31: * mechanisms to make the HW do something. It is not completely stateless but
linux-master/drivers/net/wireless/intel/iwlwifi/mei/iwl-mei.h
379: * Return: 0 unless something went wrong. It is illegal to call any
linux-master/drivers/net/wireless/intel/iwlwifi/mei/trace-data.h
70: * If you add something here, add a stub in case
linux-master/drivers/net/wireless/intel/iwlwifi/mei/trace.h
64: * If you add something here, add a stub in case
linux-master/drivers/net/wireless/intel/iwlwifi/mvm/coex.c
429: /* FIXME: TCM load per interface? or need something per link? */
447: /* FIXME: TCM load per interface? or need something per link? */
linux-master/drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c
382: * something getting messed up, the command read from the FIFO
linux-master/drivers/net/wireless/intel/iwlwifi/mvm/phy-ctxt.c
194: * only if something in the configuration changed: in case that this is the
linux-master/drivers/net/wireless/intel/iwlwifi/mvm/rxmq.c
292: * filtered could be replayed, or something like that, and
linux-master/drivers/net/wireless/intel/iwlwifi/mvm/scan.c
2663: * we need to stop something. Prefer stopping regular
linux-master/drivers/net/wireless/intel/iwlwifi/pcie/rx.c
2180: * If we have something to service, the tasklet will re-enable ints.
2181: * If we *don't* have something, we'll re-enable before leaving here.
linux-master/drivers/net/wireless/intel/iwlwifi/pcie/trans.c
2110: /* in this case, something else already removed the device */
linux-master/drivers/net/wireless/intel/iwlwifi/pcie/tx.c
606: /*Upon error, free only if we allocated something */
linux-master/drivers/net/wireless/marvell/libertas/cfg.c
1534: /* actually compare if something has changed ... */
1585: * - we've not kzallec() something when we've added a key at
linux-master/drivers/net/wireless/purelifi/plfxlc/usb.c
708: /* Either something really bad happened, or
815: /* Either something really bad happened, or
linux-master/drivers/net/wireless/ralink/rt2x00/rt2x00dev.c
1309: * Perhaps we can add something smarter here,
linux-master/drivers/net/wireless/ralink/rt2x00/rt2x00link.c
20: * When we lack RSSI information return something less then -80 to
linux-master/drivers/net/wireless/ralink/rt2x00/rt2x00queue.h
26: * be something around 3840 bytes.
90: * Note that this pointer could point to something outside
linux-master/drivers/net/wireless/ralink/rt2x00/rt2x00usb.c
317: /* TODO: report something more appropriate than IO_FAILED. */
linux-master/drivers/net/wireless/realtek/rtl818x/rtl8180/dev.c
1458: /* TODO: should we do something ? */
linux-master/drivers/net/wireless/realtek/rtlwifi/core.c
161: * but stop with RFOFF may cause something wrong,
1652: /* <5> tell mac80211 do something: */
linux-master/drivers/net/wireless/realtek/rtlwifi/ps.c
261: * nic_on may something wrong, like adhoc TP
linux-master/drivers/net/wireless/realtek/rtlwifi/rtl8192cu/trx.c
365: /* TODO: Error recovery. drop this skb or something. */
linux-master/drivers/net/wireless/realtek/rtlwifi/rtl8723be/hw.c
1419: * root cause is not clear now, is something
linux-master/drivers/net/wireless/st/cw1200/wsm.c
1186: /* First check if we really need to do something.
linux-master/drivers/net/wireless/ti/wl12xx/scan.c
332: /* don't stop scanning automatically when something is found */
linux-master/drivers/net/wireless/ti/wl18xx/scan.c
201: /* don't stop scanning automatically when something is found */
linux-master/drivers/net/wireless/ti/wlcore/tx.c
1081: /* only reset the queues if something bad happened */
linux-master/drivers/net/wireless/zydas/zd1211rw/zd_usb.c
1419: /* Either something really bad happened, or we're just dealing with
1431: /* Just in case something has gone wrong! */
linux-master/drivers/net/wwan/iosm/iosm_ipc_mux_codec.c
1377: /* Is something pending in UL and flow ctrl off */
linux-master/drivers/ntb/test/ntb_perf.c
51: * Assuming $DBG_DIR is something like:
linux-master/drivers/ntb/test/ntb_pingpong.c
56: * Assuming $DBG_DIR is something like:
linux-master/drivers/ntb/test/ntb_tool.c
56: * Assuming $DBG_DIR is something like:
linux-master/drivers/nvdimm/pmem.c
342: * happen unless something else went wrong.
linux-master/drivers/nvme/host/core.c
731: * For something we're not in a state to send to the device the default action
linux-master/drivers/nvme/host/fc.c
375: /* found an lport, but something about its state is bad */
686: /* found an rport, but something about its state is bad */
2650: * target whenever it posts something to the corresponding SQ. When an
3898: * As we need something to post FC-specific udev events to,
linux-master/drivers/nvme/host/fc.h
219: * something other than Association (e.g. 0).
linux-master/drivers/nvmem/microchip-otpc.c
97: * Payload size varies. The memory footprint is something as follows:
linux-master/drivers/of/irq.c
86: * If you think of adding to the list for something *new*, think
linux-master/drivers/parisc/iosapic.c
378:** Return the IRT entry in case we need to look something else up.
467: /* Convert pcidev INTR_PIN into something we
linux-master/drivers/parisc/lba_pci.c
1507: But it doesn't. Still missing something. *sigh*
linux-master/drivers/parport/TODO-parport
13: bits when they have something to say. We should read out and deal
linux-master/drivers/parport/ieee1284_ops.c
6: * of doing something, they can provide their own routines (and put
linux-master/drivers/pci/access.c
168: * just inadvertently cleared something we shouldn't have.
linux-master/drivers/pci/controller/pci-aardvark.c
726: * determining that something is wrong with the target of the
linux-master/drivers/pci/controller/pci-hyperv.c
3650: * specs. Pull it from the instance ID, to get something usually
3656: * domain used by Gen1 VMs for something that looks like a physical
linux-master/drivers/pci/controller/pci-mvebu.c
498: * If something tries to change the window while it is enabled
1564: * reality has something like N fully independent host bridges
linux-master/drivers/pci/controller/pci-xgene-msi.c
340: * something else has been made pending in the meantime
linux-master/drivers/pci/hotplug/cpqphp_ctrl.c
2576: /* Check if we were able to split something off */
2588: /* Check if we were able to split something off */
2627: /* Check if we were able to split something off */
2639: /* Check if we were able to split something off */
2679: /* Check if we were able to split something off */
2691: /* Check if we were able to split something off */
2838: * a bridge and the pin is tied to something that's
2843: /* We have to share with something already set up */
linux-master/drivers/pci/hotplug/cpqphp_nvram.c
447: * In that case, the driver would incorrectly store something
linux-master/drivers/pci/hotplug/ibmphp_core.c
937: err("something wrong when powering up... please see below for details\n");
linux-master/drivers/pci/hotplug/ibmphp_pci.c
357: /* not sure if i need this. per scott, said maybe need * something like this
1614: err("strange, cannot find bus which is supposed to be at the system... something is terribly wrong...\n");
linux-master/drivers/pci/hotplug/ibmphp_res.c
593: /* didn't find a bus, something's wrong!!! */
979: /* didn't find a bus, something's wrong!!! */
1350: debug("something terribly wrong. Cannot find parent bus to the one to remove\n");
linux-master/drivers/pci/hotplug/pciehp_hpc.c
638: * until we've done something to handle it.
linux-master/drivers/pci/iov.c
792: * If it is already FIXED, don't change it, something
linux-master/drivers/pci/quirks.c
633: * BAR0 should be 8 bytes; instead, it may be set to something like 8k
linux-master/drivers/pci/vgaarb.c
394: * released something.
970: * multi-GPU laptops do something saner, and desktops won't have any
1029: * poll : event if something change on any card (not just the target)
linux-master/drivers/pcmcia/i82092.c
100: "Oops, you did something we didn't think of.\n");
linux-master/drivers/pcmcia/rsrc_nonstatic.c
636: * If we failed to find something suitable, ensure we fail.
linux-master/drivers/phy/cadence/cdns-dphy.c
347: * 1MHz clk (or something close).
linux-master/drivers/pinctrl/pinconf.c
287: * values, so they can be decoded to something meaningful.
linux-master/drivers/pinctrl/pinctrl-gemini.c
98: * - For the bits named *_ENABLE, once you DISABLE something, it simply cannot
101: * - For the bits named *_DISABLE, once you enable something, it cannot be
linux-master/drivers/pinctrl/pinctrl-single.c
230: * REVISIT: Reads and writes could eventually use regmap or something
linux-master/drivers/pinctrl/pinctrl-tb10x.c
643: * used for something else.
linux-master/drivers/pinctrl/pinmux.c
198: * pin_free() - release a single muxed in pin so something else can be muxed
linux-master/drivers/pinctrl/starfive/pinctrl-starfive-jh7100.c
153: * That is it should underflow and return something >= NR_GPIOS.
linux-master/drivers/pinctrl/sunplus/sppctl.c
130: * bits in mask-field should be set then you can write something to
linux-master/drivers/platform/chrome/wilco_ec/event.c
186: * used to notify different threads when something has changed, plus a flag
linux-master/drivers/platform/goldfish/goldfish_pipe.c
29: * It is intended to be as simple as something like:
69: * Update this when something changes in the driver's behavior so the host
426: * something.
441: * something on one of the previous iterations.
linux-master/drivers/platform/surface/aggregator/controller.c
1655: * ssam_controller_stateunlock, but something like ssam_client_link
linux-master/drivers/platform/surface/aggregator/ssh_packet_layer.c
436: /* Check if there actually is something to corrupt. */
linux-master/drivers/platform/x86/apple-gmux.c
882: * reports something higher so that it can be fixed.
linux-master/drivers/platform/x86/asus-laptop.c
1717: * asus_model_match() and try something completely different.
linux-master/drivers/platform/x86/asus-wmi.c
2142: * If we get -EBUSY then something else is handling the PCI hotplug -
2924: * zero temperature, something is clearly wrong
linux-master/drivers/platform/x86/dell/dell_rbu.c
432: /* check to see if we have something to return */
464: /* check to see if we have something to return */
519: /* Incase something goes wrong when we are
linux-master/drivers/platform/x86/eeepc-laptop.c
867: * If we get -EBUSY then something else is handling the PCI hotplug -
linux-master/drivers/platform/x86/intel/Kconfig
190: will then remain awake until something triggers another suspend.
linux-master/drivers/platform/x86/msi-laptop.c
716: /* Do something with blocked...*/
linux-master/drivers/platform/x86/p2sb.c
223: * initcall dependencies looks something like this:
linux-master/drivers/platform/x86/sony-laptop.c
365: /* If there is something in the fifo schedule next release. */
linux-master/drivers/platform/x86/think-lmi.c
1201: /* Check there is actually something to save */
linux-master/drivers/platform/x86/thinkpad_acpi.c
2168: /* Give people a chance to notice they are doing something that
3490: * for userspace to do something even remotely sane */
3781: pr_crit("THERMAL ALARM: a sensor reports something is too hot!\n");
3786: pr_alert("THERMAL EMERGENCY: a sensor reports something is extremely hot!\n");
6405: * WARNING: The X61 has been verified to use HBRV for something else, so
7800: * something else in offset 0x84 according to the ACPI DSDT. Other
7959: /* something changed the HFSP regisnter since
linux-master/drivers/platform/x86/toshiba_acpi.c
1605: * video setting if something changed.
linux-master/drivers/pmdomain/bcm/raspberrypi-power.c
97: * to turn off something that we haven't ourselves turned on.
linux-master/drivers/pnp/isapnp/compat.c
53: if (from->card != card) /* something is wrong */
linux-master/drivers/power/supply/ab8500_chargalg.c
1223: * It is called periodically or when something happens that will
linux-master/drivers/power/supply/ab8500_charger.c
3626: /* Create something that will match the subdrivers when we bind */
linux-master/drivers/power/supply/ab8500_fg.c
964: * trusted so return an error unless we must return something here, as
linux-master/drivers/power/supply/bq27xxx_battery.c
1527: * Or < 0 if something fails.
1546: * Or < 0 if something fails.
1572: * Or < 0 if something fails.
1582: * Or < 0 if something fails.
1592: * Or < 0 if something fails.
1602: * Or < 0 if something fails.
1640: * Or < 0 if something fails.
1665: * Or < 0 if something fails.
1691: * Or < 0 if something fails.
1709: * Return < 0 if something fails.
1815: * Or 0 if something fails.
1928: * Return < 0 if something fails.
1991: * Or < 0 if something fails.
linux-master/drivers/power/supply/cpcap-battery.c
359: * via device tree. If it turns out to be something device specific
linux-master/drivers/power/supply/ds2760_battery.c
505: * too inaccurate to rely on - spec say something ~15% failure.
linux-master/drivers/power/supply/surface_battery.c
317: * Warn if the unit has changed. This is something we genuinely don't
linux-master/drivers/pps/kapi.c
213: /* Wake up if captured something */
linux-master/drivers/pwm/pwm-microchip-core.c
324: * It is possible that something could have set the period_steps
linux-master/drivers/pwm/pwm-ntxec.c
104: * The case that something has previously set the duty cycle to zero
linux-master/drivers/pwm/pwm-renesas-tpu.c
272: * This could be calculated using something like:
linux-master/drivers/regulator/axp20x-regulator.c
1182: * something the regulator subsystem does not support.
linux-master/drivers/regulator/core.c
5639: * from a gpio extender or something else.
linux-master/drivers/regulator/helpers.c
309: * voltage by calling list_voltage() until it gets something in bounds
linux-master/drivers/remoteproc/remoteproc_core.c
1508: * something went really wrong and we must complain.
linux-master/drivers/rtc/rtc-ab-b5ze-s3.c
452: * return an error if we get something after that limit.
linux-master/drivers/rtc/rtc-cmos.c
1054: * need to do something about other clock frequencies.
linux-master/drivers/rtc/rtc-ds1374.c
245: * (i.e. not something that we'd rather the caller know about via
linux-master/drivers/rtc/rtc-ds1685.c
1283: * Not all platforms have the IRQF pin tied to something. If not, the
1298: /* Check to see if something came back. */
linux-master/drivers/rtc/rtc-gamecube.c
251: * rebooting properly, so wiiubrew.org must be missing something.
linux-master/drivers/rtc/rtc-pcf2123.c
15: * should look something like:
linux-master/drivers/s390/block/dasd.c
1433: * If we already use the full opm, something is amiss, and we
2661: * is waiting for something that may not come reliably, (e.g. a state
linux-master/drivers/s390/block/dasd_alias.c
31: * something, this function should get faster or better, the rest has just
177: * Negative return code indicates that something went wrong (e.g. -ENOMEM)
linux-master/drivers/s390/block/dasd_eckd.c
723: * Only returns something useful if dasd_eckd_cdl_special is true
linux-master/drivers/s390/char/tape_3590.c
1340: * First check all RC-QRCs where we want to do something special
linux-master/drivers/s390/cio/device.h
25: /* states to wait for i/o completion before doing something */
linux-master/drivers/s390/cio/device_fsm.c
1082: /* states to wait for i/o completion before doing something */
linux-master/drivers/s390/cio/vfio_ccw_cp.c
726: * the problem if something does break.
linux-master/drivers/s390/crypto/ap_bus.h
300: * was no ap_queue device with this qid found. When something is
linux-master/drivers/s390/crypto/zcrypt_api.c
72: * Returns true if something has changed (for example the
linux-master/drivers/s390/net/qeth_core_main.c
3701: * happens something is really wrong -> recover */
6856: /* something went wrong. save changed features and return error */
linux-master/drivers/s390/virtio/virtio_ccw.c
1176: /* Don't poke around indicators, something's wrong. */
linux-master/drivers/sbus/char/uctrl.c
247:/* Wait for something to read, read it, then clear the bit */
linux-master/drivers/scsi/53c700.c
788: * ACK). If we want to do something else, we call that routine in
1949: * reset via sg or something */
linux-master/drivers/scsi/NCR5380.c
1956: * If we get something weird that we aren't expecting,
linux-master/drivers/scsi/NCR5380.h
184: * Convert status register phase to something we can use to set phase in
linux-master/drivers/scsi/aacraid/commsup.c
1143: * If we are waiting on something and this happens to be
1196: * waiting on something else, setup to wait on a Config Change.
1300: * If we are waiting on something and this happens to be
linux-master/drivers/scsi/aacraid/rx.c
271: * Notify the i960 that something it probably cares about has
linux-master/drivers/scsi/aacraid/src.c
347: * Notify the i960 that something it probably cares about has
linux-master/drivers/scsi/advansys.c
11338: * AscGetChipCfgMsw, but I may have overlooked something,
linux-master/drivers/scsi/aha152x.c
2093: * something went wrong, if there's something left in the fifos
linux-master/drivers/scsi/aha1542.c
315: * probably do something special, but for now just printing a message
316: * is sufficient. A SCSI reset detected is something that we really
linux-master/drivers/scsi/aha1740.c
457: something is broken; since there is no way to return an
linux-master/drivers/scsi/aic7xxx/aic79xx.seq
456: * something other than an 8byte aligned boundary. In
1172: * so, check to see if there is a residual or the status byte is something
linux-master/drivers/scsi/aic7xxx/aic79xx_core.c
2830: * mesg_out to something other than NOP.
linux-master/drivers/scsi/aic7xxx/aic7xxx.seq
1604: * is a residual or the status byte is something other than STATUS_GOOD (0).
linux-master/drivers/scsi/aic7xxx/aic7xxx_core.c
1694: * mesg_out to something other than MSG_NOP.
linux-master/drivers/scsi/aic7xxx/aicasm/aicasm_gram.y
1862: * Make sure that we aren't attempting to write something
linux-master/drivers/scsi/aic94xx/aic94xx_scb.c
468: * that the EH will wake up and do something.
linux-master/drivers/scsi/aic94xx/aic94xx_sds.c
547: u8 something_here[];
linux-master/drivers/scsi/arm/acornscsi.c
794: * but with untransferred buffers... If we don't do something, then
796: * It doesn't appear to be set to something meaningful by the higher
1568: /* tag queue reconnect... message[1] = queue tag. Print something to indicate something happened! */
linux-master/drivers/scsi/arm/acornscsi.h
336: unsigned char xfer_required:1; /* set if we need to transfer something */
linux-master/drivers/scsi/cxlflash/sislite.h
137: * would happen if a frame is dropped and something times out.
linux-master/drivers/scsi/dc395x.c
2404: * something broke :-( */
4229: * them in in case something else needs them.
linux-master/drivers/scsi/esas2r/esas2r_int.c
490: * really something wrong with the hardware. The way
linux-master/drivers/scsi/hosts.c
434: * they actually do something sensible with such commands.
linux-master/drivers/scsi/hpsa.c
2832: /* Prevent subsequent unmap of something never mapped */
linux-master/drivers/scsi/ibmvscsi/ibmvfc.c
1100: * something bad like double completing it.
3340: * things we send. Make sure this response is to something we
3872: * things we send. Make sure this response is to something we
linux-master/drivers/scsi/ibmvscsi/ibmvscsi.c
1824: * things we send. Make sure this response is to something we
linux-master/drivers/scsi/ipr.c
4653: * We want to make sure we return something that places partitions
linux-master/drivers/scsi/isci/host.c
377: /* / @todo The driver did something wrong and we need to fix the condtion. */
linux-master/drivers/scsi/libfc/fc_exch.c
1273: * Send ACK_1 (or equiv.) indicating we received something.
linux-master/drivers/scsi/libfc/fc_fcp.c
497: * Indicate error to scsi-ml because something went wrong with the
linux-master/drivers/scsi/lpfc/lpfc_init.c
3182: /* We only do something if CMF is enabled */
3246: /* We only do something if CMF is enabled */
linux-master/drivers/scsi/mesh.c
1141: /* target wants to do something different:
linux-master/drivers/scsi/mesh.h
115:#define ERR_SEQERR 0x10 /* we did something the chip didn't like */
linux-master/drivers/scsi/mpt3sas/mpt3sas_base.c
2084: * something to use if the target device goes brain dead and tries
2661: * something to use if the target device goes brain dead and tries
linux-master/drivers/scsi/ncr53c8xx.c
7835: ** something important? :)
linux-master/drivers/scsi/nsp32.c
783: * something lock up! guess no connection.
linux-master/drivers/scsi/pm8001/pm8001_sas.c
1067: * here is that the drive is off doing something so
linux-master/drivers/scsi/qla1280.c
452: * met, but then again if we receive something like that from the
468: * insmod needs to find the variable and make it point to something
4268: /* set our host ID (need to do something about our two IDs) */
linux-master/drivers/scsi/qlogicfas408.h
39: something official */
99: where something crashed or gets stuck at and as a simple profiler) */
linux-master/drivers/scsi/script_asm.pl
669:# Handle SET and CLEAR instructions. Note that we should also do something
linux-master/drivers/scsi/scsi.c
413: * by the device it is now safe to ask for something bigger.
447: * by the device it is now safe to ask for something bigger.
linux-master/drivers/scsi/scsi_lib.c
88: * If the host/device isn't busy, assume that something actually
linux-master/drivers/scsi/scsi_sysfs.c
1686: * the target. Target will be held in CREATED state until something
linux-master/drivers/scsi/scsi_transport_iscsi.c
3937: * (like address or something else), calculate the remaining length
linux-master/drivers/scsi/scsicam.c
237: * If something went wrong, then apparently we have to return a geometry
linux-master/drivers/scsi/sr.c
252: * sense data indicating something other than media-not-present
linux-master/drivers/scsi/st.c
1815: in this request but still something left to write
2848: return 0; /* Should do something ? */
linux-master/drivers/scsi/storvsc_drv.c
1770: * This is DMA_BIDIRECTIONAL or something else we are never
linux-master/drivers/scsi/sym53c8xx_2/sym_hipd.c
78: * Print something that tells about extended errors.
2740: * a time. But when something bad happens on the SCSI BUS,
2765: * something really bad happens to a device, etc ...
4400: * The C code is currently trying to recover from something.
linux-master/drivers/scsi/sym53c8xx_2/sym_hipd.h
55: * by the platform specific code to something else.
linux-master/drivers/scsi/virtio_scsi.c
673: * controller or something on the host side other than the
linux-master/drivers/scsi/wd33c93.c
1166: * or two. Not sure why, or if I'm doing something wrong to
1187: * something when we get this interrupt - the question is 'what?'.
1686: * so we won't panic, but we will notify the user in case something really
linux-master/drivers/scsi/wd719x.c
26: * something goes wrong.
linux-master/drivers/siox/siox-core.c
163: * reset when something is wrong.
linux-master/drivers/soc/fsl/dpio/qbman-portal.c
1181: /* Before using valid-bit to detect if something is there, we have to
1234: * There's something there. Move "next_idx" attention to the next ring
1273: /* Before using valid-bit to detect if something is there, we have to
1326: * There's something there. Move "next_idx" attention to the next ring
linux-master/drivers/soc/fsl/qbman/qman.c
1384: * something related to QM_PIRQ_EQCI, this may need fixing.
linux-master/drivers/soc/fsl/qbman/qman_test_stash.c
82: * helper to run something on all cpus (can't use on_each_cpu(), as that invokes
linux-master/drivers/soc/fsl/qe/gpio.c
142: * something like qe_pio_controller. Someday.
linux-master/drivers/soc/rockchip/io-domain.c
163: * request something like a max of 3.6V when they really want 3.3V.
linux-master/drivers/soc/tegra/pmc.c
2870: * are not valid then something went badly wrong!
linux-master/drivers/spi/spi-aspeed-smc.c
452: * Restore initial value if something goes wrong else we could
linux-master/drivers/spi/spi-at91-usart.c
249: /* Enable RX interrupt if something fails and fallback to PIO */
linux-master/drivers/spi/spi-au1550.c
567: * while there is something to read from rx fifo
linux-master/drivers/spi/spi-dw-core.c
803: * the MMC SPI driver or something else.
linux-master/drivers/spi/spi-ep93xx.c
444: * If we got ROR (receive overrun) interrupt we know that something is
linux-master/drivers/spi/spi-geni-qcom.c
263: * times out then an abort times out is if something is blocking our
linux-master/drivers/spi/spi-loopback-test.c
558: /* if still not found then something has modified too much */
847: /* if it is 0, as we expected something else,
848: * then return something special
linux-master/drivers/spi/spi-mpc52xx.c
58: /* do. If something interesting happens */
linux-master/drivers/spi/spi-pxa2xx.c
722: /* We did something */
linux-master/drivers/spi/spi-slave-system-control.c
30: * The numbers are chosen to display something human-readable on two 7-segment
linux-master/drivers/spi/spi-stm32.c
973: * If overrun is detected, it means that something went wrong,
1077: * that something went wrong, so stop the current transfer
linux-master/drivers/spi/spi.c
2353: * sent before doing something. Is used by the spi-mem code to make sure SPI
linux-master/drivers/staging/fbtft/fbtft-core.c
1037: "%s: something is wrong. Shouldn't get here.\n", __func__);
linux-master/drivers/staging/media/atomisp/pci/atomisp_gmin_platform.c
1292: * if it founds something different than string, letting it
linux-master/drivers/staging/media/atomisp/pci/atomisp_v4l2.c
100: * be to replace this to something stored inside atomisp allocated
linux-master/drivers/staging/media/atomisp/pci/hmm/hmm_bo.c
454: * so, if this happened, something goes wrong.
linux-master/drivers/staging/media/atomisp/pci/sh_css.c
2422: * In practice this means something other than yuv_line or nv12.
linux-master/drivers/staging/media/av7110/av7110.c
2332: * I *think* HPS setting has something to do with the phase
linux-master/drivers/staging/media/av7110/budget-patch.c
389: // than leaving something unconfigured
534:** I *think* HPS setting has something to do with the phase
linux-master/drivers/staging/media/meson/vdec/codec_vp9.c
114: * - struct segmentation is for loop filter only (removed something)
linux-master/drivers/staging/media/tegra-video/vi.c
1767: * in case of something wrong during graph parsing and continue with
linux-master/drivers/staging/nvec/nvec.c
603: /* The EC did not request a read, so it send us something, read it */
linux-master/drivers/staging/rtl8712/rtl871x_mlme.c
1582: /* todo: if you want to do something io/reg/hw setting before join_bss,
linux-master/drivers/staging/rtl8723bs/core/rtw_mlme.c
2113: /* todo: if you want to do something io/reg/hw setting before join_bss, please add code here */
linux-master/drivers/staging/rtl8723bs/core/rtw_xmit.c
2521: /* timeout, do something?? */
linux-master/drivers/staging/rtl8723bs/hal/hal_com.c
644: /* TODO - Is something needed here? */
647: /* TODO - Is something needed here? */
linux-master/drivers/staging/rtl8723bs/hal/rtl8723bs_xmit.c
120: *_FAIL something error
357: *_FAIL something error
linux-master/drivers/staging/sm750fb/sm750_accel.c
97: * got something error
linux-master/drivers/target/target_core_transport.c
1926: * target_submit_prep or something similar must have been called on the cmd,
linux-master/drivers/tee/optee/ffa_abi.c
634: * eventual errors early in case something changes.
linux-master/drivers/tee/optee/optee_rpc_cmd.h
33: * If secure world needs to wait for something, for instance a mutex, it
linux-master/drivers/thunderbolt/nhi.c
1205: * segment as its NHI, if we can find *something* on that segment
linux-master/drivers/thunderbolt/switch.c
1277: * Returns true if the port had something (router, XDomain) connected
3596: /* Trigger wake when something is plugged in/out */
linux-master/drivers/thunderbolt/tunnel.c
419: * Returns true if there is something to be reserved and writes the
linux-master/drivers/tty/ipwireless/hardware.c
927: * return 1 if something has been received from hw
linux-master/drivers/tty/mips_ejtag_fdc.c
660: * have something with a GIC that routes the FDC IRQs (i.e. no sharing
linux-master/drivers/tty/mxser.c
213: see also ISA probe function before you change something */
linux-master/drivers/tty/n_hdlc.c
191: * Called when the line discipline is changed to something
linux-master/drivers/tty/serial/8250/8250_dma.c
118: /* we already checked empty fifo above, so there should be something */
linux-master/drivers/tty/serial/8250/8250_pci.c
881: * serial ports, or 0x1000 indicates *something*. This is not
linux-master/drivers/tty/serial/8250/8250_port.c
3415: * call it if we have saved something in the saved flags
linux-master/drivers/tty/serial/Kconfig
885: something like this to connect more than two modems to your Linux
linux-master/drivers/tty/serial/cpm_uart.h
92: /* something nasty happened */
108: /* something nasty happened */
linux-master/drivers/tty/serial/dz.c
279: * If something to do... (remember the dz has no output fifo,
linux-master/drivers/tty/serial/imx.c
841: /* If we received something, check for 0xff flood */
1203: /* If we received something, check for 0xff flood */
linux-master/drivers/tty/serial/ip22zilog.c
750: * > and I noticed that something is not right with reference
linux-master/drivers/tty/serial/mps2-uart.c
240: * So we keep this check in case something suspicious has happened.
linux-master/drivers/tty/serial/mxs-auart.c
1559: * If something went wrong, rollback.
linux-master/drivers/tty/serial/omap-serial.c
1237: * call it if we have saved something in the saved flags
linux-master/drivers/tty/serial/pmac_zilog.c
23: * - maybe put something right into uap->clk_divisor
linux-master/drivers/tty/serial/serial_core.c
1079: * If we're about to load something into the transmit
linux-master/drivers/tty/serial/sunzilog.c
816: * > and I noticed that something is not right with reference
linux-master/drivers/tty/serial/ucc_uart.c
224: /* something nasty happened */
243: /* something nasty happened */
linux-master/drivers/tty/tty_io.c
843: * The "cookie" is something that the ldisc read function can fill
847: * data or clears the cookie. The cookie may be something that the
1833: * something that needs to be handled for hangups.
linux-master/drivers/tty/tty_ldisc.c
465: * and we need something attached.
linux-master/drivers/tty/vt/vt.c
3839: * following resets all attributes to something sane.
linux-master/drivers/tty/vt/vt_ioctl.c
1167: * tell us if the process has gone or something else
1227: * tell us if the process has gone or something else
linux-master/drivers/uio/uio_hv_generic.c
93: * Callback from vmbus_event when something is in inbound ring.
linux-master/drivers/usb/atm/usbatm.c
1243: /* turn usbatm_[rt]x_process into something close to a no-op */
linux-master/drivers/usb/core/driver.c
617: /* this should never happen, don't release something that's not ours */
linux-master/drivers/usb/core/file.c
107: * Return: -EINVAL if something bad happens with trying to register a
linux-master/drivers/usb/core/hcd-pci.c
307: * context, normally "rmmod", "apmd", or something similar.
linux-master/drivers/usb/core/hcd.c
1201: /* Any status except -EINPROGRESS means something already started to
linux-master/drivers/usb/core/hub.c
1042: * physically unplugged and something is plugged in, the events will
3294: * if it was on it would indicate that something happened
linux-master/drivers/usb/dwc2/core.h
813: * frame even for things that only transfer very rarely, so something that runs
linux-master/drivers/usb/dwc2/gadget.c
494: * transmission and we have something to give it. The actual setup of
3176: /* this probably means something bad is happening */
4853: * to be something valid.
linux-master/drivers/usb/dwc2/hcd.c
5741: * We don't want to power off the PHY if something under the
linux-master/drivers/usb/dwc2/hcd.h
260: * @next_active_frame: (Micro)frame _before_ we next need to put something on
linux-master/drivers/usb/dwc2/hcd_queue.c
575: * This will schedule something on the main dwc2 schedule.
585: * already scheduled something on the low speed schedule and
586: * need to find something that matches on the high speed one.
1515: /* We'll schedule later when we have something to do */
linux-master/drivers/usb/early/ehci-dbgp.c
644: /* bomb out completely if something weird happened */
linux-master/drivers/usb/fotg210/fotg210-hcd.c
2432: /* if we're removing something not at the queue head,
linux-master/drivers/usb/gadget/composite.c
1586: * here, even though we know we've set it to something useful.
linux-master/drivers/usb/gadget/function/f_mass_storage.c
853: /* Did something go wrong with the transfer? */
linux-master/drivers/usb/gadget/function/u_serial.c
56: * for a telephone or fax link. And ttyGS2 might be something that just
535: * We only start I/O when something is connected to both sides of
linux-master/drivers/usb/gadget/function/u_tcm.h
41: * something sensible (e.g. probe/remove the composite).
linux-master/drivers/usb/gadget/legacy/ether.c
54: * A third option is also in use. Rather than CDC Ethernet, or something
linux-master/drivers/usb/gadget/legacy/zero.c
164: /* Normally the host would be woken up for something
linux-master/drivers/usb/gadget/udc/aspeed-vhub/ep0.c
310: * We are in data phase and there's no request, something is
linux-master/drivers/usb/gadget/udc/aspeed-vhub/epn.c
454: * may have to do something more complex here,
linux-master/drivers/usb/gadget/udc/at91_udc.c
294: * - clear SET_FX bits (setting them could change something)
295: * - set CLR_FX bits (clearing them could change something)
linux-master/drivers/usb/gadget/udc/atmel_usba_udc.c
1692: * do something here...
linux-master/drivers/usb/gadget/udc/bdc/bdc_udc.c
230:/* something changes on upstream port, handle it here */
linux-master/drivers/usb/gadget/udc/gr_udc.c
1232: * Handles interrupts from in endpoints. Returns whether something was handled.
1257: * Handles interrupts from out endpoints. Returns whether something was handled.
1311: * Handle state changes. Returns whether something was handled.
linux-master/drivers/usb/gadget/udc/lpc32xx_udc.c
1963: /* If there isn't a request waiting, something went wrong */
2753: * happen alot, something is wrong. */
linux-master/drivers/usb/host/ehci-hub.c
106: * but if something went wrong the port must not
linux-master/drivers/usb/host/ehci-omap.c
237: * context, normally "rmmod", "apmd", or something similar.
linux-master/drivers/usb/host/ehci-q.c
489: /* if we're removing something not at the queue head,
linux-master/drivers/usb/host/fhci-hub.c
93: /* Enable IDLE since we want to know if something comes along */
linux-master/drivers/usb/host/fhci-sched.c
436: /* Enable IDLE since we want to know if something comes along */
linux-master/drivers/usb/host/fhci-tds.c
518: * This routine is called when something wrong with the controller and
607: /* start transmit only if we have something in the TDs */
linux-master/drivers/usb/host/octeon-hcd.c
1907: * Without DMA we need to be careful to not schedule something
2797: * something wrong with the transfer. For example, PID
linux-master/drivers/usb/host/ohci-at91.c
273: * context, "rmmod" or something similar.
linux-master/drivers/usb/host/ohci-hcd.c
764: * was non-empty at that time, something is badly wrong with the
linux-master/drivers/usb/host/ohci-omap.c
322: * context, normally "rmmod", "apmd", or something similar.
linux-master/drivers/usb/host/ohci-pxa27x.c
500: * context, normally "rmmod", "apmd", or something similar.
linux-master/drivers/usb/host/ohci-q.c
307: * When the HC can't see the ED, something changes ED_UNLINK to one of:
323: /* To deschedule something from the control or bulk list, just
linux-master/drivers/usb/host/ohci-s3c2410.c
330: * context, normally "rmmod", "apmd", or something similar.
linux-master/drivers/usb/host/oxu210hp-hcd.c
2847: /* something else might have unlinked the qh by now */
linux-master/drivers/usb/host/uhci-debug.c
3: * UHCI-specific debugging code. Invaluable when something
linux-master/drivers/usb/host/uhci-hcd.c
475: "host controller process error, something bad happened!\n");
linux-master/drivers/usb/host/xhci-mem.c
1979: xhci_warn(xhci, "WARN something wrong with SW event ring dequeue ptr.\n");
2519: * something other than the default (~1ms minimum between interrupts).
linux-master/drivers/usb/host/xhci-ring.c
3018: xhci_warn(xhci, "WARN something wrong with SW event ring dequeue ptr\n");
linux-master/drivers/usb/host/xhci.c
2044: /* the HCD set up something wrong */
linux-master/drivers/usb/image/mdc800.c
1031: /* Clean driver up, when something fails */
linux-master/drivers/usb/misc/adutux.c
734: /* something prevented us from registering this driver */
linux-master/drivers/usb/misc/idmouse.c
365: /* something prevented us from registering this device */
linux-master/drivers/usb/misc/iowarrior.c
862: /* something prevented us from registering this driver */
linux-master/drivers/usb/misc/ldusb.c
730: /* something prevented us from registering this driver */
linux-master/drivers/usb/misc/legousbtower.c
816: /* something prevented us from registering this driver */
linux-master/drivers/usb/misc/usblcd.c
370: /* something prevented us from registering this driver */
linux-master/drivers/usb/misc/usbtest.c
1103: * usb_unlink_urb() is used to unlink something not at the
linux-master/drivers/usb/musb/musb_gadget.c
1813: * -EINVAL something went wrong (not driver)
linux-master/drivers/usb/musb/tusb6010.c
327: * mode), or low power Default-B sessions, something else supplies power.
linux-master/drivers/usb/serial/ark3116.c
693: * hardware bug or something.
linux-master/drivers/usb/serial/cyberjack.c
369: /* only do something if we have more data to send */
linux-master/drivers/usb/serial/cypress_m8.c
1038: /* something ugly is going on... */
linux-master/drivers/usb/serial/io_edgeport.c
653: /* tell the tty driver that something
793: /* tell the tty driver that something has changed */
1300: /* something went wrong */
1306: /* revert the credits as something bad happened. */
1780: * We could choose to do something else when Byte3 says
2114: /* something bad happened, let's free up the memory */
2155: /* something went wrong */
2229: /* something bad happened, let's free up the memory */
2316: /* something bad happened, let's free up the memory */
linux-master/drivers/usb/serial/iuu_phoenix.c
981: /* This is not UART related but IUU USB driver related or something */
linux-master/drivers/usb/serial/keyspan.c
1341: /* Now do something useful with the data */
1408: /* Now do something useful with the data */
2191: /* only do something if we have a bulk out endpoint */
2487: /* only do something if we have a bulk out endpoint */
linux-master/drivers/usb/serial/mxuport.c
423: * When something interesting happens, modem control lines XON/XOFF
linux-master/drivers/usb/serial/oti6858.c
93: u8 something; /* always equals 0x43 */
525: buf->something = 0x43;
linux-master/drivers/usb/serial/spcp8x5.c
299: /* check that they really want us to change something */
linux-master/drivers/usb/storage/freecom.c
252: * The Freecom device will only fail if there is something wrong in
297: * The Freecom device will only fail if there is something
linux-master/drivers/usb/storage/sddr55.c
98: int fatal_error; /* set if we detect something nasty */
linux-master/drivers/usb/storage/transport.c
112: * command _must_ pass through this function (or something like it) for the
145: /* something went wrong */
linux-master/drivers/usb/storage/unusual_devs.h
38: * as opposed to devices that do something strangely or wrongly.
linux-master/drivers/usb/typec/Kconfig
14: something else then USB communication.
linux-master/drivers/usb/typec/port-mapper.c
74: * the _PLD with it, but if there one day is something else (like maybe
linux-master/drivers/usb/typec/tipd/core.c
1063: * Without writing something to DATA_IN, this command would
linux-master/drivers/usb/typec/ucsi/ucsi.c
1350: /* If the PPM is still doing something else, reset it again. */
1618: /* Check if there is already something connected */
linux-master/drivers/usb/usb-skeleton.c
541: /* something prevented us from registering this driver */
linux-master/drivers/vfio/group.c
193: * statement is that the user cannot have done something that
linux-master/drivers/vfio/pci/vfio_pci_intrs.c
132: * mask, not just when something is pending.
linux-master/drivers/vhost/vhost.c
2170:/* TODO: This is really inefficient. We need something like get_user()
2820: /* Signal the Guest tell them we used something up. */
linux-master/drivers/vhost/vringh.c
315: /* You must want something! */
837: * vringh_notify_enable_user - we want to know if something changes.
850: * vringh_notify_disable_user - don't tell us if something changes.
1068: * vringh_notify_enable_kern - we want to know if something changes.
1081: * vringh_notify_disable_kern - don't tell us if something changes.
1578: * vringh_notify_enable_iotlb - we want to know if something changes.
1591: * vringh_notify_disable_iotlb - don't tell us if something changes.
linux-master/drivers/video/backlight/backlight.c
87: * This callback gets called when something important happens inside a
linux-master/drivers/video/backlight/lcd.c
23:/* This callback gets called when something important happens inside a
linux-master/drivers/video/fbdev/Kconfig
698: something goes wrong.
745: something goes wrong.
973: something goes wrong.
linux-master/drivers/video/fbdev/amifb.c
3710: * Make sure the Copper has something to do
linux-master/drivers/video/fbdev/atafb.c
251: * * checks var and eventually tweaks it to something supported,
linux-master/drivers/video/fbdev/atmel_lcdfb.c
739: * TODO: intensity bit. Maybe something like
linux-master/drivers/video/fbdev/aty/aty128fb.c
2110: /* If we can't test scratch registers, something is seriously wrong */
linux-master/drivers/video/fbdev/aty/atyfb_base.c
3659: par->irq = (unsigned int) -1; /* something invalid */
linux-master/drivers/video/fbdev/aty/radeon_base.c
977: * and do something better using 2nd CRTC instead of just hackish
linux-master/drivers/video/fbdev/aty/radeon_monitor.c
964: * We need something better ultimately. Things like fbcon basically pass us out
linux-master/drivers/video/fbdev/aty/radeon_pm.c
1558: * register is something new ?
1624: /* The trace reads that one here, waiting for something to settle down ? */
2899: * we'll have something better once we actually have some TVOut
linux-master/drivers/video/fbdev/core/Kconfig
24: something on your display, try setting this to N. Matrox cards in
linux-master/drivers/video/fbdev/core/fbcon.c
1110: else /* default to something safe */
linux-master/drivers/video/fbdev/geode/lxfb_core.c
34: * we try to make it something sane - 640x480-60 is sane
linux-master/drivers/video/fbdev/matrox/matroxfb_base.c
526: return 16; /* return something reasonable... or panic()? */
582: /* for other try to do something */
linux-master/drivers/video/fbdev/matrox/matroxfb_crtc2.c
561: /* do something... */
linux-master/drivers/video/fbdev/matrox/matroxfb_maven.c
806: /* something end... [A6]+1..[A8] */
814: /* something start... 0..[A4]-1 */
linux-master/drivers/video/fbdev/matrox/matroxfb_misc.c
506: * be something different?
linux-master/drivers/video/fbdev/metronomefb.c
220: /* calculating trn. trn is something used to index into
linux-master/drivers/video/fbdev/nvidia/nv_accel.c
273: par->currentRop = ~0; /* set to something invalid */
linux-master/drivers/video/fbdev/omap2/omapfb/omapfb-ioctl.c
842: * Fill in something that should keep the applications working.
linux-master/drivers/video/fbdev/omap2/omapfb/omapfb-main.c
996:/* checks var and eventually tweaks it to something supported,
1727:/* initialize fb_info, var, fix to something sane based on the display */
linux-master/drivers/video/fbdev/platinumfb.c
162:/* [danj] I think there's something fishy about those constants... */
linux-master/drivers/video/fbdev/pm3fb.c
1103: * This is the point where the color is converted to something that
linux-master/drivers/video/fbdev/pvr2fb.c
775: * already setup pvr2_fix with something meaningful at this point.
linux-master/drivers/video/fbdev/pxafb.c
1389: * and something has changed.
linux-master/drivers/video/fbdev/sa1100fb.c
485: * Make sure the user isn't doing something stupid.
702: * and something has changed.
1103: * does something stupid.
linux-master/drivers/video/fbdev/sis/sis_main.c
5381: "RAM type something else than expected: %d\n",
linux-master/drivers/video/fbdev/skeletonfb.c
203: * of var, then you are doing something wrong. Note also that the
358: * This is the point where the color is converted to something that
369: * palette after converting the colors to something acceptable by
373: * any of the above visuals, then you are doing something wrong.
linux-master/drivers/video/fbdev/sstfb.c
235:/* XXX do something to avoid hanging the machine if the voodoo is out */
linux-master/drivers/virt/vboxguest/vmmdev.h
270: * Some additional information, for example 'Beta 1' or something like
linux-master/drivers/virtio/virtio_balloon.c
211: * In the extremely unlikely case that something has occurred and we
linux-master/drivers/virtio/virtio_mmio.c
431: * virtio-mmio v1 uses a 32bit QUEUE PFN. If we have something
linux-master/drivers/w1/masters/ds2490.c
456: * can do something with it).
991: * pulling the bus state down to reading the state is 15us, something
linux-master/drivers/w1/masters/w1-gpio.c
80: * This parameter means that something else than the gpiolib has
linux-master/drivers/w1/w1.c
618: /* if the family driver needs to initialize something... */
linux-master/drivers/watchdog/sb_wdog.c
36: * loosely based on something Alan Cox wrote years ago.
linux-master/drivers/watchdog/shwdt.c
43: * something quite higher than 100 (or we need a proper high-res timer
linux-master/drivers/watchdog/sun4v_wdt.c
106: * We can expect a handle to be returned otherwise something
linux-master/drivers/xen/xen-pciback/xenbus.c
264: * put something in here to ensure that if a bridge gets given to a
linux-master/drivers/xen/xenbus/xenbus_client.c
221: (something it was trying to in the past) because dev->state
linux-master/drivers/xen/xenbus/xenbus_dev_frontend.c
617: * OK, now we have a complete message. Do something with it.
linux-master/drivers/xen/xenbus/xenbus_probe.c
86:/* If something in array of ids matches this device, return it. */
linux-master/fs/affs/bitmap.c
196: /* didn't find something, can only happen
linux-master/fs/afs/dir.c
1160: /* the filename maps to something */
linux-master/fs/afs/server.c
175: * TODO: For speed we want to use something other than a flat list
linux-master/fs/afs/vl_alias.c
27: .key = key, /* This might need to be something */
linux-master/fs/aio.c
1341: * something to be aware of when touching this code.
linux-master/fs/autofs/expire.c
459: if (found != expired) { // something has changed, continue
linux-master/fs/bcachefs/bcachefs.h
53: * of each bucket. It could be used to implement something more sophisticated,
linux-master/fs/bcachefs/bset.c
1301: * This works out ok, but it's something to be aware of:
linux-master/fs/bcachefs/btree_iter.c
3059: * doing something new: dont keep iterators excpt the ones that
linux-master/fs/bcachefs/btree_update.c
91: * something in an ancestor snapshot)
linux-master/fs/bcachefs/dirent.c
584: * XXX: btree_trans_too_many_iters() is something we'd like to
linux-master/fs/bcachefs/journal_io.c
1522: * something sensible:
linux-master/fs/bcachefs/journal_types.h
38: bool must_flush:1; /* something wants a flush */
linux-master/fs/btrfs/Kconfig
88: reference problems or verifying they didn't break something.
linux-master/fs/btrfs/backref.c
2962: * Return <0 if there is something wrong happened.
linux-master/fs/btrfs/block-group.c
2345: /* We may have excluded something, so call this just in case. */
2836: /* We may have excluded something, so call this just in case */
3352: * This can happen if something re-dirties a block group that
linux-master/fs/btrfs/ctree.c
2340: * Returns 0 if it found something.
2631: * Return true if something is wrong.
4608: * returns zero if something useful was found, < 0 on error and 1 if there
5004: * returns 0 if something is found, 1 if nothing was found and < 0 on error
5046: * returns 0 if something is found, 1 if nothing was found and < 0 on error
linux-master/fs/btrfs/ctree.h
693: * Returns 0 if it found something or 1 if there are no greater leaves.
linux-master/fs/btrfs/dev-replace.c
1269: * something that can happen if the dev_replace
linux-master/fs/btrfs/discard.c
511: * length filter. In the case something is added to make a
linux-master/fs/btrfs/disk-io.c
306: * last committed. Or something seriously wrong happened.
3343: * to something non-standard make sure we truncate it to sectorsize.
4317: * before any delayed worker has done something with the nodes.
linux-master/fs/btrfs/extent-io-tree.c
895: * Return true if we find something, and update @start_ret and @end_ret.
987: * True is returned if we find something, false if nothing was in the tree.
1203: * There's a hole, we need to insert something in it and ignore the
1431: * There's a hole, we need to insert something in it and ignore the
linux-master/fs/btrfs/extent-tree.c
2765: /* Logic error, something removed the block group. */
4093: * caller to try again and hope it progress something by writing some
4510: * If we get ENOMEM here or something else we want to
5878: * the tree, assuming nothing will change. If something does change
linux-master/fs/btrfs/extent_io.c
1894: * crashing the machine for something we can survive anyway.
2008: * If something went wrong, don't allow any metadata write bio to be
2484: * The value here is something negative that can't be confused with a valid
linux-master/fs/btrfs/file.c
395: * From here on out we will have actually dropped something, so
2008: * something like fallocate() that is holding the extent lock trying to
2295: * something has gone horribly wrong.
linux-master/fs/btrfs/free-space-cache.c
2193: * remove, so something has gone wrong.
linux-master/fs/btrfs/fs.h
136: /* Indicate that the cleaner thread is awake and doing something. */
linux-master/fs/btrfs/inode.c
3254: * If the ordered extent had an IOERR or something else went
3488: * This creates an orphan entry for the given inode in case something goes wrong
3776: * something larger than an xattr. We have to assume the inode
4679: * log tree in the case we do something like this:
5412:"%s gets something invalid in DIR_ITEM (name %s, directory ino %llu, location(%llu %u %llu))",
8175: * did something wrong.
8214: * 2) We need to have something to cache all the space that is going to
10549: * file changes again after this, the user is doing something stupid and
10648: * case something changes in the future, let's catch it
linux-master/fs/btrfs/ioctl.c
1089: * >0 - normal mode, something else is running,
linux-master/fs/btrfs/lru_cache.h
32: * use something like inode numbers as keys, which are always a u64, we
linux-master/fs/btrfs/qgroup.c
2288: /* Content mismatch, something went wrong */
linux-master/fs/btrfs/ref-verify.c
661: * sure we haven't messed something up. If we are making a new allocation and
947: * Could have an empty block group, maybe have something to check for
linux-master/fs/btrfs/reflink.c
131: * remaining of the block/page is equivalent to zeroes. We had something
linux-master/fs/btrfs/root-tree.c
65: * If we find something return 0, otherwise > 0, < 0 on error.
linux-master/fs/btrfs/scrub.c
1843: * For dev-replace, if we know there is something wrong with
linux-master/fs/btrfs/send.c
5768: * not by using something like filemap_range_has_page() before
linux-master/fs/btrfs/super.c
1891: * On another filesystem a subvolume mount is close to something like:
linux-master/fs/btrfs/tests/extent-io-tests.c
479: * something repetitive that could miss some hypothetical off-by-n bug.
linux-master/fs/btrfs/tests/free-space-tests.c
167: * First let's do something simple, an extent at the same offset as the
255: test_err("left something behind when removing space");
linux-master/fs/btrfs/tree-log.c
1971: * points to. Otherwise something like the following would result in a
6450: * by having something like this:
linux-master/fs/btrfs/tree-mod-log.c
335: * When we override something during the move, we log these removals.
787: * previous operations will be rewound (until we reach something older than
linux-master/fs/btrfs/ulist.c
27: * do something useful with the node;
linux-master/fs/btrfs/verity.c
345: * Once we've copied something, we want all of the items
linux-master/fs/btrfs/volumes.c
6087: /* we couldn't find one that doesn't fail. Just return something
linux-master/fs/buffer.c
1708: * moment when something will explicitly mark the buffer dirty (hopefully that
linux-master/fs/cachefiles/key.c
31: * turn the raw key into something cooked
linux-master/fs/cachefiles/namei.c
63: * Unmark a backing inode and tell cachefilesd that there's something that can
linux-master/fs/ceph/addr.c
1082: * We have something to write. If this is
linux-master/fs/ceph/caps.c
336: /* temporary, until we do something about cap import/export */
linux-master/fs/ceph/file.c
1771: * use a version assertion to redrive the thing if something
linux-master/fs/ceph/super.h
533: * we do want to set it to something, so that generic vfs code has an
562: * to be converted to something that can fit inside 32 bits. Note that
linux-master/fs/coda/inode.c
326: /* fake something like AFS does */
linux-master/fs/crypto/keyring.c
167: * Note that the name of this key type really should be something like
1097: * We return 0 if we successfully did something: removed a claim to the
linux-master/fs/d_path.c
399: * error value. So libc would do something like
linux-master/fs/dcache.c
568: * points to something that won't be moving around. I.e. skip the
705: // need to do something - put it on LRU if it wasn't there already
linux-master/fs/debugfs/inode.c
452: * @data: a pointer to something that the caller will want to get to later
496: * @data: a pointer to something that the caller will want to get to later
535: * @data: a pointer to something that the caller will want to get to later
825: * This is the equlivant of doing something like
linux-master/fs/dlm/lock.c
1354: /* something as changed, very unlikely but
4952:/* This is called by the midcomms layer when something is received for
linux-master/fs/dlm/lowcomms.c
1075: /* close other sock con if we have something new */
1082: /* check if we receved something while adding */
1094: /* check if we receved something while adding */
linux-master/fs/dlm/member.c
623: * Prevent dlm_recv from being in the middle of something when we do
linux-master/fs/dlm/midcomms.c
37: * hash. There exists also logic to detect version mismatched if something weird
linux-master/fs/dlm/recoverd.c
101: /* Schedule next timer if recovery put something on toss.
linux-master/fs/ecryptfs/crypto.c
1854: * Encrypts and encodes a filename into something that constitutes a
linux-master/fs/eventpoll.c
987: * been free'd and then gotten re-allocated to something else (since
1022: * We could return EPOLLERR | EPOLLHUP or something, but let's
1705: * We have to check if something went wrong during the poll wait queue
linux-master/fs/exfat/super.c
302: * Make the limit 24 just in case someone invents something
linux-master/fs/ext2/inode.c
607: * Allocation strategy is simple: if we have to allocate something, we will
linux-master/fs/ext4/ext4.h
1880: * them into something which is architecture independent. We don't define
linux-master/fs/ext4/extents.c
5655: /* Do we have something to swap ? */
5677: /* Do we have something to swap */
linux-master/fs/ext4/ialloc.c
495: * something similar, although regular files will
linux-master/fs/ext4/indirect.c
507: * Allocation strategy is simple: if we have to allocate something, we will
linux-master/fs/ext4/inode.c
3039: * We do something simple for now. The filemap_flush() will
linux-master/fs/ext4/mballoc.c
272: * given some of them can block, we'd have to use something like semaphores
1039: * Scale down goal len to make sure we find something
2638: * This could return negative error code if something goes wrong
linux-master/fs/ext4/namei.c
2368: * may not sleep between calling this and putting something into
linux-master/fs/f2fs/file.c
4608: * blocks were preallocated, or a negative errno value if something went
linux-master/fs/fat/inode.c
1266: * just in case someone invents something unusual.
linux-master/fs/fat/namei_vfat.c
86: * This may be nfsd (or something), anyway, we can't see the
linux-master/fs/fs-writeback.c
1603: * Writeback blocked by something other than
2133: * Did we write something? Try for more
linux-master/fs/fuse/dax.c
582: * Both read/write and mmap path can race here. So we need something
linux-master/fs/gfs2/aops.c
512: * obviously not something we'd want to do on too regular a basis.
linux-master/fs/gfs2/glock.c
1526: * debugging option or something like that. This is the fast
linux-master/fs/gfs2/rgrp.c
2610: * or -ve errno if something went wrong while checking
linux-master/fs/isofs/inode.c
812: * Note - we should never be setting the blocksize to something
818: * zonesize in the filesystem. If we have it set to something less,
linux-master/fs/isofs/rock.c
39: * This is a way of ensuring that we have something in the system
linux-master/fs/jffs2/README.Locking
27:time this happens are part of the new node, not just something that
linux-master/fs/jffs2/fs.c
679: /* NB. This will happen again. We need to do something appropriate here. */
linux-master/fs/jffs2/gc.c
314: /* Inode-less node. Clean marker, snapshot or something like that */
linux-master/fs/jffs2/wbuf.c
666: something screwed up */
1130: * a bootloader or something like that.
linux-master/fs/jfs/jfs_dmap.c
1881: /* something failed in handling an allocation request involving
2558: /* something went wrong in bubbling up the new
2974: /* better have found something since the higher
linux-master/fs/jfs/jfs_extent.c
327: /* if something other than an out of space error,
linux-master/fs/jfs/jfs_imap.c
1952: /* something bad happened. if a new iag was allocated,
linux-master/fs/jfs/jfs_superblock.h
11: * make the magic number something a human could read
linux-master/fs/jfs/namei.c
1595: * This may be nfsd (or something), anyway, we can't see the
linux-master/fs/locks.c
739: * 1/ that fl_blocked_requests can be tested locklessly. If something
2192: * setting conf->fl_type to something other than F_UNLCK.
linux-master/fs/namei.c
1394: if (flags & DCACHE_MOUNTED) { // something's mounted on it..
2901: /* Find something mounted on "pts" in the same directory as
linux-master/fs/namespace.c
3385: * we don't want to use lock_mount() - in this case finding something
4172: * - we don't move root/cwd if they are not at the root (reason: if something
4477: * detached mount with an anonymous mount namespace. IOW, something
linux-master/fs/netfs/write_collect.c
393: * something that's in progress. The issuer thread may be adding stuff
linux-master/fs/netfs/write_issue.c
26: * negotiated with the server; in something like ceph, they may represent the
linux-master/fs/nfs/dir.c
1839: * eventually need to do something more here.
linux-master/fs/nfs/internal.h
57: * a server can return, so make something up.
linux-master/fs/nfs/nfs42xdr.c
1234: * something odd.
linux-master/fs/nfs/nfsroot.c
207: * contains something, append it to our root options buffer
linux-master/fs/nfs/pnfs.c
125: * mount option? something else?
linux-master/fs/nfs/super.c
1108: /* We probably want something more informative here */
linux-master/fs/nfsd/nfs4proc.c
173: * the right thing on attempts to open something other than a
2570: * So first_op is something allowed outside a session, like
linux-master/fs/nfsd/nfs4state.c
7568: /* An empty list means that something else is going to be using it */
linux-master/fs/nfsd/nfs4xdr.c
333: * space for that many aces; something fishy is
linux-master/fs/nfsd/nfsfh.c
322: * that it expects something not of the given type.
linux-master/fs/nfsd/state.h
166: * o 1 more ephemeral reference for each nfsd thread currently doing something
linux-master/fs/notify/fanotify/fanotify.c
180:/* and the list better be locked by something too! */
260: /* userspace responded, convert to something usable */
linux-master/fs/notify/inotify/inotify_user.c
749: * Without _something_ set, we would have no events to
linux-master/fs/notify/mark.c
506: /* something else already called this function on this mark */
532: /* something else already called this function on this mark */
linux-master/fs/ntfs3/fslog.c
4986: * something its undo_next_lsn field.
linux-master/fs/ocfs2/alloc.c
5567: * something case 2 can handle.
linux-master/fs/ocfs2/cluster/heartbeat.c
777: * bad type... This isn't something that we should try
linux-master/fs/ocfs2/dlm/dlmmaster.c
1216: mlog(0, "something happened such that the "
1701: /* ok, something horribly messed. kill thyself. */
linux-master/fs/ocfs2/dlm/dlmrecovery.c
2651: /* dlmlock returned something other than NOTQUEUED or NORMAL */
linux-master/fs/ocfs2/dlm/dlmthread.c
103:/* Call whenever you may have added or deleted something from one of
linux-master/fs/ocfs2/dlm/dlmunlock.c
373: /* something bad. this will BUG in ocfs2 */
linux-master/fs/ocfs2/dlmfs/dlmfs.c
93: * flags which mean something to us:
linux-master/fs/ocfs2/dlmglue.c
631: * want error prints to show something without garbling the
1190: /* set it to something invalid so if we get called again we
linux-master/fs/ocfs2/journal.c
2308: * thread before changing it to something other than MOUNTED
linux-master/fs/ocfs2/stackglue.c
679: return -ENOMEM; /* or something. */
linux-master/fs/ocfs2/stackglue.h
43: * ocfs2_protocol_version changes when ocfs2 does something different in
linux-master/fs/ocfs2/suballoc.c
1239: * If we didn't do this, then deleting something and reallocating it as
linux-master/fs/ocfs2/xattr.c
5385: * modified something. We have to assume they did, and dirty
linux-master/fs/orangefs/orangefs-bufmap.c
185: * XXX: lock between calling this and doing something useful?
linux-master/fs/orangefs/waitqueue.c
330: * user process that needs something done and is being
linux-master/fs/overlayfs/dir.c
1378: * Check if the preallocated inode was actually used. Having something
linux-master/fs/overlayfs/namei.c
1410: * Assume something is there, we just couldn't
linux-master/fs/pipe.c
679: * if something changes and you got it wrong, the poll
linux-master/fs/posix_acl.c
1179: * something like xattr_permission() isn't needed. Only LSMs get a say.
linux-master/fs/proc/proc_sysctl.c
1401: * to call unregister_sysctl_table() and can instead use something like
linux-master/fs/pstore/blk.c
152: * * Others - something error.
linux-master/fs/reiserfs/bitmap.c
1175: /* do we have something to fill prealloc. array also ? */
linux-master/fs/reiserfs/do_balan.c
67: * if deleting something ( tb->insert_size[0] < 0 )
linux-master/fs/reiserfs/fix_node.c
527: /* something fits into the current node */
linux-master/fs/reiserfs/inode.c
1753: * does something when called for a synchronous update.
2082: * or something under it.
2369: * catch places below that try to log something without
linux-master/fs/reiserfs/journal.c
455: * Just because we return something in next_zero_bit does not mean we won't
1919: * make sure something gets logged to force
3641: * transaction that actually writes something, but should be taken
linux-master/fs/reiserfs/namei.c
58: * comment? maybe something like set de to point to what the path points to?
303: * FIXME: should add something like IOERROR
linux-master/fs/reiserfs/objectid.c
23: /* FIXME: add something else here */
linux-master/fs/reiserfs/reiserfs.h
791: * A release write_lock and wait for something
linux-master/fs/reiserfs/super.c
1109:/* returns 0 if something is wrong in option string, 1 - otherwise */
linux-master/fs/remap_range.c
123: * Ensure that we don't remap a partial EOF block in the middle of something
linux-master/fs/select.c
557: /* got something, stop busy polling */
925: /* found something, stop busy polling */
linux-master/fs/seq_file.c
214: // something left in the buffer - copy it out first
linux-master/fs/smb/client/cifsacl.c
350: * If we have too many subauthorities, then something is really wrong.
linux-master/fs/smb/client/cifsfs.c
11:/* Note that BB means BUGBUG (ie something to fix eventually) */
linux-master/fs/smb/client/connect.c
2371: * need to lock before changing something in the session.
linux-master/fs/smb/client/dir.c
792: * This may be nfsd (or something), anyway, we can't see the
linux-master/fs/smb/client/file.c
174: * to only read a portion of that, but as long as we read something, the netfs
1873: * structures - something is really wrong.
linux-master/fs/smb/client/smb1ops.c
209: * if we have more than 32k mids in the list, then something
linux-master/fs/smb/client/smb2ops.c
4475: cifs_dbg(VFS, "%s: something went wrong\n", __func__);
linux-master/fs/smb/client/smb2pdu.c
409: /* If sess reconnected but tcon didn't, something strange ... */
linux-master/fs/smb/client/transport.c
124: * that something is wrong, unless it is quite a slow link or a very
linux-master/fs/smb/server/smbacl.c
264: * If we have too many subauthorities, then something is really wrong.
linux-master/fs/tracefs/event_inode.c
35:/* Choose something "unique" ;-) */
49:/* Just try to make something consistent and unique */
359: * @data: something that the caller will want to get to later on.
672: /* Incremented ctx->pos without adding something, reset it */
822: * something not worth much. Keeping directory links at 1
linux-master/fs/tracefs/inode.c
616: * @data: a pointer to something that the caller will want to get to later
linux-master/fs/ubifs/commit.c
66: * If the root TNC node is dirty, we definitely have something to
303: /* Check if there is something to do */
linux-master/fs/ubifs/debug.c
1487: * if everything is all right and %-EINVAL if something is wrong with TNC.
linux-master/fs/ubifs/dir.c
857: /* We've deleted something - clean the "no space" flags */
961: /* We've deleted something - clean the "no space" flags */
linux-master/fs/ubifs/gc.c
512: * which obsoletes something in 'lp->lnum'.
linux-master/fs/ubifs/io.c
1171: * set it to something smaller so that it ends at the closest max.
1197: /* NOR flash or something similar */
1248: * head contains something related to this inode, it is
linux-master/fs/ubifs/replay.c
1210: * something went wrong and we cannot proceed mounting
linux-master/fs/ubifs/super.c
385: /* We've deleted something - clean the "no space" flags */
773: * necessary to report something for the 'statfs()' call.
linux-master/fs/ubifs/tnc.c
1281: * znode like this: | 3 | 5 | 5 | 6 | 7 |, which results in something
linux-master/fs/ufs/inode.c
251: * @err: we set it if something wrong
linux-master/fs/unicode/mkutf8data.c
1976: /* We must have found something above. */
linux-master/fs/xfs/libxfs/xfs_alloc.c
1178: * If we're feeding an AGFL block to something that doesn't live in the
1790: * once aligned; if not, we search left for something better.
linux-master/fs/xfs/libxfs/xfs_attr.c
990: * Returns 0 on success, or a negative errno if something else went wrong.
linux-master/fs/xfs/libxfs/xfs_attr.h
181: * committed to re-calling that subroutine until it returns something other than
linux-master/fs/xfs/libxfs/xfs_attr_remote.c
697: * routine until it returns something other than -EAGAIN.
linux-master/fs/xfs/libxfs/xfs_bmap.c
4494: * holes. There should always be something for us
linux-master/fs/xfs/libxfs/xfs_bmap.h
81:/* Map something in the CoW fork. */
linux-master/fs/xfs/libxfs/xfs_bmap_btree.c
228: * If we are coming here from something like unwritten extent
linux-master/fs/xfs/libxfs/xfs_btree.c
4410: /* Return value means the next level up has something to do. */
linux-master/fs/xfs/libxfs/xfs_btree_staging.c
800: * that, then something went wrong and we have to fail. This should
linux-master/fs/xfs/libxfs/xfs_dir2_data.c
122: * If this isn't a directory, something is seriously wrong. Bail out.
linux-master/fs/xfs/libxfs/xfs_dir2_leaf.c
97: * Pop an assert if something is wrong.
linux-master/fs/xfs/libxfs/xfs_dir2_node.c
2292: int *rvalp) /* out: did something */
linux-master/fs/xfs/libxfs/xfs_exchmaps.c
305: * or something that doesn't match what we asked for,
330: * or something that doesn't match what we asked for,
348: /* We found something to exchange, so return it. */
1058: * Walk through the file ranges until we find something to
linux-master/fs/xfs/libxfs/xfs_health.h
37: * a) Primary evidence, which signals that something is defective within the
44: * c) Indirect evidence, which points to something being wrong in another
linux-master/fs/xfs/libxfs/xfs_ialloc.c
601: * cannot merge, something is seriously wrong.
2198: * something is out of sync.
linux-master/fs/xfs/libxfs/xfs_inode_fork.c
81: * If the size is unreasonable, then something
122: * If the number of extents is unreasonable, then something is wrong and
linux-master/fs/xfs/libxfs/xfs_refcount.c
1199: * no longer the case, something is seriously wrong with the
linux-master/fs/xfs/scrub/agheader.c
90: * it, we're racing with something that's tearing down the AG, so
linux-master/fs/xfs/scrub/agheader_repair.c
180: * different root then something's seriously wrong.
linux-master/fs/xfs/scrub/attr_repair.c
293: * Decode the leaf local entry format. If something seems wrong, we
343: * Decode the leaf remote entry format. If something seems wrong, we
422: /* Skip key if it conflicts with something else? */
977: /* If we still have attr fork extents, something's wrong. */
linux-master/fs/xfs/scrub/common.c
54: * caller that something bad happened, and we preserve *error so that
61: * something bad happened. Since the error has been cleared, the caller
233:/* Record something being wrong with the filesystem primary superblock. */
387: * Calculate the number of blocks the rmap thinks are owned by something.
706: * If we're going to repair something, we need to ask for the largest possible
1013: * If the lookup succeeds, something else must be very wrong in the fs
linux-master/fs/xfs/scrub/cow_repair.c
357: * of the file range, or we find a delalloc or written extent, something is
linux-master/fs/xfs/scrub/findparent.c
291: * Returns the usual negative errno if something else happened.
352: * Returns the usual negative errno if something else happened.
linux-master/fs/xfs/scrub/fscounters.c
553: * something's probably wrong with the counters.
linux-master/fs/xfs/scrub/inode_repair.c
479:/* Turn di_mode into /something/ recognizable. Returns true if we succeed. */
984:/* Reset the data fork to something sane. */
linux-master/fs/xfs/scrub/orphanage.c
429: * discrepancy is a sign that something is seriously wrong.
linux-master/fs/xfs/scrub/parent.c
919: * stored. If the fork is absent, something is amiss.
linux-master/fs/xfs/scrub/rcbag.c
188: * We should have found /something/ because either next_rrm is the next
191: * sharing count. But if something is seriously wrong, bail out.
linux-master/fs/xfs/scrub/reap.c
71: * so if it's gone now there's something wrong and the fs will shut down.
77: * with only the same rmap owner but the block is not owned by something with
linux-master/fs/xfs/scrub/rtbitmap_repair.c
91: * If we find a delalloc reservation then something is very
linux-master/fs/xfs/scrub/scrub.c
84: * scrubber, something will notice that something is amiss and report
526: * Userspace asked us to repair something, we repaired it, rescanned
539: * Userspace asked us to scrub something, it's broken, and we have no
linux-master/fs/xfs/scrub/scrub.h
134: * something that can't be opened directly (e.g. symlinks).
linux-master/fs/xfs/scrub/tempfile.c
334: * If we find a delalloc reservation then something is very
431: * that, then something went wrong and we have to fail. This should
linux-master/fs/xfs/xfs_attr_inactive.c
80: * caught holding something that the logging code wants to flush to disk.
linux-master/fs/xfs/xfs_icache.c
525: * XXX(hch): eventually we should do something equivalent to
linux-master/fs/xfs/xfs_icreate_item.c
238: * cancelled, but warn the user that something is awry if the buffers
linux-master/fs/xfs/xfs_inode.c
2199: /* If this is not an unlinked inode, something is very wrong. */
linux-master/fs/xfs/xfs_log.c
261: * will hang here waiting for something else to update the AIL
785: * something to an unlinked inode, the irele won't cause
linux-master/fs/xfs/xfs_log_cil.c
1483: * xc_push_commit_stable flag even if something else has already queued
linux-master/fs/xfs/xfs_log_priv.h
684: * vmalloc if it can't get something straight away from the free lists or
linux-master/fs/xfs/xfs_log_recover.c
1277: * block. This wraps all the way back around to the head so something is
linux-master/fs/xfs/xfs_qm.c
427: * If something else is freeing this dquot and hasn't yet removed it
linux-master/fs/xfs/xfs_reflink.c
1361: * find one, that's a good sign that something is seriously
linux-master/include/asm-generic/cmpxchg.h
19: * something tries to do an invalidly-sized xchg().
linux-master/include/asm-generic/mmu.h
7: * Architectures with an MMU need something more complex.
linux-master/include/asm-generic/qspinlock.h
26: * it requires architectures to have xchg16; something which many LL/SC
linux-master/include/asm-generic/tlb.h
694: * that would want something that odd, I think it is up to that
linux-master/include/asm-generic/word-at-a-time.h
56: * The optimal byte mask counting is probably going to be something
linux-master/include/clocksource/hyperv_timer.h
54: * need to use something else. The currently published specification
linux-master/include/crypto/sha1.h
39: * the correct way to hash something with SHA-1 (use crypto_shash instead).
linux-master/include/drm/drm_drv.h
239: * Anything else would indicate there's something seriously wrong.
358: * TTM or something else entirely) and returns the resulting buffer handle. This
linux-master/include/drm/drm_util.h
58: * for_each_if(x->something == SOMETHING)
linux-master/include/drm/xe_pciids.h
23: * To turn them into something else, just provide a different macro passed as
linux-master/include/kunit/assert.h
79: * Represents a simple expectation or assertion that simply asserts something is
linux-master/include/linux/acct.h
9: * user-level programs that try to do something useful with the
linux-master/include/linux/backlight.h
290: * and if class_get_devdata() points to something in the body of that driver,
linux-master/include/linux/bio.h
202: * something like:
207: * do_something
linux-master/include/linux/buffer_head.h
120: * do something in addition to setting a b_state bit.
linux-master/include/linux/clk.h
423: * Returns 0 if there're none and a negative value if something failed.
488: * Returns 0 if there're none and a negative value if something failed.
linux-master/include/linux/closure.h
18: * progress" - in flight bios, some other thread that's doing something else -
127: * something unusual you can use closure_set_dead() which also helps
linux-master/include/linux/comedi/comedidev.h
469: * have their 'async_dma_dir' member set to something other than
808: * bit-shift operator to multiply or divide something by the sample size.
linux-master/include/linux/compiler-clang.h
124: * inputs, turning them into something worse than "m". Avoid using
linux-master/include/linux/dcache.h
321: * used to clone an existing reference; using it on something with
473: * the inode. (3) The dentry may have something attached to ->d_lower and the
474: * type field of the flags may be set to something other than miss or whiteout.
linux-master/include/linux/dmaengine.h
407: * in one burst to the device. Typically something like half the
linux-master/include/linux/drbd_genl.h
74: * GENL_op_init( .doit = x, .dumpit = y, .flags = something)
linux-master/include/linux/fb.h
260: /* checks var and eventually tweaks it to something supported,
linux-master/include/linux/fs.h
1028: __attribute__((aligned(4))); /* lest something weird decides that 2 is OK */
2583:/* try to use something standard before you use this */
linux-master/include/linux/highmem.h
159: * // Do something to the contents of that page.
linux-master/include/linux/i2c.h
626: * configure padmux here for SDA/SCL line or something else they want.
628: * may configure padmux here for SDA/SCL line or something else they want.
675: * per transfer, plus something called combined message or write-then-read.
linux-master/include/linux/ipmi.h
202: * way. This is useful if you need to spin waiting for something to
linux-master/include/linux/iversion.h
35: * inode. If it's different then something has changed. Observers cannot infer
linux-master/include/linux/kconfig.h
34: * Getting something that works in C and CPP for an arg that may or may
linux-master/include/linux/kobject.h
164: * called whenever a kobject has something happen to it so that the kset
linux-master/include/linux/kvm_host.h
858:/* The guest did something we don't support. */
linux-master/include/linux/lcd.h
61: points to something in the body of that driver, it is also invalid. */
linux-master/include/linux/llist.h
213: * test whether the list is empty without deleting something from the
linux-master/include/linux/mm.h
2581: * because something (e.g., COW, uffd-wp) blocks that from happening for all
3236: * usage, an architecture is expected to do something like
linux-master/include/linux/mm_inline.h
537: * cleared so we will never accidentally replace something valuable. Meanwhile
linux-master/include/linux/mmc/host.h
153: * or a negative errno value when something bad happened
162: * or a negative errno value when something bad happened
linux-master/include/linux/mtd/mtd.h
359: * If the driver is something smart, like UBI, it may need to maintain
linux-master/include/linux/objpool.h
202: /* fault caught: something must be wrong */
linux-master/include/linux/overflow.h
12: * to do something like:
linux-master/include/linux/pci.h
1542: * _do_something_(res);
linux-master/include/linux/pci_hotplug.h
35: * the user wants to do something to a specific slot (query it for information,
linux-master/include/linux/platform_data/cros_ec_commands.h
3399: /* Notify the AP that something happened on CEC */
4809: * necessarily reboot the EC. Rename to "image" or something similar?
6386: * In your experimental code, you may want to do something like this:
linux-master/include/linux/platform_data/mmc-mxcmmc.h
18: * or a negative errno value when something bad happened
linux-master/include/linux/pm.h
451: * something when it is called (it should ensure that the device will be
linux-master/include/linux/printk.h
102: * Use this one if you want to tell the user or vendor about something
linux-master/include/linux/pstore.h
152: * backend is also expected to write @id with something that
linux-master/include/linux/ptrace.h
244: * syscall handler, or something along those lines).
443: * is unspecified, but should be something harmless like an %ENOSYS error
linux-master/include/linux/rculist.h
316: * do_something(bar);
linux-master/include/linux/rcupdate.h
755: * therefore might be referencing something that the corresponding RCU
linux-master/include/linux/regmap.h
1690: * something is going wrong and something probably needs to select
linux-master/include/linux/remoteproc.h
60: * do something (e.g. allocate a system resource). Sometimes a negotiation
446: * the elements should be always something sane.
linux-master/include/linux/sched/signal.h
200: * from jiffies_to_ns(utime + stime) if sched_clock uses something
linux-master/include/linux/sched/task.h
188: * must assume something there may need to be copied to userspace.
linux-master/include/linux/start_kernel.h
9: up something else. */
linux-master/include/linux/sysctl.h
156: * @count: Upped every time something is added to @inodes and downed every time
157: * something is removed from inodes
linux-master/include/linux/sysv_fs.h
161: * something is most likely wrong (not a filesystem, bad bytesex). */
linux-master/include/linux/typecheck.h
6: * Check at compile time that something is of a particular type.
26: * Check at compile time that something is a pointer type.
linux-master/include/linux/uaccess.h
315: * The recommended usage is something like the following:
linux-master/include/linux/usb/sl811.h
25: /* some boards need something like these: */
linux-master/include/linux/xarray.h
1068: * If there is already something stored at @index, this function does
1481:/* True if the pointer is something other than a node */
linux-master/include/linux/xz.h
89: * itself specifies something that we don't support.
linux-master/include/media/media-device.h
54: * @req_queue: Queue a validated request, cannot fail. If something goes
linux-master/include/media/v4l2-subdev.h
305: * board or platform it might be connected to something else entirely.
linux-master/include/media/videobuf2-core.h
384: * state. Typically you only have to do something if the
linux-master/include/net/9p/9p.h
351: * on the entity (ie. read means something different on a directory than
linux-master/include/net/cfg80211.h
9097: * pass %NULL as the @wakeup parameter to advertise that something
linux-master/include/net/cfg802154.h
204: * or not. Assign this to something global to your driver to
linux-master/include/net/dropreason-core.h
137: * @SKB_DROP_REASON_IP_INHDR: there is something wrong with IP header (see
linux-master/include/net/inet_ecn.h
248: * 1 if something is broken and should be logged (!!! above)
linux-master/include/net/netlabel.h
36: * to convert the label on the packet into something meaningful on the host
linux-master/include/net/sctp/structs.h
1768: * Error Count : [Clear this any time I get something.]
linux-master/include/rdma/uverbs_ioctl.h
63: /* User isn't allowed to provide something < min_len */
linux-master/include/scsi/scsi_host.h
171: * get an immediate call to slave_destroy(). If we find something
linux-master/include/scsi/sg.h
123:#define SG_INFO_CHECK 0x1 /* something abnormal happened */
linux-master/include/scsi/viosrp.h
141: * asynchrouously with something like a SCSI AER
linux-master/include/soc/fsl/qman.h
747: * do_something_with(myfq->an_extra_field);
linux-master/include/sound/max98095.h
49: * but it is something that might not be supported.
linux-master/include/sound/soundfont.h
23: unsigned char mapped; /* True if mapped to something else */
linux-master/include/trace/define_custom_trace.h
9: * TRACE_INCLUDE_FILE if the file name is something other than TRACE_SYSTEM.h
13: * TRACE_INCLUDE_PATH if the path is something other than core kernel include/trace
linux-master/include/trace/define_trace.h
9: * TRACE_INCLUDE_FILE if the file name is something other than TRACE_SYSTEM.h
13: * TRACE_INCLUDE_PATH if the path is something other than core kernel include/trace
linux-master/include/uapi/drm/i915_drm.h
1107: * Note that having something in the write domain implies it's in the
3678: * it's something we can expect to see in the wild. See
3747: * device local-memory we can do something like:
linux-master/include/uapi/linux/acct.h
9: * user-level programs that try to do something useful with the
linux-master/include/uapi/linux/bpf.h
1908: * defaults to something like:
linux-master/include/uapi/linux/btrfs_tree.h
354: * Stores items that allow to quickly map UUIDs to something else.
1089: * are set to something a given disk format doesn't understand
linux-master/include/uapi/linux/capability.h
364:/* Allow triggering something that will wake the system */
linux-master/include/uapi/linux/dm-log-userspace.h
159: * The region size is something that was determined at constructor time.
linux-master/include/uapi/linux/dvb/frontend.h
20: * @FE_IS_STUPID: There's something wrong at the
227: * @FE_HAS_SIGNAL: Has found something above the noise level.
linux-master/include/uapi/linux/hdreg.h
396: * If you change something here, please remember to update fix_driveid() in
linux-master/include/uapi/linux/jffs2.h
19:/* You must include something which defines the C99 uintXX_t types.
linux-master/include/uapi/linux/media.h
54: * Drivers should change it to something useful.
linux-master/include/uapi/linux/netfilter_bridge/ebtables.h
99: * Contrary, iptables doesn't use something like ebt_entries and therefore uses
linux-master/include/uapi/linux/raid/md_u.h
107: * means 'raid0', so we need something else. This is
linux-master/include/uapi/linux/seccomp.h
98: * syscalls if arguments are rewritten to something unsafe.
linux-master/include/uapi/linux/videodev2.h
261: * HDTV image (use Rec. 709), or something else (use sRGB).
1245:/* FIXME: in theory we should pass something like PCI device + memory
linux-master/include/uapi/linux/virtio_balloon.h
103: * If implementing a similar structure, do something like the below instead:
linux-master/include/uapi/linux/wireless.h
432:/* Note : if you have something like 80 frequencies,
linux-master/include/uapi/mtd/ubi-user.h
79: * is something like:
linux-master/include/video/omapfb_dss.h
283: * itself. However, the configs should be something that
linux-master/include/video/sticore.h
335: /* do not add something below here ! */
linux-master/init/Kconfig
1783: something like this).
linux-master/init/main.c
1036: * this. But we do want output early, in case something goes wrong.
linux-master/io_uring/cancel.c
303: /* found something, done! */
linux-master/io_uring/openclose.c
144: * marginal gain for something that is now known to be a slower
linux-master/io_uring/rsrc.c
127: /* arbitrary limit, but we need something */
linux-master/ipc/util.c
218: * Thus the object must be fully initialized, and if something fails,
linux-master/kernel/audit.c
1275: * something to keep in mind if this changes */
2301:/* global counter which is incremented every time something logs in */
linux-master/kernel/auditsc.c
2970: * If a process ends with a core dump, something fishy is going on and we
linux-master/kernel/bpf/btf.c
2675: /* We must resolve to something concrete at this point, no
linux-master/kernel/bpf/helpers.c
2522: * usually looks something like this pattern:
linux-master/kernel/bpf/log.c
79: /* check if we have at least something to put into user buf */
123: * something, even if terminal '\0'
linux-master/kernel/bpf/trampoline.c
73: * (something else is making changes to this same trampoline).
linux-master/kernel/bpf/verifier.c
2096: * something new about u64 from any random s64 range, and vice versa.
2211: /* We might have learned something about the sign bit. */
4359: * something (e.g., stack access through non-r10 register), so
11282: * equivalent without forcing them to explicitly cast with something
13243: /* something was added to pkt_ptr, set range to zero */
13302: /* something was added to pkt_ptr, set range to zero */
13567: /* We may learn something more from the var_off */
13630: /* We may learn something more from the var_off */
13769: /* We may learn something more from the var_off */
14810: * requires single bit to learn something useful. E.g., if we
14812: * are actually set? We can learn something definite only if
15570: * something into it earlier
17264: * 4: ... something useful here ...
linux-master/kernel/crash_core.c
431: * all of that, so there is no need to invent something new.
linux-master/kernel/debug/kdb/kdb_io.c
71: case 2: /* \e<something> */
850: /* user hit something unexpected */
linux-master/kernel/debug/kdb/kdb_main.c
875: * The "str" argument may point to something like | grep xyz
linux-master/kernel/entry/common.c
35: * the ABI here can be something that doesn't make sense for
linux-master/kernel/events/core.c
7759: * If there is something to dump, add space for the dump
7872: * something about the overflowing header::size, like repurpose the
linux-master/kernel/events/hw_breakpoint.c
639: * call above. If not, something is broken.
linux-master/kernel/events/ring_buffer.c
505: * Only send RECORD_AUX if we have something useful to communicate
linux-master/kernel/events/uprobes.c
1673: * architecture needs to do something different it can define
linux-master/kernel/exit.c
931: * Take the task off the cpu after something catastrophic has
1440: * there always is something to wait for.
linux-master/kernel/futex/pi.c
556: * requeue_cmp_pi or for whatever reason something took the
829: * the user space value claiming something different. There is no
linux-master/kernel/futex/requeue.c
705: * It can't be requeued from uaddr2 to something else since we don't
linux-master/kernel/futex/waitwake.c
472: * Even if something went wrong, if we find out that a futex
linux-master/kernel/irq/autoprobe.c
42: * something may have generated an irq long ago and we want to
linux-master/kernel/irq/spurious.c
211: * with something else removing an action. It's ok to take
linux-master/kernel/kcsan/report.c
520: * something other than TASK_RUNNING.
linux-master/kernel/latencytop.c
12: * the 'traditional' interrupt latency (which is primarily caused by something
linux-master/kernel/locking/lockdep.c
3169: * something is wrong.
4884: * No key, no joy, we need to hash something.
linux-master/kernel/module/procfs.c
19: int printed_something = 0;
28: printed_something = 1;
33: printed_something = 1;
37: if (!printed_something)
linux-master/kernel/module/stats.c
189: * These failures are good signs the kernel or userspace is doing something
linux-master/kernel/panic.c
546: * If something bad has gone wrong, you'll want @lockdebug_ok = false, but for
linux-master/kernel/power/snapshot.c
85: * It is still worth to have a warning here if something changes and this
linux-master/kernel/power/swap.c
936: * them synced (in case something goes wrong) but we DO not want to mark
linux-master/kernel/printk/printk.c
3593: * users know there might be something in the kernel's log buffer that
linux-master/kernel/ptrace.c
306: * Using the euid would make more sense here, but something
linux-master/kernel/rcu/Kconfig.debug
121: that something is hung up somewhere. Therefore, the notifier
linux-master/kernel/rcu/tree.c
259: * do_something();
261: * do_something_else();
265: * call to do_something() would be guaranteed to wait only until
2540: * Stop only if limit reached and CPU has something to do.
linux-master/kernel/rcu/tree_nocb.h
325: * Return true if there was something to be flushed and it succeeded, otherwise
linux-master/kernel/sched/completion.c
9: * something which isn't entirely natural for semaphores.
linux-master/kernel/sched/core.c
2769: * XXX do further audits, this smells like something putrid.
3665: * Make it appear like a SCHED_FIFO task, its something
8931: * If you want to use yield() to wait for something, use wait_event().
linux-master/kernel/sched/deadline.c
1158: * The task might have changed its scheduling policy to something
2294: * 'something', and let the caller sort the things out.
2331: /* Retry if something changed. */
linux-master/kernel/sched/fair.c
5470: * 4) do not run the "skip" process, if something else is available
5880: * Nothing to run but something to decay (on_list)?
linux-master/kernel/sched/rt.c
1902: * just give the caller *something* to work with from the compatible
linux-master/kernel/seccomp.c
1917: * combine these two flags, there's no way to tell whether something
linux-master/kernel/signal.c
1153: * signal was rt and sent by user using something
1598: * kill_something_info() interprets pid in interesting ways just like kill(2).
1604:static int kill_something_info(int sig, struct kernel_siginfo *info, pid_t pid)
2240: * The arch code has something special to do before a
2625: * changed. If the debugger wanted something
2867: * with SIGCONT or something like that.
3830: return kill_something_info(sig, &info, pid);
linux-master/kernel/softirq.c
42: execution. Hence, we get something sort of weak cpu binding.
linux-master/kernel/time/hrtimer.c
1850: * Give the system a chance to do something else than looping
linux-master/kernel/time/tick-broadcast.c
888: * interrupt or we got woken by something else.
923: * We got woken by something else. Reprogram
linux-master/kernel/time/timekeeping.c
2360: * something is VERY wrong!
linux-master/kernel/time/timer.c
2565: * that will tell you if something is gone wrong and where.
linux-master/kernel/time/timer_migration.c
1558: * level. Otherwise there went something wrong!
linux-master/kernel/torture.c
921: * need the kthread to be stopped so that you can do something to it before
linux-master/kernel/trace/Kconfig
153:# options do not appear when something else selects it. We need the two options
412: something other than the kernel. For example, if a
937: If something does not get converted properly, this option can be
linux-master/kernel/trace/fgraph.c
36: * archs can override this function if they must do something
45: * archs can override this function if they must do something
linux-master/kernel/trace/ftrace.c
397: /* Only do something if we are tracing something */
998: * The files created are permanent, if something happens
2226: * count is something other than one, we do not
2804: * archs can override this function if they must do something
2812: * archs can override this function if they must do something
3212: /* If something went wrong, bail without enabling anything */
3254: /* if we can't allocate this size, try something smaller */
3933: * want people to see, but if something is tracing
3934: * something, we probably want to know about it.
3958: * want people to see, but if something had traced
3959: * something, we probably want to know about it.
4874: * The caller might want to do something special
5565: * to call something else
5594: * to call something else
7540: /* Make sure there's something to do */
linux-master/kernel/trace/ring_buffer.c
245: * If the event is something other than a data event, it
1124: * We use cmpxchg to help prevent this race. We also do something
1904: * If something was added to this page, it was full
2120: /* Can't run something on an offline CPU. */
2179: /* Can't run something on an offline CPU. */
3117: * a bit of overhead in something as critical as function tracing,
3215: * tracing something else. In this case, calling this function
3579: * If something came in between C and D, the write stamp
3642: /* We reserved something on the buffer */
3717: * storm or we have something buggy.
6563: * Basic stats are recorded and reported. If something in the
6604:static __init int rb_write_something(struct rb_test_data *data, bool nested)
6676: rb_write_something(data, false);
6693: rb_write_something(data, true);
linux-master/kernel/trace/trace.c
1451: * something other than NULL when we get here, which we can
6486: * We block until we read something and tracing is disabled.
6489: * then enable tracing. But after we have read something,
linux-master/kernel/trace/trace_eprobe.c
681: * It's a bug if one failed for something other than memory
linux-master/kernel/trace/trace_events.c
894: /* Make sure there's something to do */
1064: * know that something went wrong.
2804: * back to back without something in between.
2805: * We can skip that something in between.
linux-master/kernel/trace/trace_events_filter.c
312: * program that gets affected by the operand. Thus if we have something like
linux-master/kernel/trace/trace_events_hist.c
3073: /* If we can't find the variable, something went wrong */
linux-master/kernel/trace/trace_events_synth.c
1349: * semicolons, and that's something we no
linux-master/kernel/trace/trace_osnoise.c
1654: * migrate the thread away from the current CPU, something bad has happened.
linux-master/kernel/trace/trace_recursion_record.c
80: /* Did something else already added this for us? */
linux-master/kernel/trace/trace_selftest.c
37: * we loop more than the size, there's something wrong
linux-master/kernel/trace/trace_seq.c
19: * try to write something into the trace_seq buffer and if it fails
59: * do something else with the contents.
linux-master/kernel/trace/trace_stack.c
70: * saving the function's local variables, the stack will look something like
linux-master/kernel/workqueue.c
1347: * is exhausted, something went really wrong and we probably made enough
3257: * kernels, where a requeueing work item waiting for something to
3830: * %true if @flush_color >= 0 and there's something to flush. %false
5255: * If something goes wrong during CPU up/down, we'll fall back to
linux-master/lib/Kconfig.debug
244: Selecting something other than "None" results in a kernel image
linux-master/lib/cpumask.c
127: * do_something(cpu);
134: * do_something(cpu);
linux-master/lib/crypto/sha1.c
80: * you do have to use SHA-1, this isn't the correct way to hash something with
linux-master/lib/flex_proportions.c
34: * which something happened with proportion of type j.
linux-master/lib/kobject.c
282: * returned something from .rodata.
347: pr_err("kobject (%p): tried to init an initialized object, something is seriously wrong.\n",
420: pr_err("kobject '%s' (%p): tried to add an uninitialized object, something is seriously wrong.\n",
linux-master/lib/lru_cache.c
338: return 1; /* something on the free list */
340: return 1; /* something to evict */
linux-master/lib/maple_tree.c
4268: /* spanning writes always overwrite something */
linux-master/lib/raid6/int.uc
27:/* Change this from BITS_PER_LONG if there is something better... */
linux-master/lib/ratelimit.c
3: * ratelimit.c - Do something with rate limit.
linux-master/lib/sort.c
201: * a swap_func function if you need to do something more than a memory
linux-master/lib/string_kunit.c
214: STRCMP_TEST_EXPECT_LOWER(test, strcmp, "Just a string", "Just a string and something else");
242: STRCMP_TEST_EXPECT_LOWER(test, strncmp, "Just a string", "Just a string and something else",
243: strlen("Just a string and something else"));
248: STRCMP_TEST_EXPECT_EQUAL(test, strncmp, "Just a string", "Just a string and something else",
linux-master/lib/test_kmod.c
535: * We must return 0 after a trigger even unless something went
544: * fail when something went wrong with the driver upon trigger
linux-master/lib/xarray.c
30: * @entry refers to something stored in a slot in the xarray
linux-master/lib/xz/xz_lzma2.h
103: * Match byte is used when the previous LZMA symbol was something else than
linux-master/lib/xz/xz_private.h
122: * big enough, and XZ_OPTIONS_ERROR if props indicates something that this
linux-master/lib/zlib_deflate/deflate.c
389: /* Make sure there is something to do and avoid duplicate consecutive
linux-master/lib/zlib_inflate/inflate.c
273: ... do something with BITS(n) ...
linux-master/lib/zstd/compress/zstd_compress.c
5651: * if we ended up splitting a sequence. Otherwise, it may return a ZSTD error if something
linux-master/lib/zstd/decompress/zstd_decompress.c
95: * Returns 0 if successful, or a zstd error code if something went wrong.
1265: RETURN_ERROR(GENERIC, "impossible to reach"); /* some compiler require default to do something */
2092: RETURN_ERROR(GENERIC, "impossible to reach"); /* some compiler require default to do something */
linux-master/mm/balloon_compaction.c
188: * list is empty and there are no isolated pages, then something
linux-master/mm/compaction.c
2192: * Either we isolated something and proceed with migration. Or
linux-master/mm/filemap.c
716: * When userland calls fsync (or something like nfsd does the equivalent), we
981: * get overwritten with something else, is a waste of memory.
3290: * Do we have something in the page cache already?
linux-master/mm/gup.c
49: * neither is the case, there is certainly something wrong.
1140: * an error pointer if there is a mapping to something not represented
1953: * Failing to pin anything implies something has gone wrong (except when
linux-master/mm/hugetlb.c
1890: * have done something to cause success (such as freeing some
3600: * pages are allocated from memblock allocated or something similar.
linux-master/mm/kmsan/kmsan.h
44: * recover if something goes wrong.
linux-master/mm/ksm.c
915: * a page to put something that might look like our key in page->mapping.
2370: * to waste our time searching for something identical to it there.
linux-master/mm/madvise.c
1402: * -EBADF - map exists, but area maps something that isn't a file.
linux-master/mm/memcontrol.c
284: * 3) CPU1: a process from another memcg is allocating something,
2972: * better to wait until the end of task_move if something is going on.
5176: * Please deprecate this and replace with something simpler if at all
linux-master/mm/memory-failure.c
517: * Also when FAIL is set do a force kill because something went
528: * In case something went wrong with munmapping
541: * something else on the address in-between. We could
1103: * This way the application knows that something went
1475: * it into something we can handle.
linux-master/mm/memory.c
1319: * contains uffd-wp protection information, that's something we can't
4914: * something).
linux-master/mm/migrate.c
1299: * We would like to do something similar for the old page, when
linux-master/mm/mmap.c
1539: /* The open routine did something to the protections that pgprot_modify
linux-master/mm/nommu.c
360: * lock, except when an application is doing something nasty
linux-master/mm/page_alloc.c
4401: * so that we can identify them and convert them to something
linux-master/mm/percpu.c
2023: * something we support properly and can be highly unreliable and
linux-master/mm/rmap.c
486: * [ something equivalent to page_mapped_in_vma() ].
2565: * rmap_walk_anon - do something to anonymous page using the object-based
2616: * rmap_walk_file - do something to file page using the object-based rmap method
linux-master/mm/shmem.c
2167: * entry unconditionally - even if something else had already woken the
linux-master/mm/slub.c
6052: * we need to add something to before end.
linux-master/mm/vmalloc.c
437: * or be re-mapped for something else, if TLB flushes are being delayed or
2610: /* At least something should be left free */
3252: * Set direct map to something invalid so that it won't be cached if
linux-master/mm/vmscan.c
6200: * are "out of memory" and something needs to be killed.
7132: * page out something else, and this flag essentially protects
linux-master/net/Kconfig
173: of the computers on your local network wants to send something to
linux-master/net/atm/lec.c
170: * there is non-reboot way to recover if something goes wrong.
474: /* Do something needful? */
linux-master/net/batman-adv/bat_iv_ogm.c
1715: /* do we get something for free()? */
linux-master/net/batman-adv/bat_v_elp.c
308: /* if something goes wrong while probing, better to stop
linux-master/net/batman-adv/bat_v_ogm.c
745: /* if these are not allocated, something is wrong. */
linux-master/net/batman-adv/bridge_loop_avoidance.c
987: /* TODO: we could call something like tt_local_del() here. */
linux-master/net/batman-adv/send.c
1090: /* do we get something for free()? */
linux-master/net/batman-adv/tp_meter.c
866: /* something went wrong during the preparation/transmission */
linux-master/net/batman-adv/translation-table.c
2570: /* Replace the old buffer only if I received something in the
linux-master/net/bluetooth/hci_event.c
1549: * timeout in case something goes wrong.
5644: * but we're in central role this must be something
linux-master/net/bluetooth/hci_request.c
643: * current RPA has expired or there is something else than
linux-master/net/bluetooth/hci_request.h
36: /* If something goes wrong when building the HCI request, the error
linux-master/net/bluetooth/hci_sync.c
956: * current RPA has expired or there is something else than
linux-master/net/bluetooth/l2cap_sock.c
213: /* Check that the socket wasn't bound to something that
linux-master/net/bluetooth/rfcomm/core.c
1600: /* We should probably do something with this information here. But
linux-master/net/bridge/br_switchdev.c
152: * ndm_flags == NTF_MASTER( | NTF_STICKY), ext_flags == 0 by something
linux-master/net/bridge/netfilter/ebtables.c
974: /* used to know what we need to clean up if something goes wrong */
linux-master/net/caif/cfcnfg.c
161: /* Otherwise just return something */
linux-master/net/can/isotp.c
89: * something about 8 kbyte to be able to test this new functionality.
linux-master/net/ceph/debugfs.c
29: * .../bdi - symlink to ../../bdi/something
linux-master/net/ceph/messenger_v1.c
57: * write something. @more is true if caller will be sending more data
1470: * Write something to the socket. Called in a worker thread when the
1471: * socket appears to be writeable and we have something ready to send.
linux-master/net/ceph/messenger_v2.c
3166: * We should always have something pending here. If not,
3167: * avoid calling populate_in_iter() as if we read something
linux-master/net/core/filter.c
1392: * memory in case something goes wrong.
1446: * memory in case something goes wrong.
1521: * memory in case something goes wrong.
linux-master/net/core/flow_dissector.c
371: /* A quick check to see if there might be something to do. */
linux-master/net/core/neighbour.c
69: to protocol backends, no attempts to send something to network.
1354: /* The second case: if something is already cached
1363: /* No address is supplied; if we know something,
1440: /* Again: avoid dead loop if something went wrong */
linux-master/net/core/rtnetlink.c
107: * something like
134: * it's not used in cases where something is added to do the list.
linux-master/net/core/xdp.c
750: * ``if (vlan_proto == bpf_htons(ETH_P_8021Q)) do_something();``
linux-master/net/dccp/input.c
539: * something else, like sending a delayed ack for a TIMESTAMP
linux-master/net/devlink/port.c
1240: * If driver is calling this, most likely it is doing something wrong.
1270: * it is doing something wrong.
linux-master/net/dns_resolver/dns_key.c
63: * looks something like (note this is packed):
linux-master/net/dns_resolver/dns_query.c
15: * installed and something like the following lines should be added to the
linux-master/net/dsa/port.c
545: /* Don't try to unoffload something that is not offloaded */
linux-master/net/handshake/netlink.c
268: * to prevent it from dereferencing something that hasn't
linux-master/net/hsr/hsr_forward.c
29: * frame is received from a particular node, we know something is wrong.
linux-master/net/ipv4/cipso_ipv4.c
45: * probably be turned into a hash table or something similar so we
linux-master/net/ipv4/inet_connection_sock.c
675: * and that it has something pending.
linux-master/net/ipv4/ip_fragment.c
55: * code now. If you change something here, _PLEASE_ update ipv6/reassembly.c
linux-master/net/ipv4/ip_gre.c
82: Hence, if we want that OSPF worked or traceroute said something reasonable,
862: I have an impression, that Cisco could make something similar,
linux-master/net/ipv4/ip_output.c
468: * f.e. by something like SCTP.
linux-master/net/ipv4/nexthop.c
2227: * vetoed, which is something that should only happen if the
linux-master/net/ipv4/raw.c
735: * This should be easy, if there is something there
linux-master/net/ipv4/tcp.c
534: * if you don't tell them that something has hung up!
linux-master/net/ipv4/tcp_bbr.c
370: * case we need to slow-start up toward something safe: TCP_INIT_CWND.
linux-master/net/ipv4/tcp_cong.c
448: * something better;) a packet is only considered (s)acked in its entirety to
linux-master/net/ipv4/tcp_input.c
799:/* There is something which you must keep in mind when you analyze the
1502: * setting gso_size to something.
1549: * something-or-zero which complicates things
2353: * inside several functions named tcp_try_undo_<something>.
2563: /* Hold old state until something *above* high_seq
3035: /* CWR is to be held something *above* high_seq
4536: /* It _is_ possible, that we have something out-of-order _after_ FIN.
5793: * above did something sort of send("A", MSG_OOB); send("B", MSG_OOB);
linux-master/net/ipv4/tcp_minisocks.c
765: * and the incoming segment acknowledges something not yet
linux-master/net/ipv4/tcp_output.c
2668: * over the other conditions. So that if something "more interesting"
linux-master/net/ipv4/tcp_timer.c
156: /* We know from an ICMP that something is wrong. */
160: /* However, if socket sent something recently, select some safe
624: * we'll have to use something other than TCP to talk to the
linux-master/net/ipv4/tcp_vegas.c
76: /* Begin taking Vegas samples next time we send something. */
linux-master/net/ipv4/udp.c
1808: * This should be easy, if there is something there we
linux-master/net/ipv4/udp_tunnel_nic.c
258: /* Find something that needs sync in this table */
linux-master/net/ipv6/ila/ila_xlat.c
311: /* It is the head. If there is something in the
linux-master/net/ipv6/mcast.c
1332: * Thus, should we *ever* encounter something else larger
linux-master/net/ipv6/netfilter/ip6_tables.c
75:/* ... might want to do something with class and flowlabel here ... */
linux-master/net/ipv6/raw.c
429: * This should be easy, if there is something there
linux-master/net/ipv6/seg6_local.c
2452: * optional, it means that the user has messed something up in the
linux-master/net/ipv6/udp.c
328: * This should be easy, if there is something there we
linux-master/net/key/af_key.c
223: /* XXX Do we need something like netlink_overrun? I think
linux-master/net/mac80211/agg-tx.c
53: * or something calling ieee80211_stop_tx_ba_session(), the driver's
linux-master/net/mac80211/cfg.c
3390: * to send something, and if we're an AP we have to be able to do
linux-master/net/mac80211/ieee80211_i.h
579: /* Use a separate work struct so that we can do something here
linux-master/net/mac80211/iface.c
1940: /* default ... something at least */
linux-master/net/mac80211/mesh_plink.c
1202: /* something went wrong */
linux-master/net/mac80211/rx.c
1317: * If it is first but there's something stored, we may be able
1756: * something went wrong the first time.
1944: * with each station, that is something we don't currently handle.
linux-master/net/mac80211/sta_info.c
731: * something inserts a STA (on one CPU) without holding the RTNL
1148: * only find something if the filtered queue was emptied
linux-master/net/mac80211/tx.c
2123: /* see if this argument is something we can use */
4856: * If queue is stopped by something other than due to pending
linux-master/net/netfilter/ipvs/ip_vs_ftp.c
242: * The outgoing packet should be something like
403: * The incoming packet having the PORT command should be something like
linux-master/net/netfilter/nf_conntrack_ftp.c
482: * because we're expecting something in the other direction.
linux-master/net/netfilter/nft_cmp.c
199: * something smaller than the full u32, therefore a cpu_to_le32 is done.
linux-master/net/netfilter/x_tables.c
214: err = -EPROTOTYPE; /* Found something. */
263: err = -EPROTOTYPE; /* Found something. */
linux-master/net/netfilter/xt_hashlimit.c
242: /* FIXME: do something. question is what.. */
linux-master/net/netlink/af_netlink.c
2341: /* EMSGSIZE plus something already in the skb means
linux-master/net/nfc/nci/uart.c
170: * Called when the line discipline is changed to something
linux-master/net/rds/ib.c
400: * If it were me, I'd advocate for something more flexible. Sending and
linux-master/net/rds/loop.c
118:/* we need to at least give the thread something to succeed */
linux-master/net/rds/tcp.c
151: * cp_state to something other than RDS_CONN_UP, and then
linux-master/net/rds/tcp_recv.c
289: * trying again to see if the VM can free up something for us.
linux-master/net/rfkill/core.c
324: * _hard_ kill state -- whenever something tries to change the
linux-master/net/rxrpc/call_object.c
714: * something that may be running/waiting there.
linux-master/net/rxrpc/conn_client.c
791: * schedule the work item for that point if we discarded something.
linux-master/net/rxrpc/conn_object.c
369: * something that may be running/waiting there.
linux-master/net/rxrpc/recvmsg.c
318: /* Wait for something to happen */
linux-master/net/rxrpc/sendmsg.c
236: * in case the caller wants to do something with it.
linux-master/net/sched/cls_u32.c
800: * case then something went very wrong elsewhere.
linux-master/net/sched/sch_api.c
50: device is ready to send something) in order and at times
1614: /* Reinit, just in case something touches this. */
linux-master/net/sched/sch_taprio.c
1220: * something went really wrong. In that case, we should warn about this
linux-master/net/sctp/associola.c
169: /* Use my own max window until I learn something better. */
545: /* If we have something on the transmitted list, we have to
linux-master/net/sctp/input.c
225: * be doing something with the new socket. Switch our veiw
linux-master/net/sctp/output.c
825: * if the packet already contains something, we need to
linux-master/net/sctp/outqueue.c
189: * something with this structure...
929: * they are generated in response to something we
linux-master/net/sctp/protocol.c
1481:/* Initialize the universe into something sensible. */
1683: /* BUG. This should probably do something useful like clean
linux-master/net/sctp/socket.c
727: * be removed. This is something which needs to be looked into
5652: * Set the daddr and initialize id to something more random and also
linux-master/net/sctp/ulpqueue.c
847: /* We've received something out of order, so find where it
linux-master/net/strparser/strparser.c
170: /* Always clone since we will consume something */
linux-master/net/sunrpc/cache.c
420:/* clean cache tries to find something to clean
422: * It returns 1 if it cleaned something,
linux-master/net/sunrpc/svc_xprt.c
609: * something must be dropped. It's not clear what will happen if we allow
linux-master/net/tls/tls_device.c
726: * too long in async stage, something bad happened
linux-master/net/unix/Kconfig
14: an embedded system or something similar, you therefore definitely
linux-master/net/vmw_vsock/af_vsock.c
1054: /* For datagram sockets we can read if there is something in
1080: /* If there is something in the queue then we can read. */
linux-master/net/vmw_vsock/vmci_transport_notify.c
347: * in the queue. Ask for notifications when there is something
linux-master/net/vmw_vsock/vmci_transport_notify_qstate.c
168: * in the queue. Ask for notifications when there is something
linux-master/net/wireless/radiotap.c
195: * if there is something else wrong.
300: * move on first so next call has something fresh to test
linux-master/net/wireless/reg.c
332: /* avoid freeing static information or freeing something twice */
2489: * Give usermode a chance to do something nicer (move to another
linux-master/net/wireless/scan.c
60: * if the driver uses something other than the IEs, e.g. private
linux-master/net/wireless/wext-core.c
871: /* If we have something to return to the user */
linux-master/net/wireless/wext-priv.c
21: /* Check if the driver has something to export */
170: /* If we have something to return to the user */
linux-master/net/wireless/wext-spy.c
190: * spy addresses, we should use something more efficient...
linux-master/net/x25/x25_forward.c
32: * do something sensible
linux-master/net/xfrm/xfrm_state.c
1107: * manager will do something to install a state with proper
linux-master/rust/kernel/sync/arc.rs
467:/// fn do_something(e: ArcBorrow<'_, Example>) -> Arc<Example> {
472:/// let cloned = do_something(obj.as_arc_borrow());
linux-master/rust/kernel/types.rs
122:/// pr_info!("Do something...\n");
linux-master/rust/kernel/workqueue.rs
26://! * The [`WorkItemPointer`] trait is implemented for the pointer type that points at a something
linux-master/samples/seccomp/bpf-fancy.c
32: static const char msg1[] = "Please type something: ";
linux-master/samples/seccomp/user-trap.c
119: fprintf(stderr, "huh? trapped something besides mount? %d\n", req->data.nr);
326: * something better should happen, like undoing the
linux-master/samples/trace_events/trace-events-sample.h
374: * But to do something like:
380: * overhead, even if small, is not something we want. As tracepoints
620: * But then if something defines "samples" or "trace_events" as a macro
linux-master/samples/v4l/v4l2-pci-skeleton.c
461: * V4L2_STD_ALL. This function should look something like this:
563: * something like this:
linux-master/scripts/check-uapi.sh
172: # which won't work for our grep match. Instead, print something grep will match.
linux-master/scripts/check_extable.sh
22:# After this point, something is seriously wrong since we just found out we
28:# doing something wrong and the rest of this code is just trying to print
linux-master/scripts/checkpatch.pl
1239:# Maybe one day convert this block of bash into something that returns
4263: # int foo(something bar, other baz);
4310:# or if that brace on the next line is for something else
4603: # EXPORT_SYMBOL(something_foo);
linux-master/scripts/dtc/libfdt/fdt_overlay.c
728: /* Symbol refers to something that won't end
748: /* Symbol refers to something that won't end
linux-master/scripts/extract_xc3028.pl
7:# 1) Download the windows driver with something like:
linux-master/scripts/get_abi.pl
309:# \b doesn't work well with paths. So, we need to define something else:
883: # What: foo = <something>
linux-master/scripts/jobserver-exec
53: # If something went wrong, give back the jobs.
linux-master/scripts/kconfig/lxdialog/menubox.c
21: * *) Formerly if I selected something my scrolling would be broken because
linux-master/scripts/kconfig/streamline_config.pl
504: # Check if something other than a module selects this config
524: # If no possible config selected this, then something happened.
linux-master/scripts/kconfig/tests/preprocess/variable/Kconfig
18:# Append something to a simply expanded variable.
24:# Append something to a recursively expanded variable.
linux-master/scripts/kernel-doc
175:# They probably want to be tidied up, made more localised or something.
2361: # Make sure we got something interesting.
linux-master/scripts/rust_is_available_test.py
124: # should output at least something to `stderr` (the output should
linux-master/scripts/setlocalversion
7:# If something goes wrong, send a mail the kernel build mailinglist
linux-master/scripts/tracing/ftrace-bisect.sh
19:# If this works, then we know that something is being traced that shouldn't be.
linux-master/security/commoncap.c
849: * 2) something prevented setuid root getting all caps
linux-master/security/inode.c
84: * @data: a pointer to something that the caller will want to get to later
183: * @data: a pointer to something that the caller will want to get to later
linux-master/security/keys/trusted-keys/trusted_tpm2.c
72: * trigger, so if it does there's something nefarious going on
linux-master/security/selinux/status.c
30: * number, it means something happen, so application will reset userspace
linux-master/sound/core/pcm_iec958.c
27: * Returns: length of buffer, or negative error code if something failed.
131: * Returns: length of buffer, or negative error code if something failed.
154: * Returns: length of buffer, or negative error code if something failed.
174: * Returns: length of buffer, or negative error code if something failed.
200: * Returns: length of buffer, or negative error code if something failed.
linux-master/sound/core/pcm_lib.c
397: /* something must be really wrong */
linux-master/sound/firewire/iso-resources.h
13: * bit mask to something else than the default (all ones)
linux-master/sound/firewire/motu/motu-protocol-v1.c
70:// 0x04000000: something relevant to clock.
linux-master/sound/hda/hdac_controller.c
238: /* something wrong, controller likely turned to D3 */
278: /* something wrong, controller likely turned to D3 */
linux-master/sound/isa/cs423x/cs4236.c
94: /* Guillemot Turtlebeach something appears to be cs4232 compatible
linux-master/sound/isa/es1688/es1688_lib.c
326: return -EINVAL; /* something is wrong */
linux-master/sound/isa/sb/sb16_csp.c
587: dsp_cmd[0] = 0x08; /* SB_DSP_!something! */
linux-master/sound/isa/sc6000.c
399: * if we have something different, we have to be warned.
linux-master/sound/isa/wavefront/wavefront_midi.c
25: * something other than 0 and 1 if the CS4232 UART/MPU-401 interface
linux-master/sound/isa/wavefront/wavefront_synth.c
477: int err = -1; /* something unknown */
1494: something very similar in the reverse direction.
linux-master/sound/oss/dmasound/dmasound.h
11: * device for true DSP processors but it will be called something else.
136: SETTINGS default_hard ; /* open() or init() should set something valid */
linux-master/sound/oss/dmasound/dmasound_atari.c
1173: /* used by AtaPlay() if all doubts whether there really is something
linux-master/sound/oss/dmasound/dmasound_core.c
551: /* ++TeSche: Is something like this necessary?
linux-master/sound/oss/dmasound/dmasound_paula.c
467: /* used by AmiPlay() if all doubts whether there really is something
linux-master/sound/oss/dmasound/dmasound_q40.c
408: /* used by Q40Play() if all doubts whether there really is something
linux-master/sound/pci/als4000.c
507: * register (alt_port + ALS4K_IOB_0E_IRQTYPE_SB_CR1E_MPU). Probably something
linux-master/sound/pci/asihpi/hpi6000.c
1757: if (error) /* something failed in the HPI/DSP interface */
1760: if (phr->error) /* something failed in the DSP */
linux-master/sound/pci/asihpi/hpi6205.c
2151: HPI_DEBUG_LOG(DEBUG, "something timed out!\n");
2180: /* something failed in the HPI/DSP interface */
2196: if (phr->error != 0) /* something failed in the DSP */
linux-master/sound/pci/asihpi/hpi_internal.h
77: something like size of array `msg' is negative.
linux-master/sound/pci/asihpi/hpicmn.c
630: May be cast to something else in the following switch statement.
linux-master/sound/pci/au88x0/au88x0_eq.c
9: * 02 July 2003: First time something works :)
linux-master/sound/pci/au88x0/au88x0_pcm.c
345: // do something to start the PCM engine
360: // do something to stop the PCM engine
linux-master/sound/pci/aw2/aw2-alsa.c
339: /* TODO: something to do ? */
linux-master/sound/pci/azt3328.c
96: * OPL3 hardware playback testing, try something like:
216: and then use something like
linux-master/sound/pci/azt3328.h
46: #define IRQ_SOMETHING 0x0001 /* something & ACK */
110:/** DirectX timer, main interrupt area (FIXME: and something else?) **/
linux-master/sound/pci/cs46xx/cs46xx_lib.c
3127: "Try reloading the ALSA driver, if you find something\n");
linux-master/sound/pci/emu10k1/emupcm.c
965: // if something goes wrong. However, we cannot unmute atomically,
linux-master/sound/pci/emu10k1/p16v.h
198: /* [3:0] Does something, but not documented. Probably capture enable.
linux-master/sound/pci/es1968.c
2052: pci_read_config_word(chip->pci, 0x58, &w); /* something magical with gpio and bus arb. */
2303: /* parallel in, has something to do with recording :) */
linux-master/sound/pci/hda/patch_ca0132.c
9207: * 0xfa92 in exram. This function seems to have something to do with
linux-master/sound/pci/hda/patch_hdmi.c
3727: /* Initialize the audio infoframe channel mask and checksum to something
linux-master/sound/ppc/awacs.c
879: /* looks like MASK_GAINLINE triggers something, so we set here
linux-master/sound/ppc/pmac.c
775: /* do something when headphone is plugged/unplugged? */
linux-master/sound/ppc/snd_ps3.c
157: * expected maximum DMA done time is 5.7ms + something (DMA itself).
linux-master/sound/soc/atmel/atmel_ssc_dai.c
486: * divider needed for that to work, fall back to something sensible.
504: * dividers needed for that to work, fall back to something sensible.
linux-master/sound/soc/codecs/adau1701.c
686: * Let the pll_clkdiv variable default to something that won't happen
linux-master/sound/soc/codecs/nau8821.c
1797: * (audible hiss). Set it to something better.
linux-master/sound/soc/codecs/nau8824.c
1754: * (audible hiss). Set it to something better.
linux-master/sound/soc/codecs/nau8825.c
2161: * (audible hiss). Set it to something better.
linux-master/sound/soc/codecs/rt5640.c
2188:#define BP_POLL_MAXCOUNT 200 /* assume something is wrong after this */
linux-master/sound/soc/codecs/rt5651.c
1657:#define BP_POLL_MAXCOUNT 200 /* assume something is wrong after this */
linux-master/sound/soc/codecs/rt5677.c
5318: * if there is something wrong with the interrupt status update. The
linux-master/sound/soc/codecs/wm8996.c
2289: * something or we stall our state machine.
linux-master/sound/soc/fsl/fsl_ssi.c
464: /* FIFO still empty -- something might be wrong */
linux-master/sound/soc/rockchip/rockchip_i2s_tdm.c
184: * like that is bad, especially when it influences something like the
linux-master/sound/soc/sh/hac.c
107: /* wait for HAC to receive something from the codec */
linux-master/sound/soc/soc-core.c
712: * means it's doing something,
linux-master/sound/soc/soc-dapm.c
2002: * context up to STANDBY as unless something
linux-master/sound/soc/tegra/tegra30_ahub.c
55: * is read from or sent to memory. However, that's not something the rest of
linux-master/sound/soc/ti/davinci-i2s.c
847: * If 'fck' is not present, the clk_get(dev, NULL) that follows may find something
linux-master/sound/sparc/dbri.c
1487: /* FIXME - let the CPU do something useful during these delays */
1875: /* FIXME: do something useful in case of underrun */
linux-master/sound/usb/line6/driver.c
381: /* should be equal or something went wrong */
linux-master/sound/usb/mixer.c
1333: /* something is wrong; assume it's either from/to 0dB */
1618: * rename it to "Headphone". We determine if something is a headphone
linux-master/sound/usb/mixer_us16x08.c
165: * code if something went wrong
linux-master/sound/usb/stream.c
310: /* If we're missing wChannelConfig, then guess something
linux-master/sound/usb/usx2y/usbusx2yaudio.c
529: usx2y_clients_stop(usx2y); // something is completely wrong > stop everything
linux-master/sound/usb/usx2y/usx2yhwdeppcm.c
482: usx2y_clients_stop(usx2y); // something is completely wrong > stop everything
linux-master/tools/include/linux/kconfig.h
28: * Getting something that works in C and CPP for an arg that may or may
linux-master/tools/include/linux/overflow.h
10: * to do something like:
linux-master/tools/include/nolibc/stdio.h
31: * of valid pointers to something else).
linux-master/tools/include/tools/config.h
16: * Getting something that works in C and CPP for an arg that may or may
linux-master/tools/include/uapi/drm/i915_drm.h
1101: * Note that having something in the write domain implies it's in the
3653: * it's something we can expect to see in the wild. See
3722: * device local-memory we can do something like:
linux-master/tools/include/uapi/linux/bpf.h
1908: * defaults to something like:
linux-master/tools/include/uapi/linux/seccomp.h
98: * syscalls if arguments are rewritten to something unsafe.
linux-master/tools/lib/bpf/bpf_core_read.h
498: * E.g., what in non-BPF world (or in BPF w/ BCC) would be something like:
linux-master/tools/lib/bpf/btf.c
1951: /* if something goes wrong later, we might end up with an extra string,
linux-master/tools/lib/bpf/libbpf.c
5953: * verifier will complain with something like:
5980: * verifier will complain with something like:
linux-master/tools/lib/bpf/libbpf.h
1845: * SEC("abc/something"), where acceptable "something" should be checked by
linux-master/tools/lib/bpf/libbpf_probes.c
449: * at all, it will emit something like "invalid func unknown#181".
linux-master/tools/lib/str_error_r.c
9: * a string, be it the buffer passed or something else.
13: * to check if it returned something else and copy that instead), breaks the
linux-master/tools/lib/subcmd/pager.c
15: * something different on Windows.
linux-master/tools/memory-model/Documentation/access-marking.txt
258: do_something(newval);
267: do_something_else();
333: do_something(newval);
339: do_something_else();
368: void do_something_locked(struct foo *fp)
374: do_something(fp);
388: do_something(fp);
414:All code paths leading from the do_something_locked() function's first
421:do_something().
426:means that it is safe to release global_lock and invoke do_something().
429:to do_something_locked(). The reason for this is that the synchronization
437:invocation of do_something() from do_something_locked() will see those
454: do_something(newval);
460: do_something_else();
498: do_something(newval);
505: do_something_else();
linux-master/tools/memory-model/Documentation/control-dependencies.txt
66: do_something();
70: do_something_else();
81: do_something();
84: do_something_else();
97: do_something();
100: do_something_else();
109: do_something();
112: do_something_else();
126: do_something();
129: do_something_else();
139: do_something_else();
152: do_something();
155: do_something_else();
linux-master/tools/memory-model/Documentation/explanation.txt
72:something which predicts, given a piece of computer code running on a
392: ... /* do something */
395: ... /* do something else */
401:something resembling:
406: ... /* do something */
408: ... /* do something else */
1751:For something a little more down-to-earth, let's see how the axiom
2500:something the compiler is forbidden to do. Augmenting a store with a
2555:other known addresses can cause trouble. If you have something like:
linux-master/tools/memory-model/Documentation/glossary.txt
15: 3 do_something(p->a);
linux-master/tools/memory-model/Documentation/litmus-tests.txt
185:The output is the result of something similar to a full state-space
linux-master/tools/memory-model/Documentation/recipes.txt
562:o If more than one of the links are something other than
linux-master/tools/memory-model/Documentation/simple.txt
119:view of this processing and data, in which case something like locking
linux-master/tools/mm/slabinfo.c
675: * Analyze debug options. Return false if something is amiss.
linux-master/tools/objtool/Documentation/objtool.txt
439:If you _really_ need objtool to ignore something, and are 100% sure
linux-master/tools/objtool/check.c
2921: * where GCC does something dumb like:
3010: * does something dumb like:
3457: * something 'BAD' happened. At the risk of taking the machine down,
linux-master/tools/objtool/elf.c
698: /* something went side-ways */
linux-master/tools/perf/Documentation/callchain-overhead-calculation.txt
25: /* do something */
29: /* do something */
44:recorded with callchains the output will show something like below
linux-master/tools/perf/Documentation/perf-arm-spe.txt
74: - Sampling, rather than tracing, cuts down the profiling problem to something more manageable for
linux-master/tools/perf/Documentation/perf-intel-pt.txt
50:Another limitation is the performance impact of tracing, something that will
583:the trace run and overwrite older data in the buffer so that whenever something
1299:Start an open-ended perf record, tracing the VM process, do something on the VM, and then ctrl-C to stop.
1363:Start an open-ended perf record, tracing the VM process, do something on the VM, and then ctrl-C to stop.
linux-master/tools/perf/Documentation/perf-record.txt
691:events until it receives a signal, meaning that something unusual was
linux-master/tools/perf/Documentation/perf-stat.txt
476:if the workload is actually bound by the CPU and not by something else.
linux-master/tools/perf/Documentation/security.txt
219:If something went wrong
linux-master/tools/perf/bench/sched-messaging.c
355: /* reaching here is something disaster */
linux-master/tools/perf/bench/sched-pipe.c
300: /* reaching here is something disaster */
linux-master/tools/perf/bench/sched-seccomp-notify.c
171: /* reaching here is something disaster */
linux-master/tools/perf/bench/syscall.c
157: /* reaching here is something disaster */
linux-master/tools/perf/bench/uprobe.c
179: /* reaching here is something of a disaster */
linux-master/tools/perf/builtin-bench.c
210: * to something meaningful:
linux-master/tools/perf/builtin-trace.c
4832: * global setting. If it fails we'll get something in 'perf trace -v'
linux-master/tools/perf/pmu-events/arch/x86/alderlake/adl-metrics.json
1456: "BriefDescription": "Average number of Uops issued by front-end when it issued something",
linux-master/tools/perf/pmu-events/arch/x86/broadwellde/uncore-memory.json
301: "PublicDescription": "Counts the number of cycles when the iMC is in critical thermal throttling. When this happens, all traffic is blocked. This should be rare unless something bad is going on in the platform. There is no filtering by rank for this event.",
linux-master/tools/perf/pmu-events/arch/x86/broadwellde/uncore-power.json
425: "PublicDescription": "Counts the number of cycles that we are in external PROCHOT mode. This mode is triggered when a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle to avoid damaging the chip.",
linux-master/tools/perf/pmu-events/arch/x86/broadwellx/uncore-memory.json
334: "PublicDescription": "Counts the number of cycles when the iMC is in critical thermal throttling. When this happens, all traffic is blocked. This should be rare unless something bad is going on in the platform. There is no filtering by rank for this event.",
linux-master/tools/perf/pmu-events/arch/x86/broadwellx/uncore-power.json
425: "PublicDescription": "Counts the number of cycles that we are in external PROCHOT mode. This mode is triggered when a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle to avoid damaging the chip.",
linux-master/tools/perf/pmu-events/arch/x86/cascadelakex/clx-metrics.json
887: "BriefDescription": "Average number of Uops issued by front-end when it issued something",
linux-master/tools/perf/pmu-events/arch/x86/cascadelakex/uncore-memory.json
657: "PublicDescription": "Counts the number of cycles when the iMC is in critical thermal throttling. When this happens, all traffic is blocked. This should be rare unless something bad is going on in the platform. There is no filtering by rank for this event.",
linux-master/tools/perf/pmu-events/arch/x86/cascadelakex/uncore-power.json
173: "PublicDescription": "Counts the number of cycles that we are in external PROCHOT mode. This mode is triggered when a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle to avoid damaging the chip.",
linux-master/tools/perf/pmu-events/arch/x86/emeraldrapids/uncore-power.json
170: "PublicDescription": "External Prochot : Counts the number of cycles that we are in external PROCHOT mode. This mode is triggered when a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle to avoid damaging the chip.",
linux-master/tools/perf/pmu-events/arch/x86/haswellx/uncore-memory.json
327: "PublicDescription": "Counts the number of cycles when the iMC is in critical thermal throttling. When this happens, all traffic is blocked. This should be rare unless something bad is going on in the platform. There is no filtering by rank for this event.",
linux-master/tools/perf/pmu-events/arch/x86/haswellx/uncore-power.json
457: "PublicDescription": "Counts the number of cycles that we are in external PROCHOT mode. This mode is triggered when a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle to avoid damaging the chip.",
linux-master/tools/perf/pmu-events/arch/x86/icelake/icl-metrics.json
667: "BriefDescription": "Average number of Uops issued by front-end when it issued something",
linux-master/tools/perf/pmu-events/arch/x86/icelakex/icx-metrics.json
889: "BriefDescription": "Average number of Uops issued by front-end when it issued something",
linux-master/tools/perf/pmu-events/arch/x86/icelakex/uncore-power.json
180: "PublicDescription": "External Prochot : Counts the number of cycles that we are in external PROCHOT mode. This mode is triggered when a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle to avoid damaging the chip.",
linux-master/tools/perf/pmu-events/arch/x86/ivytown/uncore-memory.json
301: "PublicDescription": "Counts the number of cycles when the iMC is in critical thermal throttling. When this happens, all traffic is blocked. This should be rare unless something bad is going on in the platform. There is no filtering by rank for this event.",
linux-master/tools/perf/pmu-events/arch/x86/ivytown/uncore-power.json
545: "PublicDescription": "Counts the number of cycles that we are in external PROCHOT mode. This mode is triggered when a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle to avoid damaging the chip.",
linux-master/tools/perf/pmu-events/arch/x86/jaketown/uncore-memory.json
236: "PublicDescription": "Counts the number of cycles when the iMC is in critical thermal throttling. When this happens, all traffic is blocked. This should be rare unless something bad is going on in the platform. There is no filtering by rank for this event.",
linux-master/tools/perf/pmu-events/arch/x86/jaketown/uncore-power.json
264: "PublicDescription": "Counts the number of cycles that we are in external PROCHOT mode. This mode is triggered when a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle to avoid damaging the chip.",
linux-master/tools/perf/pmu-events/arch/x86/rocketlake/rkl-metrics.json
667: "BriefDescription": "Average number of Uops issued by front-end when it issued something",
linux-master/tools/perf/pmu-events/arch/x86/sapphirerapids/spr-metrics.json
942: "BriefDescription": "Average number of Uops issued by front-end when it issued something",
linux-master/tools/perf/pmu-events/arch/x86/sapphirerapids/uncore-power.json
170: "PublicDescription": "External Prochot : Counts the number of cycles that we are in external PROCHOT mode. This mode is triggered when a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle to avoid damaging the chip.",
linux-master/tools/perf/pmu-events/arch/x86/silvermont/pipeline.json
199: "PublicDescription": "Machine clears happen when something happens in the machine that causes the hardware to need to take special care to get the right answer. When such a condition is signaled on an instruction, the front end of the machine is notified that it must restart, so no more instructions will be decoded from the current path. All instructions \"older\" than this one will be allowed to finish. This instruction and all \"younger\" instructions must be cleared, since they must not be allowed to complete. Essentially, the hardware waits until the problematic instruction is the oldest instruction in the machine. This means all older instructions are retired, and all pending stores (from older instructions) are completed. Then the new path of instructions from the front end are allowed to start into the machine. There are many conditions that might cause a machine clear (including the receipt of an interrupt, or a trap or a fault). All those conditions (including but not limited to MACHINE_CLEARS.MEMORY_ORDERING, MACHINE_CLEARS.SMC, and MACHINE_CLEARS.FP_ASSIST) are captured in the ANY event. In addition, some conditions can be specifically counted (i.e. SMC, MEMORY_ORDERING, FP_ASSIST). However, the sum of SMC, MEMORY_ORDERING, and FP_ASSIST machine clears will not necessarily equal the number of ANY.",
linux-master/tools/perf/pmu-events/arch/x86/skylake/skl-metrics.json
621: "BriefDescription": "Average number of Uops issued by front-end when it issued something",
linux-master/tools/perf/pmu-events/arch/x86/skylakex/skx-metrics.json
869: "BriefDescription": "Average number of Uops issued by front-end when it issued something",
linux-master/tools/perf/pmu-events/arch/x86/skylakex/uncore-memory.json
347: "PublicDescription": "Counts the number of cycles when the iMC is in critical thermal throttling. When this happens, all traffic is blocked. This should be rare unless something bad is going on in the platform. There is no filtering by rank for this event.",
linux-master/tools/perf/pmu-events/arch/x86/skylakex/uncore-power.json
173: "PublicDescription": "Counts the number of cycles that we are in external PROCHOT mode. This mode is triggered when a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle to avoid damaging the chip.",
linux-master/tools/perf/pmu-events/arch/x86/snowridgex/uncore-power.json
179: "PublicDescription": "External Prochot : Counts the number of cycles that we are in external PROCHOT mode. This mode is triggered when a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle to avoid damaging the chip.",
linux-master/tools/perf/pmu-events/arch/x86/tigerlake/tgl-metrics.json
667: "BriefDescription": "Average number of Uops issued by front-end when it issued something",
linux-master/tools/perf/pmu-events/jevents.py
271: # it's not realistic to keep adding these, we need something more scalable ...
linux-master/tools/perf/scripts/python/export-to-postgresql.py
86:# when something (a selected event) happened. The memory address is the instruction pointer or 'ip'.
linux-master/tools/perf/scripts/python/exported-sql-viewer.py
22:# widths to suit will display something like:
4347:widths to suit will display something like:
linux-master/tools/perf/tests/code-reading.c
459:static void do_sort_something(void)
476:static void sort_something(void)
481: do_sort_something();
484:static void syscall_something(void)
499:static void fs_something(void)
514:static void do_something(void)
516: fs_something();
518: sort_something();
520: syscall_something();
682: do_something();
linux-master/tools/perf/tests/shell/base_probe/settings.sh
13: # when $PERFSUITE_RUN_DIR is set to something, all the logs and temp files will be placed there
14: # --> the $PERFSUITE_RUN_DIR/perf_something/examples and $PERFSUITE_RUN_DIR/perf_something/logs
linux-master/tools/perf/tests/shell/lib/coresight.sh
50: # to see that we are recording something and at least a minimum
linux-master/tools/perf/tests/shell/stat_all_metrics.sh
19: # Failed again, possibly the workload was too small so retry with something
linux-master/tools/perf/tests/shell/stat_all_pfm.sh
34: # too small so retry with something longer.
linux-master/tools/perf/tests/shell/stat_all_pmu.sh
13: # too small so retry with something longer.
linux-master/tools/perf/util/cs-etm.c
2609: * which means something somewhere went very wrong. No
3120: * Couldn't find the buffer corresponding to this aux record, something went wrong. Warn but
linux-master/tools/perf/util/demangle-rust.c
86: /* Not long enough to contain "::h" + hash + something else */
linux-master/tools/perf/util/disasm.c
603: * x86 SIB addressing has something like 0x8(%rax, %rcx, 1)
linux-master/tools/perf/util/dwarf-aux.c
506: * @dw_die: a DIE for something declared.
linux-master/tools/perf/util/metricgroup.h
55: * by 6.4e-05 (typically converting a unit like cache lines to something
linux-master/tools/perf/util/pmu.c
1188: * something to true, pass 1 for val rather than a pre shifted value.
linux-master/tools/perf/util/probe-event.c
1921: * if address == 0, kernel reports something like:
linux-master/tools/perf/util/srcline.c
673: * Send our request and then *deliberately* send something that can't be
linux-master/tools/perf/util/thread-stack.c
428: * to report something misleading, so flush the stack.
linux-master/tools/perf/util/trace-event-info.c
329: * /proc/kallsyms (or something specified via --kallsyms, in a
linux-master/tools/perf/util/trace-event-parse.c
318: * If the flag is not numeric, see if it is something that
linux-master/tools/power/acpi/Makefile.config
28:# make the build silent. Set this to something else to make it noisy again.
52:# to something more interesting, like "arm-linux-". If you want
linux-master/tools/power/cpupower/Makefile
28:# make the build silent. Set this to something else to make it noisy again.
86:# to something more interesting, like "arm-linux-". If you want
linux-master/tools/power/pm-graph/README
156: are waiting for something and when. It also sets a suite of kprobes on
linux-master/tools/power/pm-graph/sleepgraph.py
2357: # something else (possibly a trace marker)
linux-master/tools/scripts/utilities.mak
28:# something that won't be converted, so that the
linux-master/tools/testing/ktest/config-bisect.pl
357:# 0 is equal +1 b has something a does not
359:# -1 if a has something b does not
linux-master/tools/testing/ktest/examples/crosstests.conf
12:# such that the compiler binaries are something like:
linux-master/tools/testing/ktest/examples/include/defaults.conf
102:# ADD_CONFIG is usually something to add configs to all machines,
114:# something else, ktest will power cycle or reboot the target box
linux-master/tools/testing/ktest/examples/kvm.conf
4:# The guest is called 'Guest' and this would be something that
linux-master/tools/testing/ktest/examples/test.conf
45:# In case you need to add a patch for a bisect or something
linux-master/tools/testing/ktest/examples/vmware.conf
21:# The guest is called 'Guest' and this would be something that
linux-master/tools/testing/ktest/ktest.pl
74:# value something that is common.
240:# set when a test is something other that just building or install
441: If you use ttywatch server, something like the following would work.
503: here. Use something like /boot/grub2/grub.cfg to search.
853: # Note if a test is something other than build, then we
2661: # add something to distinguish this build
linux-master/tools/testing/ktest/sample.conf
338:# If you use ttywatch server, something like the following would work.
1100:# when something other than the BISECT_TYPE fails, ktest.pl will
1158:# In case the specificed test returns something other than just
1164:# In case the specificed test returns something other than just
1170:# If you need to abort the bisect if the test discovers something
1177:# nor bad, but something else happened (another bug detected)
1232:# disabled because it depended on something that wasn't set.
linux-master/tools/testing/kunit/kunit_kernel.py
277: 'on a different architecture with something like "--arch=x86_64".'
linux-master/tools/testing/radix-tree/idr-test.c
301: * or we find something at an ID we didn't expect, that's a bug.
linux-master/tools/testing/radix-tree/maple.c
35825: /* Storing something at 1 requires memory allocation */
35827: /* Storing something at 0 does not */
linux-master/tools/testing/selftests/arm64/signal/test_signals_utils.h
124: * something invalid in streaming mode, or potentially even
linux-master/tools/testing/selftests/arm64/signal/testcases/fake_sigreturn_bad_magic.c
23: /* just to fill the ucontext_t with something real */
33: * use a well known NON existent bad magic...something
linux-master/tools/testing/selftests/arm64/signal/testcases/fake_sigreturn_bad_size.c
26: /* just to fill the ucontext_t with something real */
linux-master/tools/testing/selftests/arm64/signal/testcases/fake_sigreturn_bad_size_for_magic0.c
23: /* just to fill the ucontext_t with something real */
linux-master/tools/testing/selftests/arm64/signal/testcases/fake_sigreturn_duplicated_fpsimd.c
23: /* just to fill the ucontext_t with something real */
linux-master/tools/testing/selftests/arm64/signal/testcases/fake_sigreturn_misaligned_sp.c
21: /* just to fill the ucontext_t with something real */
linux-master/tools/testing/selftests/arm64/signal/testcases/fake_sigreturn_missing_fpsimd.c
25: /* just to fill the ucontext_t with something real */
linux-master/tools/testing/selftests/arm64/signal/testcases/tpidr2_siginfo.c
70: * that we may need to revisit this in future if something
linux-master/tools/testing/selftests/bpf/prog_tests/bpf_obj_pinning.c
65: * something like below. But the whole point is that we actually don't
linux-master/tools/testing/selftests/bpf/prog_tests/get_branch_snapshot.c
122: * Add a check for < 10 so that we get heads-up when something
linux-master/tools/testing/selftests/bpf/prog_tests/sock_addr.c
2405: /* AF_UNIX sockets have to be bound to something to trigger the recvmsg bpf program. */
linux-master/tools/testing/selftests/bpf/progs/bpf_mod_race.c
25:/* The trace of execution is something like this:
linux-master/tools/testing/selftests/bpf/progs/core_reloc_types.h
1120: /* the only valid one is enum, to check that something still succeeds */
linux-master/tools/testing/selftests/bpf/progs/sockopt_sk.c
123: * SOL_CUSTOM, something is wrong!
linux-master/tools/testing/selftests/bpf/progs/strobemeta.h
287: * This schema allows to use something like:
linux-master/tools/testing/selftests/bpf/progs/test_custom_sec_handlers.c
38:SEC("custom/something")
linux-master/tools/testing/selftests/bpf/progs/test_global_func15.c
46: * there is something wrong with precision tracking for R0 at
linux-master/tools/testing/selftests/bpf/progs/test_stack_var_off.c
31: /* Append something to the buffer. The offset where we write is not
linux-master/tools/testing/selftests/bpf/test_lpm_map.c
319: * something on every lookup. For statistics, use this:
linux-master/tools/testing/selftests/bpf/verifier/calls.c
2272: * do something bad;
linux-master/tools/testing/selftests/bpf/xskxceiver.c
2101: /* Valid packet for synch so that something is received */
2138: /* Valid packet for synch so that something is received */
linux-master/tools/testing/selftests/cgroup/test_kmem.c
38: "/something-non-existent-with-a-long-name-%64lu-%d",
linux-master/tools/testing/selftests/clone3/clone3_selftests.h
51: /* Set to something that will always cause EINVAL. */
linux-master/tools/testing/selftests/clone3/clone3_set_tid.c
350: * something like 'NSpid: pid 42 1'.
linux-master/tools/testing/selftests/firmware/fw_fallback.sh
178: echo "and see if you have something like this:"
linux-master/tools/testing/selftests/firmware/fw_filesystem.sh
225: # cmp agrees, so something is off.
linux-master/tools/testing/selftests/ftrace/test.d/ftrace/fgraph-filter-stack.tc
24:# filter something, schedule is always good
49:# Make sure we did find something
linux-master/tools/testing/selftests/ftrace/test.d/ftrace/fgraph-filter.tc
16:# filter something, schedule is always good
34:# Make sure we did find something
linux-master/tools/testing/selftests/ftrace/test.d/ftrace/func_profiler.tc
58:echo "make sure something other than scheduler is being traced"
linux-master/tools/testing/selftests/futex/README
56: Perhaps something like "wait-wake-1" "wait-wake-2" is adequate, leaving the
linux-master/tools/testing/selftests/hid/tests/base.py
350: If this fail, there is something wrong in the device report
linux-master/tools/testing/selftests/hid/tests/test_multitouch.py
535: If this fail, there is something wrong in the device report
linux-master/tools/testing/selftests/hid/tests/test_wacom_generic.py
385: Opaque tablet similar to something in the CTL product line.
linux-master/tools/testing/selftests/iommu/iommufd_fail_nth.c
15: * If something is actually going wrong.
linux-master/tools/testing/selftests/kselftest.h
414: * something sensible if some tests have already been run
linux-master/tools/testing/selftests/kselftest_harness.h
133: * This forces a "pass" after reporting why something is being skipped
linux-master/tools/testing/selftests/kvm/lib/kvm_util.c
1724: * Invoke KVM_RUN on a vCPU until KVM returns something other than -EINTR.
linux-master/tools/testing/selftests/kvm/s390x/cmma_test.c
35: * so use_cmma goes on and the CMMA related ioctls do something.
linux-master/tools/testing/selftests/kvm/s390x/shared_zeropage_test.c
29: * Returns 1 if the shared zeropage is mapped, 0 if something else is mapped.
linux-master/tools/testing/selftests/kvm/x86_64/pmu_counters_test.c
73: * supported by KVM to verify KVM doesn't freak out and do something
308: * guarantee that currently undefined MSR indices won't be used for something
linux-master/tools/testing/selftests/kvm/x86_64/state_test.c
301: * supported features, even if something goes awry in saving
linux-master/tools/testing/selftests/landlock/fs_test.c
3668: * something else but truncate restricted: ftruncate works
linux-master/tools/testing/selftests/livepatch/functions.sh
276: # Dump something unique into the dmesg log, then stash the entry
linux-master/tools/testing/selftests/mm/compaction_test.c
245: /* Write something (in this case the address of the map) to
linux-master/tools/testing/selftests/mm/pagemap_ioctl.c
1031: /* Write something to the page to get the written bit enabled on the page */
linux-master/tools/testing/selftests/mm/pkey-helpers.h
149: * These are technically racy. since something could
linux-master/tools/testing/selftests/mm/protection_keys.c
976: * So, make sure that we use something that's a multiple
1359: * So, make sure that we use something that's a multiple
linux-master/tools/testing/selftests/mm/soft-dirty.c
33: // Write something to the page to get the dirty bit enabled on the page
108: // Write something to the page to get the dirty bit enabled on the page
linux-master/tools/testing/selftests/mm/split_huge_page_test.c
232: /* write something to the file, so a file-backed THP can be allocated */
linux-master/tools/testing/selftests/mqueue/mq_open_tests.c
170: "to something that will work\n"
182: "to something that will work\n"
linux-master/tools/testing/selftests/net/icmp.sh
58:# in case something goes wrong
linux-master/tools/testing/selftests/net/ioam6.sh
67:# | Schema Data | something that will be 4n-aligned |
140: "something that will be 4n-aligned" # Schema Data
linux-master/tools/testing/selftests/net/ioam6_parser.c
46: .sc_data = "something that will be 4n-aligned",
linux-master/tools/testing/selftests/net/mptcp/mptcp_connect.c
991: fprintf(stderr, "accept: something wrong: ip connection from port 0");
997: fprintf(stderr, "accept: something wrong: ipv6 connection from port 0");
linux-master/tools/testing/selftests/net/openvswitch/ovs-dpctl.py
745: # something like 'field.' where '.' is a
linux-master/tools/testing/selftests/net/tcp_ao/connect-deny.c
116: try_accept("Wrong password", port++, "something that is not DEFAULT_TEST_PASSWORD",
linux-master/tools/testing/selftests/powerpc/eeh/eeh-functions.sh
60: # Bump the max freeze count to something absurd so we don't
linux-master/tools/testing/selftests/powerpc/mm/pkey_siginfo.c
188: * something unexpected
linux-master/tools/testing/selftests/powerpc/mm/stack_expansion_ldst.c
67: // Do something to prevent the stack frame being popped prior to
linux-master/tools/testing/selftests/rcutorture/bin/kvm-check-branches.sh
15:# produce something that this simple script can understand. The reason
linux-master/tools/testing/selftests/rcutorture/bin/torture.sh
312:# in any way. So also supply --torture if you need something other than
linux-master/tools/testing/selftests/resctrl/resctrl_val.c
611: * be something else if perf imc event is not available.
linux-master/tools/testing/selftests/splice/short_splice_read.sh
37: echo "FAIL: something else went wrong" >&2
65: echo "FAIL: something else went wrong" >&2
linux-master/tools/testing/selftests/tc-testing/tdc.py
581: print('got something on stdin')
linux-master/tools/testing/selftests/vDSO/vdso_test_correctness.c
442: * Test getcpu() last so that, if something goes wrong setting affinity,
linux-master/tools/testing/selftests/x86/single_step_syscall.c
187: * kernel has to do something clever to avoid losing track of
linux-master/tools/testing/selftests/x86/syscall_nt.c
86: * glibc, but glibc would have to do something rather surprising
linux-master/tools/testing/selftests/x86/test_shadow_stack.c
549: * 1. Finds an empty place by mapping and unmapping something.
linux-master/tools/usb/ffs-aio-example/simple/device_app/aio_simple.c
318: /* if something was submitted we wait for event */
linux-master/tools/usb/usbip/COPYING
323:be called something other than `show w' and `show c'; they could even be
linux-master/tools/usb/usbip/INSTALL
132:is something like `gnu-as' or `x' (for the X Window System). The
linux-master/virt/kvm/kvm_main.c
4037: * currently running, because it got preempted by something
( rg something linux-master --sort path; ) 0.34s user 1.11s system 99% cpu 1.460 total
~/Downloads ❯
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment