Searched full:similarities (Results 1 – 22 of 22) sorted by relevance
/openbmc/qemu/scripts/qapi/ |
H A D | pylintrc | 10 # you want to run only the similarities checker, you can use "--disable=all 11 # --enable=similarities". If you want to run only the classes checker, but have 48 [SIMILARITIES] 50 # Ignore import statements themselves when computing similarities.
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | pylintrc | 8 # you want to run only the similarities checker, you can use "--disable=all 9 # --enable=similarities". If you want to run only the classes checker, but have 57 [SIMILARITIES]
|
/openbmc/qemu/python/ |
H A D | setup.cfg | 138 # you want to run only the similarities checker, you can use "--disable=all 139 # --enable=similarities". If you want to run only the classes checker, but have 164 [pylint.similarities] 165 # Ignore imports when computing similarities.
|
/openbmc/linux/fs/ocfs2/ |
H A D | Kconfig | 14 system with many similarities to ext3. It supports 64 bit inode
|
/openbmc/linux/tools/perf/Documentation/ |
H A D | intel-bts.txt | 8 similarities because it can also identify every branch a program takes. A
|
/openbmc/linux/arch/x86/platform/geode/ |
H A D | geos.c | 10 * TODO: There are large similarities with leds-net5501.c
|
H A D | alix.c | 11 * TODO: There are large similarities with leds-net5501.c
|
/openbmc/linux/arch/arm/kernel/ |
H A D | irq.c | 19 * Naturally it's not a 1:1 relation, but there are similarities.
|
/openbmc/linux/Documentation/driver-api/phy/ |
H A D | samsung-usb2.rst | 9 among many SoCs. In spite of the similarities it proved difficult to
|
/openbmc/linux/arch/mips/include/asm/ |
H A D | bootinfo.h | 20 * numbers do not necessarily reflect technical relations or similarities
|
H A D | cpu-features.h | 355 /* MIPSR2 - MIPSR6 have a lot of similarities */
|
/openbmc/linux/Documentation/filesystems/ |
H A D | ocfs2.rst | 8 system with many similarities to ext3. It supports 64 bit inode
|
H A D | xfs-online-fsck-design.rst | 181 discusses the similarities and differences with existing tools.
|
/openbmc/u-boot/doc/device-tree-bindings/gpio/ |
H A D | nvidia,tegra186-gpio.txt | 5 layouts for the controllers share many similarities, but also some significant
|
/openbmc/linux/Documentation/devicetree/bindings/gpio/ |
H A D | nvidia,tegra186-gpio.yaml | 16 layouts for the controllers share many similarities, but also some
|
/openbmc/linux/Documentation/bpf/ |
H A D | ringbuf.rst | 72 There are a bunch of similarities between perf buffer
|
/openbmc/qemu/docs/devel/ |
H A D | build-system.rst | 9 "make" to build the project. This is about where the similarities with
|
/openbmc/linux/arch/arm64/crypto/ |
H A D | sha512-armv8.pl | 453 # You'll surely note a lot of similarities with sha256-armv4 module,
|
/openbmc/linux/Documentation/driver-api/ |
H A D | libata.rst | 988 Thanks to Alan Cox for pointing out similarities between SATA and SCSI,
|
/openbmc/linux/drivers/usb/storage/ |
H A D | alauda.c | 15 * sddr09 driver which has many similarities, and with some help from the
|
/openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
H A D | bitbake-user-manual-metadata.rst | 9 BitBake files have their own syntax. The syntax has similarities to
|
/openbmc/linux/tools/memory-model/Documentation/ |
H A D | explanation.txt | 1261 hb, despite their similarities to rfe. For example, suppose we have
|