<?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>4d256122 - ALSA: drivers: Use *-y instead of *-objs in Makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/sound/drivers/Makefile#4d256122</link>
        <description>ALSA: drivers: Use *-y instead of *-objs in Makefile*-objs suffix is reserved rather for (user-space) host programs whileusually *-y suffix is used for kernel drivers (although *-objs worksfor that purpose for now).Let&apos;s correct the old usages of *-objs in Makefiles.Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;Reviewed-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;Reviewed-by: Jaroslav Kysela &lt;perex@perex.cz&gt;Link: https://lore.kernel.org/r/20240507135513.14919-7-tiwai@suse.de

            List of files:
            /linux-6.15/sound/drivers/Makefile</description>
        <pubDate>Tue, 07 May 2024 13:55:06 +0000</pubDate>
        <dc:creator>Takashi Iwai &lt;tiwai@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>315a3d57 - ALSA: Implement the new Virtual PCM Test Driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/sound/drivers/Makefile#315a3d57</link>
        <description>ALSA: Implement the new Virtual PCM Test DriverWe have a lot of different virtual media drivers, which can be used fortesting of the userspace applications and media subsystem middle layer.However, all of them are aimed at testing the video functionality andsimulating the video devices. For audio devices we have only snd-dummymodule, which is good in simulating the correct behavior of an ALSA device.I decided to write a tool, which would help to test the userspace ALSAprograms (and the PCM middle layer as well) under unusual circumstancesto figure out how they would behave. So I came up with this Virtual PCMTest Driver.This new Virtual PCM Test Driver has several features which can be usefulduring the userspace ALSA applications testing/fuzzing, or testing/fuzzingof the PCM middle layer. Not all of them can be implemented using theexisting virtual drivers (like dummy or loopback). Here is what can thisdriver do:- Simulate both capture and playback processes- Generate random or pattern-based capture data- Inject delays into the playback and capturing processes- Inject errors during the PCM callbacksAlso, this driver can check the playback stream for containing thepredefined pattern, which is used in the corresponding selftest to checkthe PCM middle layer data transferring functionality. Additionally, thisdriver redefines the default RESET ioctl, and the selftest covers this PCMAPI functionality as well.The driver supports both interleaved and non-interleaved access modes, andhave separate pattern buffers for each channel. The driver supports up to4 channels and up to 8 substreams.Signed-off-by: Ivan Orlov &lt;ivan.orlov0322@gmail.com&gt;Acked-by: Jaroslav Kysela &lt;perex@perex.cz&gt;Link: https://lore.kernel.org/r/20230606193254.20791-2-ivan.orlov0322@gmail.comSigned-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;

            List of files:
            /linux-6.15/sound/drivers/Makefile</description>
        <pubDate>Tue, 06 Jun 2023 19:32:53 +0000</pubDate>
        <dc:creator>Ivan Orlov &lt;ivan.orlov0322@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>54235050 - ALSA: Add generic serial MIDI driver using serial bus API</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/sound/drivers/Makefile#54235050</link>
        <description>ALSA: Add generic serial MIDI driver using serial bus APIGeneric serial MIDI driver adding support for using serial devicescompatible with the serial bus as raw MIDI devices, allowing usingadditional serial devices not compatible with the existingserial-u16550 driver. Supports only setting standard serial baudrates onthe underlying serial device; however, the underlying serial device canbe configured so that a requested 38.4 kBaud is actually the standard MIDI31.25 kBaud. Supports DeviceTree configuration.Signed-off-by: Daniel Kaehn &lt;kaehndan@gmail.com&gt;Reviewed-by: Rob Herring &lt;robh@kernel.org&gt;Link: https://lore.kernel.org/r/20220509145933.1161526-3-kaehndan@gmail.comSigned-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;

            List of files:
            /linux-6.15/sound/drivers/Makefile</description>
        <pubDate>Mon, 09 May 2022 14:59:33 +0000</pubDate>
        <dc:creator>Daniel Kaehn &lt;kaehndan@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>f16dca3e - sound: ac97: Remove sound driver for ancient platform</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/sound/drivers/Makefile#f16dca3e</link>
        <description>sound: ac97: Remove sound driver for ancient platformXilinx PowerPC platforms are no longer supported and none is really testingthese platforms that&apos;s why remove them. If someone has any issue with itthese patches can be reverted.Signed-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;Acked-by: Takashi Iwai &lt;tiwai@suse.de&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/31a3b884dde2c47a30bb2b92355978b97ea70f86.1585575111.git.michal.simek@xilinx.com

            List of files:
            /linux-6.15/sound/drivers/Makefile</description>
        <pubDate>Mon, 30 Mar 2020 13:32:16 +0000</pubDate>
        <dc:creator>Michal Simek &lt;michal.simek@xilinx.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/sound/drivers/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/sound/drivers/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>597603d6 - ALSA: introduce the snd-aloop module for the PCM loopback</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/sound/drivers/Makefile#597603d6</link>
        <description>ALSA: introduce the snd-aloop module for the PCM loopbackThe snd-aloop module allows redirecting of the PCM playback in thekernel back to the user space using the standard ALSA PCM capture API.The module also allows time synchronization with another timing sourceand notifications of playback stream parameter changes.Signed-off-by: Jaroslav Kysela &lt;perex@perex.cz&gt;

            List of files:
            /linux-6.15/sound/drivers/Makefile</description>
        <pubDate>Mon, 09 Aug 2010 12:21:11 +0000</pubDate>
        <dc:creator>Jaroslav Kysela &lt;perex@perex.cz&gt;</dc:creator>
    </item>
