Home
last modified time | relevance | path

Searched full:pretty (Results 1 – 25 of 94) sorted by relevance

1234

/Documentation/i2c/busses/
Di2c-taos-evm.rst44 The communication protocol is text-based and pretty simple. It is
/Documentation/i2c/
Dten-bit-addresses.rst31 Note that 10-bit address devices are still pretty rare, so the limitations
/Documentation/networking/
Dfib_trie.rst87 level compression. This part follows the original paper pretty closely
98 The route manipulation functions. Should conform pretty closely to the
Deql.rst40 TCP implementation is pretty fast though.--)
373 6.4 Kbyte/s, which I think is pretty cool. :)
/Documentation/arch/arm/
Dinterrupts.rst9 Firstly, it contains some pretty major changes to the way we handle the
110 The "level" handler is what we currently have - its pretty simple.
/Documentation/filesystems/
Dgfs2.rst41 is pretty close.
/Documentation/driver-api/
Dnvmem.rst19 drivers/misc, where they all had to duplicate pretty much the same code to
24 the solutions used were pretty much different from one driver to another, there
/Documentation/power/
Ds2ram.rst23 way to debug these things, and it's actually pretty powerful (but
/Documentation/filesystems/bcachefs/
DCodingStyle.rst73 The most important tool for introspection is the humble pretty printer - in
76 Pretty printers are wonderful, because they compose and you can use them
/Documentation/arch/x86/x86_64/
Dfake-numa-for-cpusets.rst76 cpusets. Since cpusets can form a hierarchy, you can create some pretty
/Documentation/bpf/
Dbtf.rst13 The debug info is used for map pretty print, function signature, etc. The
149 pretty print. At most one encoding can be specified for the int type.
227 equal to ``30``. This is because the original use case is map pretty print
623 pretty print types, dump func signatures and line info, etc.
741 tool has full btf knowledge and is able to pretty print map key/values, dump
902 5.1 bpftool map pretty print
927 bpftool is able to pretty print like below:
/Documentation/driver-api/media/drivers/
Dcx88-devel.rst94 I'm pretty sure when no IR signal is present the receiver is always in a
/Documentation/misc-devices/
Dlis3lv02d.rst97 A: The sensor is pretty sensitive, so your hands can do it. Lift it
/Documentation/scheduler/
Dsched-nice-design.rst8 Nice levels were always pretty weak under Linux and people continuously
/Documentation/dev-tools/kunit/api/
Dfunctionredirection.rst46 Using static stubs is pretty straightforward:
/Documentation/devicetree/bindings/iio/
Dst,st-sensors.yaml9 description: The STMicroelectronics sensor devices are pretty straight-forward
/Documentation/process/
Dsubmitting-patches.rst55 pretty convincing, but not all bugs are that blatant. Even if the
153 The following ``git config`` settings can be used to add a pretty format for
158 [pretty]
163 $ git log -1 --pretty=fixes 54a4f0239f2e
406 pass it on as an open-source patch. The rules are pretty simple: if you
637 alphabetically by subject line - pretty much any email reader will
/Documentation/usb/
Dusb-serial.rst195 have been pretty thoroughly tested at various baud rates with 8-N-1
199 The USA-28 isn't yet supported though doing so should be pretty
271 As far as I can tell it supports pretty much every sirf command as
/Documentation/driver-api/md/
Draid5-cache.rst89 The log implementation is pretty straightforward. The difficult part is the
/Documentation/locking/
Dpi-futex.rst62 problems as other user-space locking constructs). Fact is, pretty much
Dspinlocks.rst32 The above is usually pretty simple (you usually need and want only one
/Documentation/userspace-api/netlink/
Dintro-specs.rst45 Python-pretty-printed. This is because some Netlink types can't
/Documentation/driver-api/pci/
Dp2pdma.rst7 The PCI bus has pretty decent support for performing DMA transfers
/Documentation/sound/designs/
Dtracepoints.rst141 ALSA PCM core also has a pretty print format for each of the tracepoints. Below
/Documentation/translations/zh_TW/process/
Dsubmitting-patches.rst126 [pretty]
131 $ git log -1 --pretty=fixes 54a4f0239f2e

1234