Home
last modified time | relevance | path

Searched refs:analyse (Results 1 – 12 of 12) sorted by relevance

/OK3568_Linux_fs/yocto/poky/scripts/contrib/
H A Dpatchreview.py98 def analyse(results, want_blame=False, verbose=True): function
213 analyse(results, want_blame=args.blame, verbose=args.verbose)
/OK3568_Linux_fs/buildroot/package/libcap-ng/
H A DConfig.in6 library. It includes utilities that can analyse all currently
/OK3568_Linux_fs/buildroot/package/trace-cmd/
H A DConfig.in11 target. You can analyse these traces on the target or on
/OK3568_Linux_fs/yocto/poky/meta/recipes-kernel/blktrace/
H A Dblktrace_git.bb5 trace information for the kernel to user space, and utilities to analyse and \
/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/
H A Ddev-touch.rst18 Processing is required to analyse the raw data and produce input events. In
/OK3568_Linux_fs/kernel/Documentation/kbuild/
H A Dgcc-plugins.rst11 We can analyse, change and add further code during compilation via
/OK3568_Linux_fs/kernel/tools/perf/Documentation/
H A Dtips.txt8 Create an archive with symtabs to analyse on other machine: perf archive
/OK3568_Linux_fs/buildroot/dl/sox/git/test/
H A DREADME72 The output file is examined by the 'model' or 'lmodel' program to analyse
/OK3568_Linux_fs/kernel/tools/power/cpupower/po/
H A Dfr.po532 msgstr "analyse du CPU %d impossible puisqu'il ne semble pas être présent\n"
537 msgstr "analyse du CPU %d :\n"
788 msgstr "analyse du CPU %d :\n"
/OK3568_Linux_fs/kernel/Documentation/filesystems/
H A Dxfs-self-describing-metadata.rst24 scripting to analyse the structure of a 100TB filesystem when trying to
32 to analyse and so that analysis blows out towards weeks/months of forensic work.
/OK3568_Linux_fs/kernel/kernel/trace/
H A DKconfig451 Only enable it if you want to analyse the branching behavior.
/OK3568_Linux_fs/kernel/Documentation/networking/
H A Dfilter.rst1399 each new branch to analyse, the verifier looks at all the states it's previously