<item>
        <title>9ab4d072 - [ALSA] Add PC-speaker sound driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/sound/drivers/Makefile#9ab4d072</link>
        <description>[ALSA] Add PC-speaker sound driverAdded PC-speaker sound driver (snd-pcsp).Signed-off-by: Stas Sergeev &lt;stsp@aknet.ru&gt;Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;

            List of files:
            /linux-6.15/sound/drivers/Makefile</description>
        <pubDate>Mon, 03 Mar 2008 09:53:54 +0000</pubDate>
        <dc:creator>Stas Sergeev &lt;stsp@aknet.ru&gt;</dc:creator>
    </item>
<item>
        <title>a9f00d8d - [ALSA] Xilinx ML403 AC97 Controller Reference device driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/sound/drivers/Makefile#a9f00d8d</link>
        <description>[ALSA] Xilinx ML403 AC97 Controller Reference device driverAdd ALSA support for the opb_ac97_controller_ref_v1_00_a ip core foundin Xilinx&apos; ML403 reference design.Known issue: Currently this driver hits a WARN_ON_ONCE(1) statement inkernel/irq/resend.c (line 70). According to Linus(http://lkml.org/lkml/2007/8/5/5) this may be ignored, right? I haven&apos;thad a look into this &apos;problem&apos; yet.Signed-off-by: Joachim Foerster &lt;JOFT@gmx.de&gt;Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;Signed-off-by: Jaroslav Kysela &lt;perex@perex.cz&gt;

            List of files:
            /linux-6.15/sound/drivers/Makefile</description>
        <pubDate>Mon, 05 Nov 2007 15:06:01 +0000</pubDate>
        <dc:creator>Joachim Foerster &lt;JOFT@gmx.de&gt;</dc:creator>
    </item>
<item>
        <title>c1017a4c - [ALSA] Changed Jaroslav Kysela&apos;s e-mail from perex@suse.cz to perex@perex.cz</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/sound/drivers/Makefile#c1017a4c</link>
        <description>[ALSA] Changed Jaroslav Kysela&apos;s e-mail from perex@suse.cz to perex@perex.czSigned-off-by: Jaroslav Kysela &lt;perex@perex.cz&gt;

            List of files:
            /linux-6.15/sound/drivers/Makefile</description>
        <pubDate>Mon, 15 Oct 2007 07:50:19 +0000</pubDate>
        <dc:creator>Jaroslav Kysela &lt;perex@perex.cz&gt;</dc:creator>
    </item>
<item>
        <title>757e119b - [ALSA] Add snd-portman2x4 driver for Midiman Portman 2x4 MIDI device</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/sound/drivers/Makefile#757e119b</link>
        <description>[ALSA] Add snd-portman2x4 driver for Midiman Portman 2x4 MIDI devicesnd-portman2x4 driver supports Midiman Portman 2x4 parallel portMIDI device.Signed-off-by: Matthias Koenig &lt;mkoenig@suse.de&gt;Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;Signed-off-by: Jaroslav Kysela &lt;perex@suse.cz&gt;

            List of files:
            /linux-6.15/sound/drivers/Makefile</description>
        <pubDate>Thu, 25 Jan 2007 12:15:05 +0000</pubDate>
        <dc:creator>Matthias Koenig &lt;mkoenig@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>68ab801e - [ALSA] Add snd-mts64 driver for ESI Miditerminal 4140</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/sound/drivers/Makefile#68ab801e</link>
        <description>[ALSA] Add snd-mts64 driver for ESI Miditerminal 4140Added snd-mts64 driver for Ego Systems (ESI) Miditerminal 4140by Matthias Koenig &lt;mk@phasorlab.de&gt;.The driver requires parport (CONFIG_PARPORT).Signed-off-by: Matthias Koenig &lt;mk@phasorlab.de&gt;Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;Signed-off-by: Jaroslav Kysela &lt;perex@suse.cz&gt;

            List of files:
            /linux-6.15/sound/drivers/Makefile</description>
        <pubDate>Thu, 27 Jul 2006 14:59:23 +0000</pubDate>
        <dc:creator>Matthias Koenig &lt;mk@phasorlab.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/sound/drivers/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/sound/drivers/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>
