Home
last modified time | relevance | path

Searched full:though (Results 1 – 25 of 3840) sorted by relevance

12345678910>>...154

/kernel/linux/linux-6.6/Documentation/driver-api/usb/
Dpersist.rst20 required to behave as though the device has been unplugged. It's a
29 though they had disconnected. This is always safe and it is the
48 even though suspend current may have been maintained while the system
52 it's as though you had unplugged all the USB devices. Yes, it's
87 kernel treats the device as though it had merely been reset instead of
97 behaves as though the old device had been unplugged and a new device
/kernel/linux/linux-5.10/Documentation/driver-api/usb/
Dpersist.rst20 required to behave as though the device has been unplugged. It's a
29 though they had disconnected. This is always safe and it is the
48 even though suspend current may have been maintained while the system
52 it's as though you had unplugged all the USB devices. Yes, it's
87 kernel treats the device as though it had merely been reset instead of
97 behaves as though the old device had been unplugged and a new device
/kernel/linux/linux-5.10/Documentation/process/
D6.Followthrough.rst28 process. Life can be made much easier, though, if you keep a few things in
67 explanation not prove persuasive, though, especially if others start to
100 though, and not before all other alternatives have been explored. And bear
140 complete (and you have added yourself to the MAINTAINERS file), though, it
148 though; you still need to be responsive to developers who have questions or
151 More importantly, though: inclusion into the mainline puts your code into
178 is insufficient motivation, though, it's also worth considering that the
D8.Conclusion.rst14 documents in HTML or PDF format (though the version of TeX shipped by some
42 All of these books suffer from a common fault, though: they tend to be
68 The kernel can always benefit from a larger developer base, though. There
D5.Posting.rst23 work being done is complex, though, there is a lot to be gained by getting
75 subsystem tree, though, to facilitate wider testing and review. Depending
113 - Do not overdo it, though. One developer once posted a set of edits
123 finger the last patch as the one which caused the problem, even though
129 done. When done properly, though, it is time well spent.
322 followed though; if you use it, remember that information in the
329 patches with the proper threading. If you have a long series, though, and
/kernel/linux/linux-6.6/Documentation/process/
D6.Followthrough.rst28 process. Life can be made much easier, though, if you keep a few things in
74 explanation not prove persuasive, though, especially if others start to
107 though, and not before all other alternatives have been explored. And bear
147 complete (and you have added yourself to the MAINTAINERS file), though, it
155 though; you still need to be responsive to developers who have questions or
158 More importantly, though: inclusion into the mainline puts your code into
185 is insufficient motivation, though, it's also worth considering that the
D8.Conclusion.rst13 format (though the version of TeX shipped by some distributions runs into
40 All of these books suffer from a common fault, though: they tend to be
66 The kernel can always benefit from a larger developer base, though. There
Dresearcher-guidelines.rst34 code) produced by the Linux kernel community is welcome, though research
39 repositories, is clearly permissible. Though, as with any research,
51 contributors. As a general rule, though, the kernel community derives
54 with others who have different goals. Responding to a survey, though, is a
D5.Posting.rst22 work being done is complex, though, there is a lot to be gained by getting
74 subsystem tree, though, to facilitate wider testing and review. Depending
112 - Do not overdo it, though. One developer once posted a set of edits
122 finger the last patch as the one which caused the problem, even though
128 done. When done properly, though, it is time well spent.
351 followed though; if you use it, remember that information in the
358 patches with the proper threading. If you have a long series, though, and
/kernel/linux/linux-6.6/drivers/regulator/
Dbd71828-regulator.c281 * though => allow setting all states to support
316 * though => allow setting all states to support
351 * though => allow setting all states to support
468 * though => allow setting all states to support
502 * though => allow setting all states to support
536 * though => allow setting all states to support
571 * though => allow setting all states to support
661 * though => allow setting all states to support
/kernel/linux/linux-5.10/drivers/regulator/
Dbd71828-regulator.c308 * though => allow setting all states to support
349 * though => allow setting all states to support
390 * though => allow setting all states to support
505 * though => allow setting all states to support
545 * though => allow setting all states to support
585 * though => allow setting all states to support
626 * though => allow setting all states to support
728 * though => allow setting all states to support
/kernel/linux/linux-6.6/Documentation/filesystems/ext4/
Dabout.rst8 as well, though they do not support all the features that ext4 supports,
28 pages on x86 and the block layer's default block size), though the
/kernel/linux/linux-5.10/Documentation/filesystems/ext4/
Dabout.rst8 as well, though they do not support all the features that ext4 supports,
28 pages on x86 and the block layer's default block size), though the
/kernel/linux/linux-5.10/Documentation/filesystems/
Ddlmfs.rst29 - Right now it only works with the OCFS2 DLM, though support for other
55 find its heartbeat area, though it will eventually support heartbeat
84 maximum currently supported LVB length is 64 bytes (though that is an
/kernel/linux/linux-5.10/Documentation/core-api/
Ddma-isa-lpc.rst8 controller. Even though ISA is more or less dead today the LPC bus
55 API. Do _not_ use isa_virt_to_bus() even though it does the same
58 is really all you need. Remember that even though the DMA controller
/kernel/linux/linux-6.6/Documentation/filesystems/
Ddlmfs.rst29 - Right now it only works with the OCFS2 DLM, though support for other
55 find its heartbeat area, though it will eventually support heartbeat
84 maximum currently supported LVB length is 64 bytes (though that is an
/kernel/linux/linux-6.6/Documentation/core-api/
Ddma-isa-lpc.rst8 controller. Even though ISA is more or less dead today the LPC bus
55 API. Do _not_ use isa_virt_to_bus() even though it does the same
58 is really all you need. Remember that even though the DMA controller
/kernel/linux/linux-6.6/tools/testing/selftests/powerpc/pmu/ebb/
Dfork_cleanup_test.c28 /* Even though we have EBE=0 we can still see the EBB regs */ in child()
35 /* We can still read from the event, though it is on our parent */ in child()
/kernel/linux/linux-5.10/tools/testing/selftests/powerpc/pmu/ebb/
Dfork_cleanup_test.c28 /* Even though we have EBE=0 we can still see the EBB regs */ in child()
35 /* We can still read from the event, though it is on our parent */ in child()
/kernel/linux/linux-6.6/drivers/pci/hotplug/
DTODO28 though pci_hotplug.h declares it private. See get_max_bus_speed() for an
49 though pci_hotplug.h declares it private. See sn_hp_destroy() for an
/kernel/linux/linux-6.6/arch/sparc/kernel/
Dtrampoline_32.S47 wr %g1, 0x0, %psr ! traps off though
101 wr %g1, 0x0, %psr ! traps off though
160 wr %g1, 0x0, %psr ! traps off though
/kernel/linux/linux-5.10/arch/sparc/kernel/
Dtrampoline_32.S47 wr %g1, 0x0, %psr ! traps off though
101 wr %g1, 0x0, %psr ! traps off though
160 wr %g1, 0x0, %psr ! traps off though
/kernel/linux/linux-6.6/arch/powerpc/include/asm/
Dexception-64e.h27 * SPRGs are user-readable though, thus we might have to change some of
39 * exception frame is smaller than the CRIT or MC one though
78 * though we currently don't test for overflow). It provides you with a
/kernel/linux/linux-5.10/arch/powerpc/include/asm/
Dexception-64e.h27 * SPRGs are user-readable though, thus we might have to change some of
39 * exception frame is smaller than the CRIT or MC one though
78 * though we currently don't test for overflow). It provides you with a
/kernel/linux/linux-6.6/Documentation/bpf/
Dbpf_prog_run.rst80 the regular (non-live) mode. The XDP program will be executed as though the
84 though it arrived on that ifindex, and if it returns ``XDP_TX``, the packet
85 will be transmitted *out* of that same interface. Do note, though, that

12345678910>>...154