<?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>21b9a47e - media: cec: i2c: ch7322: Add ch7322 CEC controller driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/media/cec/Makefile#21b9a47e</link>
        <description>media: cec: i2c: ch7322: Add ch7322 CEC controller driverAdd a CEC device driver for the Chrontel ch7322 CEC conroller.This is an I2C device capable of sending and receiving CEC messages.Signed-off-by: Jeff Chase &lt;jnchase@google.com&gt;Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/media/cec/Makefile</description>
        <pubDate>Mon, 22 Jun 2020 23:59:50 +0000</pubDate>
        <dc:creator>Jeff Chase &lt;jnchase@google.com&gt;</dc:creator>
    </item>
<item>
        <title>a8106818 - media: move CEC USB drivers to a separate directory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/media/cec/Makefile#a8106818</link>
        <description>media: move CEC USB drivers to a separate directoryAs CEC support doesn&apos;t depend on MEDIA_SUPPORT, let&apos;splace the platform drivers outside the media menu.As a side effect, instead of depends on	USB, driversjust select it.Acked-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/media/cec/Makefile</description>
        <pubDate>Wed, 15 Apr 2020 09:14:25 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>4be5e864 - media: move CEC platform drivers to a separate directory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/media/cec/Makefile#4be5e864</link>
        <description>media: move CEC platform drivers to a separate directoryAs CEC support doesn&apos;t depend on MEDIA_SUPPORT, let&apos;splace the platform drivers outside the media menu.As a side effect, instead of depends on PCI, seco drivercan select it (and DMI).Acked-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/media/cec/Makefile</description>
        <pubDate>Wed, 15 Apr 2020 09:03:40 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>de73b88c - media: cec: move the core to a separate directory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/media/cec/Makefile#de73b88c</link>
        <description>media: cec: move the core to a separate directoryIn preparation for moving CEC drivers to the CEC directory,move the core to a separate place.Acked-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/media/cec/Makefile</description>
        <pubDate>Wed, 15 Apr 2020 08:43:44 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>f94d463f - media: cec: remove cec-edid.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/media/cec/Makefile#f94d463f</link>
        <description>media: cec: remove cec-edid.cMove cec_get_edid_phys_addr() to cec-adap.c. It&apos;s not worth keepinga separate source for this.Signed-off-by: Hans Verkuil &lt;hans.verkuil@cisco.com&gt;Cc: &lt;stable@vger.kernel.org&gt;      # for v4.17 and upSigned-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/media/cec/Makefile</description>
        <pubDate>Thu, 13 Sep 2018 12:00:39 +0000</pubDate>
        <dc:creator>Hans Verkuil &lt;hans.verkuil@cisco.com&gt;</dc:creator>
    </item>
<item>
        <title>22712b38 - media: cec-pin-error-inj: parse/show error injection</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/media/cec/Makefile#22712b38</link>
        <description>media: cec-pin-error-inj: parse/show error injectionAdd support to the CEC Pin framework to parse error injection commandsand to show them.The next patch will do the actual implementation of this.Signed-off-by: Hans Verkuil &lt;hans.verkuil@cisco.com&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;

            List of files:
            /linux-6.15/drivers/media/cec/Makefile</description>
        <pubDate>Tue, 31 Oct 2017 13:55:09 +0000</pubDate>
        <dc:creator>Hans Verkuil &lt;hans.verkuil@cisco.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/media/cec/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/media/cec/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>ea5c8ef2 - media: cec-pin: add low-level pin hardware support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/media/cec/Makefile#ea5c8ef2</link>
        <description>media: cec-pin: add low-level pin hardware supportAdd support for CEC hardware that relies on low-level pin polling orGPIO interrupts.One example is the Allwinner SoC. But any GPIO-based CEC implementation canuse this as well.A GPIO implementation is very suitable as well for debugging: it can useinterrupts to detect state changes and report it. Userspace can then verifyif the bus traffic is correct. This also makes error injection possible.The disadvantage is that it is hard to get the timings right since linuxisn&apos;t a hard realtime system.In general on an idle system it works quite well, but under load the timerwill miss its mark every so often.The debugfs file /sys/kernel/debug/cec/cecX/status gives some statisticswith respect to the timer overruns.When the adapter is unconfigured and the low-level driver supportsinterrupts, then the interrupt will be used to detect changes. This shouldbe quite accurate. But when the adapter is configured a hrtimer has to beused.The hrtimer implements a state machine where for each state the code willread the bus or drive the bus and go on to the next state. It will re-armthe timer with a delay based on the next state.Signed-off-by: Hans Verkuil &lt;hans.verkuil@cisco.com&gt;Reviewed-by: Maxime Ripard &lt;maxime.ripard@free-electrons.com&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;

            List of files:
            /linux-6.15/drivers/media/cec/Makefile</description>
        <pubDate>Tue, 11 Jul 2017 06:30:42 +0000</pubDate>
        <dc:creator>Hans Verkuil &lt;hans.verkuil@cisco.com&gt;</dc:creator>
    </item>
