<?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>d99ff463 - iio: move inv_icm42600 timestamp module in common</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iio/common/Makefile#d99ff463</link>
        <description>iio: move inv_icm42600 timestamp module in commonCreate new inv_sensors common modules and move inv_icm42600timestamp module inside. This module will be used by IMUs andalso in the future by other chips.Modify inv_icm42600 driver to use timestamp module and do someheaders cleanup.Signed-off-by: Jean-Baptiste Maneyrol &lt;jean-baptiste.maneyrol@tdk.com&gt;Reviewed-by: Andy Shevchenko &lt;andy.shevchenko@gmail.com&gt;Link: https://lore.kernel.org/r/20230606162147.79667-3-inv.git-commit@tdk.comSigned-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;

            List of files:
            /linux-6.15/drivers/iio/common/Makefile</description>
        <pubDate>Tue, 06 Jun 2023 16:21:45 +0000</pubDate>
        <dc:creator>Jean-Baptiste Maneyrol &lt;jean-baptiste.maneyrol@tdk.com&gt;</dc:creator>
    </item>
<item>
        <title>f774117c - iio/scmi: Adding support for IIO SCMI Based Sensors</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iio/common/Makefile#f774117c</link>
        <description>iio/scmi: Adding support for IIO SCMI Based SensorsThis change provides ARM SCMI Protocol based IIO device.This driver provides support for Accelerometer and Gyroscope usingSCMI Sensor Protocol extensions added in the SCMIv3.0 ARM specificationReported-by: kernel test robot &lt;lkp@intel.com&gt;Signed-off-by: Jyoti Bhayana &lt;jbhayana@google.com&gt;Link: https://lore.kernel.org/r/20210212172235.507028-2-jbhayana@google.comSigned-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Link: https://lore.kernel.org/r/20210309231259.78050-2-jbhayana@google.comSigned-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;

            List of files:
            /linux-6.15/drivers/iio/common/Makefile</description>
        <pubDate>Tue, 09 Mar 2021 23:12:59 +0000</pubDate>
        <dc:creator>Jyoti Bhayana &lt;jbhayana@google.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/drivers/iio/common/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/iio/common/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>974e6f02 - iio: cros_ec_sensors_core: Add common functions for the ChromeOS EC Sensor Hub.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iio/common/Makefile#974e6f02</link>
        <description>iio: cros_ec_sensors_core: Add common functions for the ChromeOS EC Sensor Hub.Add the core functions to be able to support the sensors attached behindthe ChromeOS Embedded Controller and used by other IIO cros-ec sensordrivers.The cros_ec_sensor_core driver matches with current driver in ChromeOS4.4 tree, so it includes all the fixes at the moment. The support forthis driver was made by Gwendal Grignou. The original patch and all thefixes has been squashed and rebased on top of mainline.Signed-off-by: Gwendal Grignou &lt;gwendal@chromium.org&gt;Signed-off-by: Guenter Roeck &lt;groeck@chromium.org&gt;[eballetbo: split, squash and rebase on top of mainline the patchesfound in ChromeOS tree]Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;Signed-off-by: Jonathan Cameron &lt;jic23@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/iio/common/Makefile</description>
        <pubDate>Mon, 01 Aug 2016 09:54:35 +0000</pubDate>
        <dc:creator>Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;</dc:creator>
    </item>
<item>
        <title>d574a87c - Add meas-spec sensors common part</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iio/common/Makefile#d574a87c</link>
        <description>Add meas-spec sensors common partMeasurement specialties drivers common part.These functions are used by further driversin the patchset: TSYS01, TSYS02D, HTU21, MS5637, MS8607Signed-off-by: Ludovic Tancerel &lt;ludovic.tancerel@maplehightech.com&gt;Signed-off-by: Jonathan Cameron &lt;jic23@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/iio/common/Makefile</description>
        <pubDate>Thu, 01 Oct 2015 14:13:36 +0000</pubDate>
        <dc:creator>Ludovic Tancerel &lt;ludovic.tancerel@maplehightech.com&gt;</dc:creator>
    </item>
<item>
        <title>50dd64d5 - iio: common: ssp_sensors: Add sensorhub driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iio/common/Makefile#50dd64d5</link>
        <description>iio: common: ssp_sensors: Add sensorhub driverSensorhub  is MCU dedicated to collect data and manage several sensors.Sensorhub is a spi device which provides a layer for IIO devices. It providessome data parsing and common mechanism for sensorhub sensors.Adds common sensorhub library for sensorhub driver and iio driverswhich uses sensorhub MCU to communicate with sensors.Signed-off-by: Karol Wrona &lt;k.wrona@samsung.com&gt;Acked-by: Kyungmin Park &lt;kyungmin.park@samsung.com&gt;Signed-off-by: Jonathan Cameron &lt;jic23@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/iio/common/Makefile</description>
        <pubDate>Wed, 28 Jan 2015 14:05:50 +0000</pubDate>
        <dc:creator>Karol Wrona &lt;k.wrona@samsung.com&gt;</dc:creator>
    </item>
<item>
        <title>3edc84e6 - iio: Add a comment to about alphabetical order to Kconfigs and Makefiles</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iio/common/Makefile#3edc84e6</link>
        <description>iio: Add a comment to about alphabetical order to Kconfigs and MakefilesKeeping Makefile and Kconfig entries in alphabetical order usually works betterthan just appending new entries at the end, since it reduces the amount ofconflicts. This patch adds a comment to the IIO Kconfig and Makefile files todocument that the entries should be kept in alphabetical order.Also reorder those  entries which weren&apos;t in alphabetical order yet.Signed-off-by: Lars-Peter Clausen &lt;lars@metafoo.de&gt;Signed-off-by: Jonathan Cameron &lt;jic23@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/iio/common/Makefile</description>
        <pubDate>Mon, 15 Jul 2013 07:45:00 +0000</pubDate>
        <dc:creator>Lars-Peter Clausen &lt;lars@metafoo.de&gt;</dc:creator>
    </item>
<item>
        <title>23491b51 - iio:common: Add STMicroelectronics common library</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iio/common/Makefile#23491b51</link>
        <description>iio:common: Add STMicroelectronics common libraryThis patch add a generic library for STMicroelectronics 3-axis sensors.Signed-off-by: Denis Ciocca &lt;denis.ciocca@st.com&gt;Reviewed-by: Lars-Peter Clausen &lt;lars@metafoo.de&gt;Signed-off-by: Jonathan Cameron &lt;jic23@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/iio/common/Makefile</description>
        <pubDate>Fri, 25 Jan 2013 23:44:00 +0000</pubDate>
        <dc:creator>Denis Ciocca &lt;denis.ciocca@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>73c6768b - iio: hid-sensors: Common attribute and trigger</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/iio/common/Makefile#73c6768b</link>
        <description>iio: hid-sensors: Common attribute and triggerThis patch contains the common code, which is used by all HID sensors.There are some common set of attributes, which every hid sensorneeds it. This patch contains all such attributes processing.Also the trigger interface is common among all HID sensors. Thispatch contains common trigger functions utilized by all HID sensors.Signed-off-by: srinivas pandruvada &lt;srinivas.pandruvada@intel.com&gt;Signed-off-by: Jonathan Cameron &lt;jic23@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/iio/common/Makefile</description>
        <pubDate>Wed, 05 Sep 2012 12:56:00 +0000</pubDate>
        <dc:creator>srinivas pandruvada &lt;srinivas.pandruvada@intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
