<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>86c2345a - tools/Makefile: Remove pci target</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#86c2345a</link>
        <description>tools/Makefile: Remove pci targete19bde2269ca (&quot;selftests: Move PCI Endpoint tests from tools/pci toKselftests&quot;) moves tools/pci/ to tools/testing/selftests/pci_endpoint,which causes build failure when running &quot;make pci&quot; under tools:  linux/tools$ make pci    DESCEND pci  make[1]: *** No targets specified and no makefile found.  Stop.  make: *** [Makefile:73: pci] Error 2Update the top level tools/Makefile to remove reference to building,installing and cleaning pci components.Link: https://lore.kernel.org/r/20250217115159.537920-1-liujianfeng1994@gmail.comFixes: e19bde2269ca (&quot;selftests: Move PCI Endpoint tests from tools/pci to Kselftests&quot;)Signed-off-by: Jianfeng Liu &lt;liujianfeng1994@gmail.com&gt;Signed-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Reviewed-by: Manivannan Sadhasivam &lt;manivannan.sadhasivam@linaro.org&gt;Signed-off-by: Krzysztof Wilczy&#324;ski &lt;kwilczynski@kernel.org&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Mon, 17 Feb 2025 11:51:52 +0000</pubDate>
        <dc:creator>Jianfeng Liu &lt;liujianfeng1994@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>2a52ca7c - sched_ext: Add scx_simple and scx_example_qmap example schedulers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#2a52ca7c</link>
        <description>sched_ext: Add scx_simple and scx_example_qmap example schedulersAdd two simple example BPF schedulers - simple and qmap.* simple: In terms of scheduling, it behaves identical to not having any  operation implemented at all. The two operations it implements are only to  improve visibility and exit handling. On certain homogeneous  configurations, this actually can perform pretty well.* qmap: A fixed five level priority scheduler to demonstrate queueing PIDs  on BPF maps for scheduling. While not very practical, this is useful as a  simple example and will be used to demonstrate different features.v7: - Compat helpers stripped out in prepartion of upstreaming as the      upstreamed patchset will be the baselinfe. Utility macros that can be      used to implement compat features are kept.    - Explicitly disable map autoattach on struct_ops to avoid trying to      attach twice while maintaining compatbility with older libbpf.v6: - Common header files reorganized and cleaned up. Compat helpers are      added to demonstrate how schedulers can maintain backward      compatibility with older kernels while making use of newly added      features.    - simple_select_cpu() added to keep track of the number of local      dispatches. This is needed because the default ops.select_cpu()      implementation is updated to dispatch directly and won&apos;t call      ops.enqueue().    - Updated to reflect the sched_ext API changes. Switching all tasks is      the default behavior now and scx_qmap supports partial switching when      `-p` is specified.    - tools/sched_ext/Kconfig dropped. This will be included in the doc      instead.v5: - Improve Makefile. Build artifects are now collected into a separate      dir which change be changed. Install and help targets are added and      clean actually cleans everything.    - MEMBER_VPTR() improved to improve access to structs. ARRAY_ELEM_PTR()      and RESIZEABLE_ARRAY() are added to support resizable arrays in .bss.    - Add scx_common.h which provides common utilities to user code such as      SCX_BUG[_ON]() and RESIZE_ARRAY().    - Use SCX_BUG[_ON]() to simplify error handling.v4: - Dropped _example prefix from scheduler names.v3: - Rename scx_example_dummy to scx_example_simple and restructure a bit      to ease later additions. Comment updates.    - Added declarations for BPF inline iterators. In the future, hopefully,      these will be consolidated into a generic BPF header so that they      don&apos;t need to be replicated here.v2: - Updated with the generic BPF cpumask helpers.Signed-off-by: Tejun Heo &lt;tj@kernel.org&gt;Reviewed-by: David Vernet &lt;dvernet@meta.com&gt;Acked-by: Josh Don &lt;joshdon@google.com&gt;Acked-by: Hao Luo &lt;haoluo@google.com&gt;Acked-by: Barret Rhoden &lt;brho@google.com&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Tue, 18 Jun 2024 20:09:17 +0000</pubDate>
        <dc:creator>Tejun Heo &lt;tj@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>950bf45d - tools/Makefile: remove cgroup target</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#950bf45d</link>
        <description>tools/Makefile: remove cgroup targetThe tools/cgroup directory no longer contains a Makefile.  This patchupdates the top-level tools/Makefile to remove references to building andinstalling cgroup components.  This change reflects the current structureof the tools directory and fixes the build failure when building tools inthe top-level directory.linux/tools$ make cgroup  DESCEND cgroupmake[1]: *** No targets specified and no makefile found.  Stop.make: *** [Makefile:73: cgroup] Error 2Link: https://lkml.kernel.org/r/20240315012249.439639-1-liucong2@kylinos.cnSigned-off-by: Cong Liu &lt;liucong2@kylinos.cn&gt;Acked-by: Stanislav Fomichev &lt;sdf@google.com&gt;Reviewed-by: Dmitry Rokosov &lt;ddrokosov@salutedevices.com&gt;Cc: Cong Liu &lt;liucong2@kylinos.cn&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Fri, 15 Mar 2024 01:22:48 +0000</pubDate>
        <dc:creator>Cong Liu &lt;liucong2@kylinos.cn&gt;</dc:creator>
    </item>
