<?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>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/nfc/st-nci/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/nfc/st-nci/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>2b6e5bfe - NFC: st-nci: Replace st21nfcb by st_nci in makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nfc/st-nci/Makefile#2b6e5bfe</link>
        <description>NFC: st-nci: Replace st21nfcb by st_nci in makefileReplace 1 missing st21nfcb by st_nciSigned-off-by: Christophe Ricard &lt;christophe-h.ricard@st.com&gt;Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/nfc/st-nci/Makefile</description>
        <pubDate>Sun, 25 Oct 2015 21:54:50 +0000</pubDate>
        <dc:creator>Christophe Ricard &lt;christophe.ricard@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>b1fa4dc4 - NFC: st-nci: Add support for proprietary commands</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nfc/st-nci/Makefile#b1fa4dc4</link>
        <description>NFC: st-nci: Add support for proprietary commandsAdd support for proprietary commands useful mainly forfactory testings. Here is a list:- FACTORY_MODE: Allow to set the driver into a mode where  no secure element are activated. It does not consider any  NFC_ATTR_VENDOR_DATA.- HCI_CLEAR_ALL_PIPES: Allow to execute a HCI clear all pipes  command. It does not consider any NFC_ATTR_VENDOR_DATA.- HCI_DM_PUT_DATA: Allow to configure specific CLF registry  like for example RF trimmings or low level drivers  configurations (I2C, SPI, SWP).- HCI_DM_UPDATE_AID: Allow to configure an AID routing into the  CLF routing table following RF technology, CLF mode or protocol.- HCI_DM_GET_INFO: Allow to retrieve CLF information.- HCI_DM_GET_DATA: Allow to retrieve CLF configurable data such as  low level drivers configurations or RF trimmings.- HCI_DM_DIRECT_LOAD: Allow to load a firmware into the CLF.  A complete packet can be more than 8KB.- HCI_DM_RESET: Allow to run a CLF reset in order to &quot;commit&quot; CLF  configuration changes without CLF power off.- HCI_GET_PARAM: Allow to retrieve an HCI CLF parameter (for example  the white list).- HCI_DM_FIELD_GENERATOR: Allow to generate different kind of RF  technology. When using this command to anti-collision is done.- HCI_LOOPBACK: Allow to echo a command and test the Dh to CLF  connectivity.- HCI_DM_VDC_MEASUREMENT_VALUE: Allow to measure the field applied  on the CLF antenna. A value between 0 and 0x0f is returned. 0 is  maximum.- HCI_DM_FWUPD_START: Allow to put CLF into firmware update mode.  It is a specific CLF command as there is no GPIO for this.- HCI_DM_FWUPD_END:  Allow to complete firmware update.- HCI_DM_VDC_VALUE_COMPARISON: Allow to compare the field applied  on the CLF antenna to a reference value.- MANUFACTURER_SPECIFIC: Allow to retrieve manufacturer specific data  received during a NCI_CORE_INIT_CMD.Signed-off-by: Christophe Ricard &lt;christophe-h.ricard@st.com&gt;Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/nfc/st-nci/Makefile</description>
        <pubDate>Sun, 25 Oct 2015 21:54:36 +0000</pubDate>
        <dc:creator>Christophe Ricard &lt;christophe.ricard@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>dc42143b - NFC: st-nci: Rename st-nci_se.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nfc/st-nci/Makefile#dc42143b</link>
        <description>NFC: st-nci: Rename st-nci_se.cRename it to se.c to keep the driver files namespace consistent.Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/nfc/st-nci/Makefile</description>
        <pubDate>Fri, 23 Oct 2015 15:05:37 +0000</pubDate>
        <dc:creator>Samuel Ortiz &lt;sameo@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>2bc4d4f8 - nfc: st-nci: Add spi phy support for st21nfcb</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nfc/st-nci/Makefile#2bc4d4f8</link>
        <description>nfc: st-nci: Add spi phy support for st21nfcbst21nfcb does support another phy than i2c: spi.st21nfcc does not support spi as the spi ios are usedby the AMS RF booster.st21nfcb is not following NCI NFC Forum recommendations for spibut rely on ST prioritary protocol ndlc as for i2c.Signed-off-by: Christophe Ricard &lt;christophe-h.ricard@st.com&gt;Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/nfc/st-nci/Makefile</description>
        <pubDate>Fri, 14 Aug 2015 20:33:37 +0000</pubDate>
        <dc:creator>Christophe Ricard &lt;christophe.ricard@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>ed06aeef - nfc: st-nci: Rename st21nfcb to st-nci</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nfc/st-nci/Makefile#ed06aeef</link>
        <description>nfc: st-nci: Rename st21nfcb to st-nciSTMicroelectronics NFC NCI chips family is extendingwith the new ST21NFCC using the AMS AS39230 RF booster.The st21nfcb driver is relevant for this solution andmight be with future products.Signed-off-by: Christophe Ricard &lt;christophe-h.ricard@st.com&gt;Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/nfc/st-nci/Makefile</description>
        <pubDate>Tue, 09 Jun 2015 20:26:05 +0000</pubDate>
        <dc:creator>Christophe Ricard &lt;christophe.ricard@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
