Searched refs:pretty (Results 1 – 25 of 99) sorted by relevance
1234
| /Linux-v5.4/tools/bpf/bpftool/ |
| D | json_writer.c | 24 bool pretty; /* optional whitepace */ member
39 if (!self->pretty) in jsonw_eol()
99 self->pretty = false; in jsonw_new()
119 self->pretty = on; in jsonw_pretty()
151 if (self->pretty) in jsonw_name()
|
| /Linux-v5.4/tools/bpf/bpftool/Documentation/ |
| D | bpftool.rst | 22 | { **-j** | **--json** } [{ **-p** | **--pretty** }] }
59 -p, --pretty
|
| D | bpftool-perf.rst | 15 *OPTIONS* := { [{ **-j** | **--json** }] [{ **-p** | **--pretty** }] }
53 -p, --pretty
|
| D | bpftool-feature.rst | 15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] }
73 -p, --pretty
|
| D | bpftool-net.rst | 15 *OPTIONS* := { [{ **-j** | **--json** }] [{ **-p** | **--pretty** }] }
88 -p, --pretty
|
| D | bpftool-cgroup.rst | 15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] | { **-f** | **--bpffs** } }
125 -p, --pretty
|
| D | bpftool-btf.rst | 15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] }
79 -p, --pretty
|
| D | bpftool-prog.rst | 15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] | { **-f** | **--bpffs** } }
198 -p, --pretty
227 **# bpftool --json --pretty prog show**
|
| D | bpftool-map.rst | 15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] | { **-f** | **--bpffs** } }
154 -p, --pretty
|
| /Linux-v5.4/tools/perf/util/ |
| D | PERF-VERSION-GEN | 22 CID=$(git log -1 --abbrev=12 --pretty=format:"%h" 2>/dev/null) && CID="-g$CID"
|
| /Linux-v5.4/kernel/configs/ |
| D | xen.config | 16 # pretty useless systems starting from allnoconfig
|
| /Linux-v5.4/Documentation/i2c/busses/ |
| D | i2c-taos-evm.rst | 44 The communication protocol is text-based and pretty simple. It is
|
| /Linux-v5.4/Documentation/i2c/ |
| D | ten-bit-addresses.rst | 31 Note that 10-bit address devices are still pretty rare, so the limitations
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | gfs2.txt | 37 is pretty close.
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | nvmem.rst | 19 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
|
| /Linux-v5.4/Documentation/bpf/ |
| D | btf.rst | 13 The debug info is used for map pretty print, function signature, etc. The
145 pretty print. At most one encoding can be specified for the int type.
223 equal to ``30``. This is because the original use case is map pretty print
495 pretty print types, dump func signatures and line info, etc.
616 tool has full btf knowledge and is able to pretty print map key/values, dump
697 5.1 bpftool map pretty print
723 bpftool is able to pretty print like below:
|
| /Linux-v5.4/Documentation/devicetree/bindings/iio/ |
| D | st-sensors.txt | 3 The STMicroelectronics sensor devices are pretty straight-forward I2C or
|
| /Linux-v5.4/Documentation/arm/ |
| D | interrupts.rst | 9 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.
|
| /Linux-v5.4/Documentation/networking/ |
| D | fib_trie.txt | 83 level compression. This part follows the original paper pretty closely
94 The route manipulation functions. Should conform pretty closely to the
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | init.rst | 4 OK, so you've got this pretty unintuitive message (currently located
|
| /Linux-v5.4/Documentation/x86/x86_64/ |
| D | fake-numa-for-cpusets.rst | 76 cpusets. Since cpusets can form a hierarchy, you can create some pretty
|
| /Linux-v5.4/Documentation/x86/ |
| D | intel-iommu.rst | 48 IOVA generation is pretty generic. We used the same technique as vmalloc()
|
| /Linux-v5.4/Documentation/power/ |
| D | s2ram.rst | 23 way to debug these things, and it's actually pretty powerful (but
|
| /Linux-v5.4/Documentation/misc-devices/ |
| D | lis3lv02d.rst | 97 A: The sensor is pretty sensitive, so your hands can do it. Lift it
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | cx88.rst | 146 I'm pretty sure when no IR signal is present the receiver is always in a
|
1234