<item>
        <title>a1014824 - tools/Makefile: do missed s/vm/mm/</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#a1014824</link>
        <description>tools/Makefile: do missed s/vm/mm/Commit 799fb82aa132 (&quot;tools/vm: rename tools/vm to tools/mm&quot;) missedrenaming &apos;vm&apos; in &apos;tools/Makefile&apos; to &apos;mm&apos;.  As a result, &apos;make clean&apos;under &apos;tools/&apos; directory fails as below:    $ make -C tools clean      DESCEND vm    make[1]: Entering directory &apos;/linux/tools/vm&apos;    make[1]: *** No rule to make target &apos;clean&apos;.  Stop.    make[1]: Leaving directory &apos;/linux/tools/vm&apos;    make: *** [Makefile:173: vm_clean] Error 2    make: Leaving directory &apos;/linux/tools&apos;Do the missed rename.Link: https://lkml.kernel.org/r/20230415203110.13858-1-sj@kernel.orgFixes: 799fb82aa132 (&quot;tools/vm: rename tools/vm to tools/mm&quot;)Signed-off-by: SeongJae Park &lt;sj@kernel.org&gt;Reported-by: Ricardo Pardini &lt;ricardo@pardini.net&gt;  Link: https://lore.kernel.org/linux-mm/20230415202454.13558-1-sj@kernel.org/Tested-by: Ricardo Pardini &lt;ricardo@pardini.net&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Sat, 15 Apr 2023 20:31:10 +0000</pubDate>
        <dc:creator>SeongJae Park &lt;sj@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>fe20cad4 - tools/nolibc: make the default target build the headers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#fe20cad4</link>
        <description>tools/nolibc: make the default target build the headersThe help in &quot;make -C tools&quot; enumerates nolibc as a valid target so wemust at least make it do something. Let&apos;s make it do the equivalentof &quot;make headers&quot; in that it will prepare a sysroot with the arch&apos;sheaders, but will not install the kernel&apos;s headers. This is theminimum some tools will need when built with a full-blown toolchainanyway.Signed-off-by: Willy Tarreau &lt;w@1wt.eu&gt;Signed-off-by: Paul E. McKenney &lt;paulmck@kernel.org&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Sat, 28 May 2022 15:45:45 +0000</pubDate>
        <dc:creator>Willy Tarreau &lt;w@1wt.eu&gt;</dc:creator>
    </item>
