Searched refs:pretty (Results 1 – 25 of 111) sorted by relevance
12345
| /kernel/linux/linux-5.10/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()
157 if (self->pretty) in jsonw_name()
|
| /kernel/linux/linux-5.10/tools/testing/selftests/wireguard/ |
| D | netns.sh | 32 pretty() { echo -e "\x1b[32m\x1b[1m[+] ${1:+NS$1: }${2}\x1b[0m" >&3; } function
33 pp() { pretty "" "$*"; "$@"; }
35 n0() { pretty 0 "$*"; maybe_exec ip netns exec $netns0 "$@"; }
36 n1() { pretty 1 "$*"; maybe_exec ip netns exec $netns1 "$@"; }
37 n2() { pretty 2 "$*"; maybe_exec ip netns exec $netns2 "$@"; }
38 ip0() { pretty 0 "ip $*"; ip -n $netns0 "$@"; }
39 ip1() { pretty 1 "ip $*"; ip -n $netns1 "$@"; }
40 ip2() { pretty 2 "ip $*"; ip -n $netns2 "$@"; }
42 waitiperf() { pretty "${1//*-}" "wait for iperf:${3:-5201} pid $2"; while [[ $(ss -N "$1" -tlpH "sp…
662 pretty "" "Objects that were created were also destroyed."
|
| /kernel/linux/linux-5.10/tools/bpf/bpftool/Documentation/ |
| D | bpftool-link.rst | 15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] | { **-f** | **--bpffs** } }
85 **# bpftool --json --pretty link show**
|
| D | common_options.rst | 16 -p, --pretty
|
| D | bpftool.rst | 22 | { **-j** | **--json** } [{ **-p** | **--pretty** }] }
|
| D | bpftool-perf.rst | 15 *OPTIONS* := { [{ **-j** | **--json** }] [{ **-p** | **--pretty** }] }
|
| D | bpftool-struct_ops.rst | 15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] }
|
| D | bpftool-feature.rst | 15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] }
|
| D | bpftool-net.rst | 15 *OPTIONS* := { [{ **-j** | **--json** }] [{ **-p** | **--pretty** }] }
|
| D | bpftool-cgroup.rst | 15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] | { **-f** | **--bpffs** } }
|
| /kernel/linux/linux-5.10/tools/perf/util/ |
| D | PERF-VERSION-GEN | 22 CID=$(git log -1 --abbrev=12 --pretty=format:"%h" 2>/dev/null) && CID="-g$CID"
|
| /kernel/linux/linux-5.10/kernel/configs/ |
| D | xen.config | 16 # pretty useless systems starting from allnoconfig
|
| /kernel/linux/linux-5.10/Documentation/i2c/busses/ |
| D | i2c-taos-evm.rst | 44 The communication protocol is text-based and pretty simple. It is
|
| /kernel/linux/linux-5.10/Documentation/i2c/ |
| D | ten-bit-addresses.rst | 31 Note that 10-bit address devices are still pretty rare, so the limitations
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | gfs2.rst | 42 is pretty close.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/ |
| D | st-sensors.txt | 3 The STMicroelectronics sensor devices are pretty straight-forward I2C or
|
| /kernel/linux/linux-5.10/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
758 5.1 bpftool map pretty print
784 bpftool is able to pretty print like below:
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | fib_trie.rst | 87 level compression. This part follows the original paper pretty closely
98 The route manipulation functions. Should conform pretty closely to the
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/Documentation/driver-api/media/drivers/ |
| D | cx88-devel.rst | 94 I'm pretty sure when no IR signal is present the receiver is always in a
|
| /kernel/linux/linux-5.10/Documentation/x86/x86_64/ |
| D | fake-numa-for-cpusets.rst | 76 cpusets. Since cpusets can form a hierarchy, you can create some pretty
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | intel-iommu.rst | 48 IOVA generation is pretty generic. We used the same technique as vmalloc()
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | s2ram.rst | 23 way to debug these things, and it's actually pretty powerful (but
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/kunit/ |
| D | usage.rst | 105 A single test case should be pretty short, pretty easy to understand,
239 however, it is an easily derived concept. Accordingly, pretty much every project
597 actual procedure for writing and running the tests is pretty much the same as
|
12345