<item>
        <title>e94c3281 - [media] cec: rename MEDIA_CEC_NOTIFIER to CEC_NOTIFIER</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/media/cec/Makefile#e94c3281</link>
        <description>[media] cec: rename MEDIA_CEC_NOTIFIER to CEC_NOTIFIERThis config option is strictly speaking independent of themedia subsystem since it can be used by drm as well.Besides, it looks odd when drivers select CEC_CORE andMEDIA_CEC_NOTIFIER, that&apos;s inconsistent naming.Signed-off-by: Hans Verkuil &lt;hans.verkuil@cisco.com&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;

            List of files:
            /linux-6.15/drivers/media/cec/Makefile</description>
        <pubDate>Sun, 28 May 2017 08:58:04 +0000</pubDate>
        <dc:creator>Hans Verkuil &lt;hans.verkuil@cisco.com&gt;</dc:creator>
    </item>
<item>
        <title>56a263aa - [media] cec: Kconfig cleanup</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/media/cec/Makefile#56a263aa</link>
        <description>[media] cec: Kconfig cleanupThe Kconfig options for the CEC subsystem were a bit messy. Inaddition there were two cec sources (cec-edid.c and cec-notifier.c)that were outside of the media/cec directory, which was weird.Move those sources to media/cec as well.The cec-edid and cec-notifier functionality is now part of the cecmodule and these are no longer separate modules.Also remove the MEDIA_CEC_EDID config option and include it with themain CEC config option (which defined CEC_EDID anyway).Added static inlines to cec-edid.h for dummy functions when CEC_COREisn&apos;t defined.CEC drivers should now depend on CEC_CORE.CEC drivers that need the cec-notifier functionality must explicitlyselect CEC_NOTIFIER.The s5p-cec and stih-cec drivers depended on VIDEO_DEV instead ofCEC_CORE, fix that as well.Signed-off-by: Hans Verkuil &lt;hans.verkuil@cisco.com&gt;Acked-by: Benjamin Gaignard &lt;benjamin.gaignard@linaro.org&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;

            List of files:
            /linux-6.15/drivers/media/cec/Makefile</description>
        <pubDate>Mon, 17 Apr 2017 10:44:35 +0000</pubDate>
        <dc:creator>Hans Verkuil &lt;hans.verkuil@cisco.com&gt;</dc:creator>
    </item>
<item>
        <title>0dbacebe - [media] cec: move the CEC framework out of staging and to media</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/media/cec/Makefile#0dbacebe</link>
        <description>[media] cec: move the CEC framework out of staging and to mediaThe last open issues have been addressed, so it is time to movethis out of staging and into the mainline and to move the publiccec headers to include/uapi/linux.Signed-off-by: Hans Verkuil &lt;hans.verkuil@cisco.com&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;

            List of files:
            /linux-6.15/drivers/media/cec/Makefile</description>
        <pubDate>Wed, 02 Nov 2016 10:25:28 +0000</pubDate>
        <dc:creator>Hans Verkuil &lt;hans.verkuil@cisco.com&gt;</dc:creator>
    </item>
</channel>
</rss>