<item>
        <title>077df623 - tools/thermal: Add thermal daemon skeleton</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#077df623</link>
        <description>tools/thermal: Add thermal daemon skeletonThis change provides a simple daemon skeleton. It is an example of howto use the thermal library which wraps all the complex code related tothe netlink and transforms it into a callback oriented code.The goal of this skeleton is to give a base brick for anyoneinterested in writing its own thermal engine or as an example to relyon to write its own thermal monitoring implementation.In the future, it will evolve with more features and hopefully morelogic.Signed-off-by: Daniel Lezcano &lt;daniel.lezcano@linaro.org&gt;Tested-by: Srinivas Pandruvada &lt;srinivas.pandruvada@linux.intel.com&gt;Link: https://lore.kernel.org/r/20220420160933.347088-5-daniel.lezcano@linaro.org

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Wed, 20 Apr 2022 16:09:32 +0000</pubDate>
        <dc:creator>Daniel Lezcano &lt;daniel.lezcano@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>110acbc6 - tools/thermal: Add a temperature capture tool</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#110acbc6</link>
        <description>tools/thermal: Add a temperature capture toolThe &apos;thermometer&apos; tool allows to capture the temperature of a set ofthermal zones defined in a configuration file at a specified rate.It is designed to have the lowest possible overhead. It will write thecaptured temperature per thermal zone per file so making easier towrite a gnuplot script.Signed-off-by: Daniel Lezcano &lt;daniel.lezcano@linaro.org&gt;Tested-by: Srinivas Pandruvada &lt;srinivas.pandruvada@linux.intel.com&gt;Link: https://lore.kernel.org/r/20220420160933.347088-4-daniel.lezcano@linaro.org

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Wed, 20 Apr 2022 16:09:31 +0000</pubDate>
        <dc:creator>Daniel Lezcano &lt;daniel.lezcano@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>47c4b0de - tools/lib/thermal: Add a thermal library</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#47c4b0de</link>
        <description>tools/lib/thermal: Add a thermal libraryThe thermal framework implements a netlink notification mechanism tobe used by the userspace to have a thermal configuration discovery,trip point changes or violation, cooling device changes notifications,etc...This library provides a level of abstraction for the thermal netlinknotification allowing the userspace to connect to the notificationmechanism more easily. The library is callback oriented.Signed-off-by: Daniel Lezcano &lt;daniel.lezcano@linaro.org&gt;Tested-by: Srinivas Pandruvada &lt;srinivas.pandruvada@linux.intel.com&gt;Link: https://lore.kernel.org/r/20220420160933.347088-2-daniel.lezcano@linaro.org

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Wed, 20 Apr 2022 16:09:29 +0000</pubDate>
        <dc:creator>Daniel Lezcano &lt;daniel.lezcano@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>0b37dff1 - tools/nolibc: add the nolibc subdir to the common Makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#0b37dff1</link>
        <description>tools/nolibc: add the nolibc subdir to the common MakefileThe Makefile in tools/ is used to forward options to the makefilesin the various subdirs. Let&apos;s add nolibc there so that it becomespossible to make tools/nolibc_headers_standalone from the main treeto simply create a completely usable sysroot.Signed-off-by: Willy Tarreau &lt;w@1wt.eu&gt;Signed-off-by: Paul E. McKenney &lt;paulmck@kernel.org&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Mon, 21 Mar 2022 17:33:14 +0000</pubDate>
        <dc:creator>Willy Tarreau &lt;w@1wt.eu&gt;</dc:creator>
    </item>
