<?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>91188544 - isdn: kcapi: don&apos;t build unused procfs code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/isdn/capi/Makefile#91188544</link>
        <description>isdn: kcapi: don&apos;t build unused procfs codeThe procfs file is completely unused without CONFIG_PROC_FS but causesa compile time warning:drivers/isdn/capi/kcapi_proc.c:97:36: error: unused variable &apos;seq_controller_ops&apos; [-Werror,-Wunused-const-variable]static const struct seq_operations seq_controller_ops = {drivers/isdn/capi/kcapi_proc.c:104:36: error: unused variable &apos;seq_contrstats_ops&apos; [-Werror,-Wunused-const-variable]drivers/isdn/capi/kcapi_proc.c:179:36: error: unused variable &apos;seq_applications_ops&apos; [-Werror,-Wunused-const-variable]drivers/isdn/capi/kcapi_proc.c:186:36: error: unused variable &apos;seq_applstats_ops&apos; [-Werror,-Wunused-const-variable]Remove the file from the build in that config and make the calls intoit conditional instead.Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Link: https://lore.kernel.org/r/20240403080702.3509288-27-arnd@kernel.orgSigned-off-by: Jakub Kicinski &lt;kuba@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/isdn/capi/Makefile</description>
        <pubDate>Wed, 03 Apr 2024 08:06:44 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>f59aba2f - isdn: capi: dead code removal</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/isdn/capi/Makefile#f59aba2f</link>
        <description>isdn: capi: dead code removalThe staging isdn drivers are gone, and CONFIG_BT_CMTP is nowthe only user. This means a lot of the code in the subsystemhas no remaining callers and can be removed.Change the capi user space front-end to be part of kernelcapi,and the combined module to only be compiled if BT_CMTP isalso enabled, then remove the interfaces that have no remainingcallers.As the notifier list and the capi_drivers list have no callersoutside of kcapi.c, the implementation gets much simpler.Some definitions from the include/linux/*.h headers are onlyneeded internally and are moved to kcapi.h.Acked-by: David Miller &lt;davem@davemloft.net&gt;Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Link: https://lore.kernel.org/r/20191210210455.3475361-2-arnd@arndb.deSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/isdn/capi/Makefile</description>
        <pubDate>Tue, 10 Dec 2019 20:59:16 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>6d979850 - isdn: move capi drivers to staging</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/isdn/capi/Makefile#6d979850</link>
        <description>isdn: move capi drivers to stagingI tried to find any indication of whether the capi drivers are still inuse, and have not found anything from a long time ago.With public ISDN networks almost completely shut down over the past 12months, there is very little you can actually do with this hardware. Themain remaining use case would be to connect ISDN voice phones to anin-house installation with Asterisk or LCR, but anyone trying this inturn seems to be using either the mISDN driver stack, or out-of-treedrivers from the hardware vendors.I may of course have missed something, so I would suggest moving thesethree drivers (avm, hysdn, gigaset) into drivers/staging/ just in casesomeone still uses them.If nobody complains, we can remove them entirely in six months, orotherwise move the core code and any drivers that are still needed backinto drivers/isdn.As Paul Bolle notes, he is still testing the gigaset driver as long ashe can, but the Dutch ISDN network will be shut down in September 2019,which puts an end to that.Marcel Holtmann still maintains the Bluetooth CMTP profile and wants tokeep that alive, so the actual CAPI subsystem code remains in place fornow, after all other drivers are gone, CMTP and CAPI can be merged intoa single driver directory.Cc: Marcel Holtmann &lt;marcel@holtmann.org&gt;Cc: Paul Bolle &lt;pebolle@tiscali.nl&gt;Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;

            List of files:
            /linux-6.15/drivers/isdn/capi/Makefile</description>
        <pubDate>Sat, 20 Apr 2019 20:28:45 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&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/drivers/isdn/capi/Makefile#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/drivers/isdn/capi/Makefile</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>1f90d665 - capi: Perform scheduled capifs removal</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/isdn/capi/Makefile#1f90d665</link>
        <description>capi: Perform scheduled capifs removaludev fully replaces this special file system that only contains CAPINCCI TTY device nodes. User space (pppdcapiplugin) works withoutnoticing the difference.Signed-off-by: Jan Kiszka &lt;jan.kiszka@web.de&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/isdn/capi/Makefile</description>
        <pubDate>Wed, 06 Apr 2011 10:58:37 +0000</pubDate>
        <dc:creator>Jan Kiszka &lt;jan.kiszka@web.de&gt;</dc:creator>
    </item>
<item>
        <title>1da177e4 - Linux-2.6.12-rc2</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/isdn/capi/Makefile#1da177e4</link>
        <description>Linux-2.6.12-rc2Initial git repository build. I&apos;m not bothering with the full history,even though we have it. We can create a separate &quot;historical&quot; gitarchive of that later if we want to, and in the meantime it&apos;s about3.2GB when imported into git - space that would just make the earlygit days unnecessarily complicated, when we don&apos;t have a lot of goodinfrastructure for it.Let it rip!

            List of files:
            /linux-6.15/drivers/isdn/capi/Makefile</description>
        <pubDate>Sat, 16 Apr 2005 22:20:36 +0000</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@ppc970.osdl.org&gt;</dc:creator>
    </item>
</channel>
</rss>
