/openbmc/u-boot/drivers/reset/aspeed/ |
H A D | Kconfig | 8 resets that are supported by watchdog. The main limitation though 18 resets that are supported by watchdog. The main limitation though 28 resets that are supported by watchdog. The main limitation though
|
/openbmc/linux/Documentation/driver-api/usb/ |
H A D | persist.rst | 20 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
|
/openbmc/linux/Documentation/process/ |
H A D | 6.Followthrough.rst | 28 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
|
H A D | 8.Conclusion.rst | 13 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
|
H A D | researcher-guidelines.rst | 34 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
|
H A D | 5.Posting.rst | 22 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
|
H A D | 2.Process.rst | 103 kernels go out with a handful of known regressions though, hopefully, none 172 though this acceptance is not a guarantee that the patch will make it 246 etc. This chain of repositories can be arbitrarily long, though it rarely 293 Use of the MMOTM tree is likely to be a frustrating experience, though; 331 improve quickly. Entry into staging is not the end of the story, though; 353 for being difficult to learn and use, though it has gotten better over 400 There are lists hosted elsewhere, though; a number of them are at 418 important to filter on both the topic of interest (though note that
|
H A D | 3.Early-stage.rst | 8 though, much of the groundwork for success is best laid before the first 19 example. In others, though, it is tempting to confuse the real problem 31 immediate problem. To the wider kernel community, though, it was seen as a 137 the place to start. That file tends to not always be up to date, though,
|
/openbmc/phosphor-logging/extensions/openpower-pels/ |
H A D | paths.hpp | 29 * This is still in paths.c/hpp even though it doesn't return a path 39 * This is still in paths.c/hpp even though it doesn't return a path
|
/openbmc/linux/drivers/regulator/ |
H A D | bd71828-regulator.c | 281 * 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
|
/openbmc/phosphor-dbus-interfaces/yaml/org/open_power/OCC/ |
H A D | PassThrough.interface.yaml | 15 should still be bytes worth of data (as though using 26 still be bytes worth of data (as though using array[byte]), so
|
/openbmc/linux/Documentation/filesystems/ext4/ |
H A D | about.rst | 8 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
|
/openbmc/linux/tools/testing/selftests/powerpc/pmu/ebb/ |
H A D | fork_cleanup_test.c | 28 /* 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()
|
/openbmc/linux/Documentation/filesystems/ |
H A D | dlmfs.rst | 29 - 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
|
/openbmc/linux/Documentation/core-api/ |
H A D | dma-isa-lpc.rst | 8 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
|
/openbmc/linux/drivers/pci/hotplug/ |
H A D | TODO | 28 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
|
/openbmc/linux/Documentation/bpf/ |
H A D | bpf_prog_run.rst | 80 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
|
/openbmc/linux/arch/powerpc/include/asm/ |
H A D | exception-64e.h | 27 * 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
|
/openbmc/linux/arch/sparc/kernel/ |
H A D | trampoline_32.S | 47 wr %g1, 0x0, %psr ! traps off though 101 wr %g1, 0x0, %psr ! traps off though 160 wr %g1, 0x0, %psr ! traps off though
|
/openbmc/linux/Documentation/hid/ |
H A D | uhid.rst | 59 You may decide to ignore UHID_OPEN/UHID_CLOSE, though. I/O is allowed even 60 though the device may have no users. 88 might make use of O_NONBLOCK, though. 169 This may be received even though you haven't received UHID_OPEN yet.
|
/openbmc/linux/Documentation/i2c/ |
H A D | gpio-fault-injection.rst | 97 and wait for the next bus clock. The process is interruptible, though. 127 process is interruptible, though. 136 using. Results may vary depending on that, though.
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/usbip-tools/ |
H A D | usbip-tools.bb | 5 # Though have rewritten all the logic to be much simpler 65 # Even though the libusbip is set to version 0.0.1, set the package version to match kernel
|
/openbmc/openbmc/poky/meta/recipes-extended/groff/files/ |
H A D | 0001-build-Fix-Savannah-64681-webpage.ps-deps.patch | 30 +# soelim even though the document doesn't require them. 43 +# soelim even though the document doesn't require them.
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 270 | 61 # (qemu-img create does not like it, though, because null-co does not 83 # 2 MB. (Anything from 256 kB should work, though, because then one L2
|
/openbmc/linux/Documentation/driver-api/ |
H A D | xillybus.rst | 94 sized buffers (even though such buffers are used by Xillybus under the hood). 125 possibly pressing CTRL-C as some stage, even though the xillybus_* pipes have 237 Even though PCI Express is hotpluggable in general, a typical motherboard 244 even though the PCIe standard requires a graceful recovery. 267 Even though a non-segmented data stream is presented to the user at both 294 partial DMA buffers is somewhat different, though. The user can tell the
|