<item>
        <title>7246f4dc - tools/lib/lockdep: drop liblockdep</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#7246f4dc</link>
        <description>tools/lib/lockdep: drop liblockdepTL;DR: While a tool like liblockdep is useful, it probably doesn&apos;tbelong within the kernel tree.liblockdep attempts to reuse kernel code both directly (by directlybuilding the kernel&apos;s lockdep code) as well as indirectly (by usingsanitized headers). This makes liblockdep an integral part of thekernel.It also makes liblockdep quite unique: while other userspace code mightuse sanitized headers, it generally doesn&apos;t attempt to use kernel codedirectly which means that changes on the kernel side of things don&apos;taffect (and break) it directly.All our workflows and tooling around liblockdep don&apos;t support thisuniqueness. Changes that go into the kernel code aren&apos;t validated to notbreak in-tree userspace code.liblockdep ended up being very fragile, breaking over and over, to thepoint that living in the same tree as the lockdep code lost most of it&apos;svalue.liblockdep should continue living in an external tree, syncing withthe kernel often, in a controllable way.Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;Cc: Ingo Molnar &lt;mingo@kernel.org&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Fri, 12 Nov 2021 15:16:02 +0000</pubDate>
        <dc:creator>Sasha Levin &lt;sashal@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>08609989 - tools/counter: Create Counter tools</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#08609989</link>
        <description>tools/counter: Create Counter toolsThis creates an example Counter program under tools/counter/*to exemplify the Counter character device interface.Cc: Pavel Machek &lt;pavel@ucw.cz&gt;Signed-off-by: William Breathitt Gray &lt;vilhelm.gray@gmail.com&gt;Link: https://lore.kernel.org/r/7c0f975ba098952122302d258ec9ffdef04befaf.1632884256.git.vilhelm.gray@gmail.comSigned-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Wed, 29 Sep 2021 03:16:01 +0000</pubDate>
        <dc:creator>William Breathitt Gray &lt;vilhelm.gray@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>e23db805 - tracing/tools: Add the latency-collector to tools directory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#e23db805</link>
        <description>tracing/tools: Add the latency-collector to tools directoryThis is a tool that is intended to work around the fact that thepreemptoff, irqsoff, and preemptirqsoff tracers only work inoverwrite mode. The idea is to act randomly in such a way that wedo not systematically lose any latencies, so that if enough testingis done, all latencies will be captured. If the same burst oflatencies is repeated, then sooner or later we will have captured allthe latencies.It also works with the wakeup_dl, wakeup_rt, and wakeup tracers.However, in that case it is probably not useful to use the randomsleep functionality.The reason why it may be desirable to catch all latencies with a longtest campaign is that for some organizations, it&apos;s necessary to testthe kernel in the field and not practical for developers to workiteratively with field testers. Because of cost and project schedulesit is not possible to start a new test campaign every time a latencyproblem has been fixed.It uses inotify to detect changes to /sys/kernel/tracing/trace.When a latency is detected, it will either sleep or printimmediately, depending on a function that act as an unfair cointoss.If immediate print is chosen, it means that we open/sys/kernel/tracing/trace and thereby cause a blackout periodthat will hide any subsequent latencies.If sleep is chosen, it means that we wait before opening/sys/kernel/tracing/trace, by default for 1000 ms, to see ifthere is another latency during this period. If there is, then we willlose the previous latency. The coin will be tossed again with adifferent probability, and we will either print the new latency, orpossibly a subsequent one.The probability for the unfair coin toss is chosen so that thereis equal probability to obtain any of the latencies in a burst.However, this assumes that we make an assumption of how manylatencies there can be. By default  the program assumes that thereare no more than 2 latencies in a burst, the probability of immediateprintout will be:1/2 and 1Thus, the probability of getting each of the two latencies will be 1/2.If we ever find that there is more than one latency in a series,meaning that we reach the probability of 1, then the table will beexpanded to:1/3, 1/2, and 1Thus, we assume that there are no more than three latencies and eachwith a probability of 1/3 of being captured. If the probability of 1is reached in the new table, that is we see more than two closelyoccurring latencies, then the table will again be extended, and soon.On my systems, it seems like this scheme works fairly well, aslong as the latencies we trace are long enough, 300 us seems to beenough. This userspace program receive the inotify event at the endof a latency, and it has time until the end of the next latencyto react, that is to open /sys/kernel/tracing/trace. Thus,if we trace latencies that are &gt;300 us, then we have at least 300 usto react.The minimum latency will of course not be 300 us on all systems, itwill depend on the hardware, kernel version, workload andconfiguration.Example usage:In one shell, give the following command:sudo latency-collector -rvv -t preemptirqsoff -s 2000 -a 3This will trace latencies &gt; 2000us with the preemptirqsoff tracer,using random sleep with maximum verbosity, with a probabilitytable initialized to a size of 3.In another shell, generate a few bursts of latencies:root@host:~# modprobe preemptirq_delay_test delay=3000 test_mode=alternateburst_size=3root@host:~# echo 1 &gt; /sys/kernel/preemptirq_delay_test/triggerroot@host:~# echo 1 &gt; /sys/kernel/preemptirq_delay_test/triggerroot@host:~# echo 1 &gt; /sys/kernel/preemptirq_delay_test/triggerroot@host:~# echo 1 &gt; /sys/kernel/preemptirq_delay_test/triggerIf all goes well, you should be getting stack traces that showsall the different latencies, i.e. you should see all the threefunctions preemptirqtest_0, preemptirqtest_1, preemptirqtest_2 in thestack traces.Link: https://lkml.kernel.org/r/20210212134421.172750-2-Viktor.Rosendahl@bmw.deSigned-off-by: Viktor Rosendahl &lt;Viktor.Rosendahl@bmw.de&gt;Signed-off-by: Steven Rostedt (VMware) &lt;rostedt@goodmis.org&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Fri, 12 Feb 2021 13:44:21 +0000</pubDate>
        <dc:creator>Viktor Rosendahl &lt;Viktor.Rosendahl@bmw.de&gt;</dc:creator>
    </item>
<item>
        <title>33a57ce0 - bpf: Compile resolve_btfids tool at kernel compilation start</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#33a57ce0</link>
        <description>bpf: Compile resolve_btfids tool at kernel compilation startThe resolve_btfids tool will be used during the vmlinux linking,so it&apos;s necessary it&apos;s ready for it.Signed-off-by: Jiri Olsa &lt;jolsa@kernel.org&gt;Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;Tested-by: Andrii Nakryiko &lt;andriin@fb.com&gt;Acked-by: Andrii Nakryiko &lt;andriin@fb.com&gt;Link: https://lore.kernel.org/bpf/20200711215329.41165-3-jolsa@kernel.org

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Sat, 11 Jul 2020 21:53:22 +0000</pubDate>
        <dc:creator>Jiri Olsa &lt;jolsa@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>950313eb - tools: bootconfig: Add bootconfig command</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#950313eb</link>
        <description>tools: bootconfig: Add bootconfig commandAdd &quot;bootconfig&quot; command which operates the bootconfigconfig-data on initrd image.User can add/delete/verify the boot config on initrdimage using this command.e.g.Add a boot config to initrd image # bootconfig -a myboot.conf /boot/initrd.imgRemove it. # bootconfig -d /boot/initrd.imgOr verify (and show) it. # bootconfig /boot/initrd.imgLink: http://lkml.kernel.org/r/157867223582.17873.14342161849213219982.stgit@devnote2Signed-off-by: Masami Hiramatsu &lt;mhiramat@kernel.org&gt;[ Removed extra blank line at end of bootconfig.c ]Signed-off-by: Steven Rostedt (VMware) &lt;rostedt@goodmis.org&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Fri, 10 Jan 2020 16:03:56 +0000</pubDate>
        <dc:creator>Masami Hiramatsu &lt;mhiramat@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>38fe26b4 - tools: Keep list of tools in alphabetical order</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#38fe26b4</link>
        <description>tools: Keep list of tools in alphabetical orderWhen `make help` is executed it lists the possible tools to build,though couple of entries is kept unordered. Fix it here.Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;Acked-by: Song Liu &lt;songliubraving@fb.com&gt;Cc: Alexei Starovoitov &lt;ast@kernel.org&gt;Cc: Daniel Borkmann &lt;daniel@iogearbox.net&gt;Cc: Martin KaFai Lau &lt;kafai@fb.com&gt;Cc: Yonghong Song &lt;yhs@fb.com&gt;Link: https://lkml.kernel.org/n/tip-0ke3p64ksa0hnbueh52n3v3q@git.kernel.orgSigned-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Fri, 28 Jun 2019 17:22:09 +0000</pubDate>
        <dc:creator>Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>3fb4f7cd - tools/power/x86: A tool to validate Intel Speed Select commands</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#3fb4f7cd</link>
        <description>tools/power/x86: A tool to validate Intel Speed Select commandsThe Intel(R) Speed select technologies contains four features.Performance profile:An non architectural mechanism that allows multipleoptimized performance profiles per system via static and/or dynamicadjustment of core count, workload, Tjmax, and TDP, etc. aka ISSin the documentation.Base Frequency: Enables users to increase guaranteed base frequency oncertain cores (high priority cores) in exchange for lower base frequencyon remaining cores (low priority cores). aka PBF in the documenation.Turbo frequency: Enables the ability to set different turbo ratio limitsto cores based on priority. aka FACT in the documentation.Core power: An Interface that allows user to define per core/tilepriority.There is a multi level help for commands and options. This can be usedto check required arguments for each feature and commands for thefeature.To start navigating the features start with$sudo intel-speed-select --helpFor help on a specific feature for example$sudo intel-speed-select perf-profile --helpTo get help for a command for a feature for example$sudo intel-speed-select perf-profile get-lock-status --helpSigned-off-by: Srinivas Pandruvada &lt;srinivas.pandruvada@linux.intel.com&gt;Acked-by: Len Brown &lt;len.brown@intel.com&gt;Acked-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Sun, 30 Jun 2019 17:14:08 +0000</pubDate>
        <dc:creator>Srinivas Pandruvada &lt;srinivas.pandruvada@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>4ab5a5d2 - tools: add a kernel-chktaint to tools/debugging</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#4ab5a5d2</link>
        <description>tools: add a kernel-chktaint to tools/debuggingAdd a script to the tools/ directory that shows if or why the runningkernel was tainted. The script was mostly written by Randy Dunlap; Ienhanced the script a bit.  There does not appear to be a good home forthis script. so create tools/debugging for tools of this nature.Signed-off-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;Signed-off-by: Thorsten Leemhuis &lt;linux@leemhuis.info&gt;[ jc: fixed conflicts, rewrote changelog ]Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Tue, 08 Jan 2019 19:40:06 +0000</pubDate>
        <dc:creator>Thorsten Leemhuis &lt;linux@leemhuis.info&gt;</dc:creator>
    </item>
<item>
        <title>1e510603 - tools: Add &apos;firmware&apos; category and add ihex2fw tool</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#1e510603</link>
        <description>tools: Add &apos;firmware&apos; category and add ihex2fw toolCommit 5620a0d1aacd (&quot;firmware: delete in-kernel firmware&quot;) removedihex2fw tool together with the rest of the contents of firmware/folder. Since that tool is quite useful for doing .ihex -&gt; .fwconverstion, restore its original source code to tools/firmwareSuggested-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Cc: Kyle McMartin &lt;kyle@kernel.org&gt;Cc: Andrew Morton &lt;akpm@linux-foundation.org&gt;Cc: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Cc: David Woodhouse &lt;dwmw2@infradead.org&gt;Cc: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Cc: linux-kernel &lt;linux-kernel@vger.kernel.org&gt;Signed-off-by: Andrey Smirnov &lt;andrew.smirnov@gmail.com&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Wed, 17 Oct 2018 18:27:18 +0000</pubDate>
        <dc:creator>Andrey Smirnov &lt;andrew.smirnov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>1ce78ce0 - tools: PCI: Change pcitest compiling process</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#1ce78ce0</link>
        <description>tools: PCI: Change pcitest compiling processChange tool compiling process in order to be build using the samemechanism used in other linux tools (e.g. iio, perf, etc). This willallow in future the buildroot tool to build and integrate this tool ina more expeditious way.Update documentation accordingly.Signed-off-by: Gustavo Pimentel &lt;gustavo.pimentel@synopsys.com&gt;Signed-off-by: Lorenzo Pieralisi &lt;lorenzo.pieralisi@arm.com&gt;Reviewed-by: Kishon Vijay Abraham I &lt;kishon@ti.com&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Thu, 23 Aug 2018 11:55:15 +0000</pubDate>
        <dc:creator>Gustavo Pimentel &lt;gustavo.pimentel@synopsys.com&gt;</dc:creator>
    </item>
<item>
        <title>9d64fc08 - tools/wmi: add a sample for dell smbios communication over WMI</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/Makefile#9d64fc08</link>
        <description>tools/wmi: add a sample for dell smbios communication over WMIThis application uses the character device /dev/wmi/dell-smbiosto perform SMBIOS communications from userspace.It offers demonstrations of a few simple tasks: - Running a class/select command - Querying a token value - Activating a tokenSigned-off-by: Mario Limonciello &lt;mario.limonciello@dell.com&gt;Reviewed-by: Edward O&apos;Callaghan &lt;quasisec@google.com&gt;Signed-off-by: Darren Hart (VMware) &lt;dvhart@infradead.org&gt;

            List of files:
            /linux-6.15/tools/Makefile</description>
        <pubDate>Wed, 01 Nov 2017 19:25:37 +0000</pubDate>
        <dc:creator>Mario Limonciello &lt;mario.limonciello@dell.com&gt;</dc:creator>
    </item>
</channel>
</rss>
