<?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 Kbuild</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>62ae4568 - drm: ensure drm headers are self-contained and pass kernel-doc</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#62ae4568</link>
        <description>drm: ensure drm headers are self-contained and pass kernel-docEnsure drm headers build, are self-contained, have header guards, andhave no kernel-doc warnings, when CONFIG_DRM_HEADER_TEST=y.The mechanism follows similar patters used in i915, xe, and usr/include.To cover include/drm, we need to recurse there using the top levelKbuild and the new include/Kbuild files.v4: check for CONFIG_WERROR in addition to CONFIG_DRM_WERRORv3: adapt to upstream build changesv2: make DRM_HEADER_TEST depend on DRMSuggested-by: Daniel Vetter &lt;daniel@ffwll.ch&gt;Cc: David Airlie &lt;airlied@gmail.com&gt;Cc: Daniel Vetter &lt;daniel@ffwll.ch&gt;Cc: Maarten Lankhorst &lt;maarten.lankhorst@linux.intel.com&gt;Cc: Maxime Ripard &lt;mripard@kernel.org&gt;Cc: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;Cc: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Acked-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;Acked-by: Simona Vetter &lt;simona.vetter@ffwll.ch&gt;Link: https://patchwork.freedesktop.org/patch/msgid/d8ad1c6d707f38a55987f616cb9650aef30b84e1.1737556766.git.jani.nikula@intel.comSigned-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Wed, 22 Jan 2025 14:41:34 +0000</pubDate>
        <dc:creator>Jani Nikula &lt;jani.nikula@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>5750121a - kbuild: list sub-directories in ./Kbuild</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#5750121a</link>
        <description>kbuild: list sub-directories in ./KbuildUse the ordinary obj-y syntax to list subdirectories.Note1:Previously, the link order of lib-y depended on CONFIG_MODULES; lib-ywas linked before drivers-y when CONFIG_MODULES=y, otherwise afterdrivers-y. This was a bug of commit 7273ad2b08f8 (&quot;kbuild: link lib-yobjects to vmlinux forcibly when CONFIG_MODULES=y&quot;), but it was not abig deal after all. Now, all objects listed in lib-y are linked last,irrespective of CONFIG_MODULES.Note2:Finally, the single target build in arch/*/lib/ works correctly. There wasa bug report about this. [1]  $ make ARCH=arm arch/arm/lib/findbit.o    CALL    scripts/checksyscalls.sh    AS      arch/arm/lib/findbit.o[1]: https://lore.kernel.org/linux-kbuild/YvUQOwL6lD4%2F5%2FU6@shell.armlinux.org.uk/Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Tested-by: Nick Desaulniers &lt;ndesaulniers@google.com&gt;Reviewed-by: Nicolas Schier &lt;nicolas@fjasle.eu&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Sat, 24 Sep 2022 18:19:10 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>b10fdeea - kbuild: check sha1sum just once for each atomic header</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#b10fdeea</link>
        <description>kbuild: check sha1sum just once for each atomic headerIt is unneeded to check the sha1sum every time.Create the timestamp files to manage it.Add &apos;.&apos; to clean-dirs because &apos;make clean&apos; must visit ./Kbuild toclean up the timestamp files.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Sat, 20 Aug 2022 09:15:29 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>ed7ceac1 - kbuild: add phony targets to ./Kbuild</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#ed7ceac1</link>
        <description>kbuild: add phony targets to ./Kbuildmissing-syscalls and old-atomics are meant to be phony targets.Adding them to always-y is odd. (always-y should generate something).Add a new phony target &apos;prepare&apos;, which depends on all the other.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Sat, 20 Aug 2022 09:15:28 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>5f2fb52f - kbuild: rename hostprogs-y/always to hostprogs/always-y</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#5f2fb52f</link>
        <description>kbuild: rename hostprogs-y/always to hostprogs/always-yIn old days, the &quot;host-progs&quot; syntax was used for specifying hostprograms. It was renamed to the current &quot;hostprogs-y&quot; in 2004.It is typically useful in scripts/Makefile because it allows Kbuild toselectively compile host programs based on the kernel configuration.This commit renames like follows:  always       -&gt;  always-y  hostprogs-y  -&gt;  hostprogsSo, scripts/Makefile will look like this:  always-$(CONFIG_BUILD_BIN2C) += ...  always-$(CONFIG_KALLSYMS)    += ...      ...  hostprogs := $(always-y) $(always-m)I think this makes more sense because a host program is always a hostprogram, irrespective of the kernel configuration. We want to specifywhich ones to compile by CONFIG options, so always-y will be handier.The &quot;always&quot;, &quot;hostprogs-y&quot;, &quot;hostprogs-m&quot; will be kept for backwardcompatibility for a while.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Sat, 01 Feb 2020 16:49:24 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>125d059b - kbuild: do not descend to ./Kbuild when cleaning</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#125d059b</link>
        <description>kbuild: do not descend to ./Kbuild when cleaning&apos;make clean&apos; descends into ./Kbuild, but does not clean anythingsince everything is added to no-clean-files.There is no need to descend to ./Kbuild in the first place.We can drop the no-clean-files assignment.With this, there is no more user of no-clean-files. I will keep itfor a while to see whether a new user will appear.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Sat, 10 Aug 2019 15:53:02 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>d082402e - kbuild: remove meaningless &apos;targets&apos; in ./Kbuild</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#d082402e</link>
        <description>kbuild: remove meaningless &apos;targets&apos; in ./Kbuildtimeconst.h is generated by $(call filechk,...), missing-syscalls andold-atomics are invoked by $(call cmd,...)None of them needs to be added to &apos;targets&apos;.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Sat, 10 Aug 2019 15:53:01 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>01d509a4 - kbuild: remove unimportant comments from ./Kbuild</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#01d509a4</link>
        <description>kbuild: remove unimportant comments from ./KbuildEvery time we add/remove a target, we need to touch the header part,including renumbering. This is not so important information.Numbering targets is rather misleading because they are not necessarilygenerated in this order. For example, 1) and 2) can be executedsimultaneously when the -j option is given.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Reviewed-by: Kieran Bingham &lt;kieran.bingham@ideasonboard.com&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Tue, 19 Feb 2019 09:33:03 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>67274c08 - scripts/gdb: delay generation of gdb constants.py</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#67274c08</link>
        <description>scripts/gdb: delay generation of gdb constants.pyscripts/gdb/linux/constants.py is never used in the kernel buildprocess. There is no good reason to create it so early.Get it out of the &apos;prepare&apos; stage.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Reviewed-by: Kieran Bingham &lt;kieran.bingham@ideasonboard.com&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Tue, 19 Feb 2019 09:33:02 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>ba97df45 - kbuild: use assignment instead of define ... endef for filechk_* rules</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#ba97df45</link>
        <description>kbuild: use assignment instead of define ... endef for filechk_* rulesYou do not have to use define ... endef for filechk_* rules.For simple cases, the use of assignment looks cleaner, IMHO.I updated the usage for scripts/Kbuild.include in case somebodymisunderstands the &apos;define ... endif&apos; is the requirement.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Acked-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Thu, 03 Jan 2019 01:16:54 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>ad774086 - kbuild: change filechk to surround the given command with { }</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#ad774086</link>
        <description>kbuild: change filechk to surround the given command with { }filechk_* rules often consist of multiple &apos;echo&apos; lines. They must besurrounded with { } or ( ) to work correctly. Otherwise, only thestring from the last &apos;echo&apos; would be written into the target.Let&apos;s take care of that in the &apos;filechk&apos; in scripts/Kbuild.includeto clean up filechk_* rules.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Mon, 31 Dec 2018 08:24:09 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>dec28d8e - kbuild: remove unused cmd_gentimeconst</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#dec28d8e</link>
        <description>kbuild: remove unused cmd_gentimeconstfilechk_gentimeconst is always used instead of cmd_gentimeconst.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Mon, 24 Dec 2018 14:11:09 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>11fda148 - kbuild: remove $(obj)/ prefixes in ./Kbuild</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#11fda148</link>
        <description>kbuild: remove $(obj)/ prefixes in ./KbuildAdding $(obj)/ to file paths relative from the top objtree looksa bit redundant to me. This commit has no functional change since$(obj) is &apos;.&apos; in this file.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Sat, 22 Dec 2018 09:50:35 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>4d4b5c2e - treewide: remove explicit rules for *offsets.s</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#4d4b5c2e</link>
        <description>treewide: remove explicit rules for *offsets.sThese explicit rules are unneeded because scripts/Makefile.buildprovides a pattern rule to create %.s from %.cSigned-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Sat, 22 Dec 2018 09:50:33 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>bdf37b4d - locking/atomics: Fix out-of-tree build</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#bdf37b4d</link>
        <description>locking/atomics: Fix out-of-tree buildBuilding a kernel out of tree with:  make O=/tmp/b oldconfig  cd /tmp/b  makegives this error:    CALL    /mnt/kernel/kernel/linux/scripts/atomic/check-atomics.sh  /bin/bash: scripts/atomic/check-atomics.sh: No such file or directory  make[3]: *** [/mnt/kernel/kernel/linux/./Kbuild:86: old-atomics] Error 127  make[3]: *** Waiting for unfinished jobs....Make the command use the proper build prerequisite which is the absolutepath to the script.Reported-by: Stephen Rothwell &lt;sfr@canb.auug.org.au&gt;Signed-off-by: Borislav Petkov &lt;bp@suse.de&gt;Cc: Boqun Feng &lt;boqun.feng@gmail.com&gt;Cc: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;Cc: Mark Rutland &lt;mark.rutland@arm.com&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;Cc: Will Deacon &lt;will.deacon@arm.com&gt;Cc: arnd@arndb.deCc: aryabinin@virtuozzo.comCc: catalin.marinas@arm.comCc: dvyukov@google.comCc: glider@google.comCc: linux-arm-kernel@lists.infradead.orgCc: linuxdrivers@attotech.comFixes: 8d32588077bd (&quot;locking/atomics: Check generated headers are up-to-date&quot;)Link: http://lkml.kernel.org/r/20181108194128.13368-1-bp@alien8.deSigned-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Thu, 08 Nov 2018 19:41:28 +0000</pubDate>
        <dc:creator>Borislav Petkov &lt;bp@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>8d325880 - locking/atomics: Check generated headers are up-to-date</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#8d325880</link>
        <description>locking/atomics: Check generated headers are up-to-dateNow that all the generated atomic headers are in place, it would be goodto ensure that:a) the headers are up-to-date when scripting changes.b) developers don&apos;t directly modify the generated headers.To ensure both of these properties, let&apos;s add a Kbuild step to checkthat the generated headers are up-to-date.Signed-off-by: Mark Rutland &lt;mark.rutland@arm.com&gt;Signed-off-by: Peter Zijlstra (Intel) &lt;peterz@infradead.org&gt;Cc: linux-arm-kernel@lists.infradead.orgCc: catalin.marinas@arm.comCc: Will Deacon &lt;will.deacon@arm.com&gt;Cc: linuxdrivers@attotech.comCc: dvyukov@google.comCc: Boqun Feng &lt;boqun.feng@gmail.com&gt;Cc: arnd@arndb.deCc: aryabinin@virtuozzo.comCc: glider@google.comLink: http://lkml.kernel.org/r/20180904104830.2975-6-mark.rutland@arm.comSigned-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Tue, 04 Sep 2018 10:48:29 +0000</pubDate>
        <dc:creator>Mark Rutland &lt;mark.rutland@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>4173cbac - kbuild: remove redundant mkdir from ./Kbuild</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#4173cbac</link>
        <description>kbuild: remove redundant mkdir from ./KbuildThese two targets are added to &quot;targets&quot;.  Their directories areautomatically created.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Mon, 13 Nov 2017 10:29:39 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#b2441318</link>
        <description>License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the &apos;GPL-2.0&apos;SPDX license identifier.  The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode &amp; Windriver) producing SPDXtag:value files created by Philippe Ombredanne.  Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed.  Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;t find any license traces, file was   considered to have no license information in it, and the top level   COPYING file license applied.   For non */uapi/* files that summary was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0                                              11139   and resulted in the first patch in this series.   If that file was a */uapi/* path one, it was &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  Results of that was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0 WITH Linux-syscall-note                        930   and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one   of the */uapi/* ones, it was denoted with the Linux-syscall-note if   any GPL family license was found in the file or had no licensing in   it (per prior point).  Results summary:   SPDX license identifier                            # files   ---------------------------------------------------|------   GPL-2.0 WITH Linux-syscall-note                       270   GPL-2.0+ WITH Linux-syscall-note                      169   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17   LGPL-2.1+ WITH Linux-syscall-note                      15   GPL-1.0+ WITH Linux-syscall-note                       14   ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5   LGPL-2.0+ WITH Linux-syscall-note                       4   LGPL-2.1 WITH Linux-syscall-note                        3   ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3   ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1   and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became   the concluded license(s). - when there was disagreement between the two scanners (one detected a   license but the other didn&apos;t, or they both detected different   licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file   resulted in a clear resolution of the license that should apply (and   which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was   confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier,   the file was flagged for further research and to be revisited later   in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights.  TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected   license ids and scores - reviewing anything where there was a license detected (about 500+   files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license   was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied   SPDX license was correctThis produced a worksheet with 20 files needing minor correction.  Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg.  Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected.  This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.)  Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>ebf003f0 - kbuild: Consolidate header generation from ASM offset information</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#ebf003f0</link>
        <description>kbuild: Consolidate header generation from ASM offset informationLargely redundant code is used in different places to generate C headersfrom offset information extracted from assembly language output.Consolidate the code in Makefile.lib and use this instead.Signed-off-by: Matthias Kaehlcke &lt;mka@chromium.org&gt;Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Wed, 12 Apr 2017 19:43:52 +0000</pubDate>
        <dc:creator>Matthias Kaehlcke &lt;mka@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>f197d75f - scripts/gdb: provide linux constants</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Kbuild#f197d75f</link>
        <description>scripts/gdb: provide linux constantsSome macro&apos;s and defines are needed when parsing memory, and withoutcompiling the kernel as -g3 they are not available in the debug-symbols.We use the pre-processor here to extract constants to a dedicated modulefor the linux debugger extensionsTop level Kbuild is used to call in and generate the constants file,while maintaining dependencies on autogenerated files ininclude/generatedLink: http://lkml.kernel.org/r/bc3df9c25f57ea72177c066a51a446fc19e2c27f.1462865983.git.jan.kiszka@siemens.comSigned-off-by: Kieran Bingham &lt;kieran.bingham@linaro.org&gt;Signed-off-by: Jan Kiszka &lt;jan.kiszka@siemens.com&gt;Cc: Michal Marek &lt;mmarek@suse.cz&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/Kbuild</description>
        <pubDate>Mon, 23 May 2016 23:24:40 +0000</pubDate>
        <dc:creator>Kieran Bingham &lt;kieran.bingham@linaro.org&gt;</dc:creator>
    </item>
</channel>
</rss>
