<?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>a4f17cc7 - s390/cio: add CRW inject functionality</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#a4f17cc7</link>
        <description>s390/cio: add CRW inject functionalityThis patch introduces the mechanism to inject artificial events to theCIO layer.One of the main-event type which triggers the CommonIO operations areChannel Report events. When a malfunction or other condition affectingchannel-subsystem operation is recognized, a Channel Report Word(consisting of one or more CRWs) describing the condition is madepending for retrieval and analysis by the program. The CRW containsinformation concerning the identity and state of a facility followingthe detection of the malfunction or other condition.The patch introduces two debugfs interfaces which can be used to inject&apos;artificial&apos; events from the userspace. It is intended to provide an easymeans to increase the test coverage for CIO code. And this functionalitycan be enabled via a new configuration option CONFIG_CIO_INJECT.The newly introduces debugfs interfaces can be used as mentioned belowto generate different fake-events. To use the crw_inject, first we shouldenable it by using enable_inject interface.i.eecho 1 &gt; /sys/kernel/debug/s390/cio/enable_injectAfter the first step, user can simulate CRW as follows:echo &lt;solicited&gt; &lt;overflow&gt; &lt;chaining&gt; &lt;rsc&gt; &lt;ancillary&gt; &lt;erc&gt; &lt;rsid&gt; \                               &gt; /sys/kernel/debug/s390/cio/crw_injectExample:A permanent error ERC on CHPID 0x60 would look like this:  echo 0 0 0 4 0 6 0x60 &gt; /sys/kernel/debug/s390/cio/crw_injectand an initialized ERC on the same CHPID:  echo 0 0 0 4 0 2 0x60 &gt; /sys/kernel/debug/s390/cio/crw_injectSigned-off-by: Vineeth Vijayan &lt;vneethv@linux.ibm.com&gt;Reviewed-by: Peter Oberparleiter &lt;oberpar@linux.ibm.com&gt;Signed-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Sun, 07 Feb 2021 19:40:58 +0000</pubDate>
        <dc:creator>Vineeth Vijayan &lt;vneethv@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>64a715ab - s390/cio: introduce CIO debugfs directory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#64a715ab</link>
        <description>s390/cio: introduce CIO debugfs directoryThis patch introduces an s390 Common I/O layer debugfs directory that isintended to provide access to debugging-related CIO functions and data.The directory is created as /sys/kernel/debug/s390/cioSigned-off-by: Vineeth Vijayan &lt;vneethv@linux.ibm.com&gt;Reviewed-by: Peter Oberparleiter &lt;oberpar@linux.ibm.com&gt;Signed-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Thu, 04 Feb 2021 06:03:00 +0000</pubDate>
        <dc:creator>Vineeth Vijayan &lt;vneethv@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>24c98674 - vfio-ccw: Introduce a new schib region</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#24c98674</link>
        <description>vfio-ccw: Introduce a new schib regionThe schib region can be used by userspace to get the subchannel-information block (SCHIB) for the passthrough subchannel.This can be useful to get information such as channel pathinformation via the SCHIB.PMCW fields.Signed-off-by: Farhan Ali &lt;alifm@linux.ibm.com&gt;Signed-off-by: Eric Farman &lt;farman@linux.ibm.com&gt;Reviewed-by: Cornelia Huck &lt;cohuck@redhat.com&gt;Message-Id: &lt;20200505122745.53208-5-farman@linux.ibm.com&gt;Signed-off-by: Cornelia Huck &lt;cohuck@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Tue, 05 May 2020 12:27:41 +0000</pubDate>
        <dc:creator>Farhan Ali &lt;alifm@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>7af52cca - vfio-ccw: Refactor how the traces are built</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#7af52cca</link>
        <description>vfio-ccw: Refactor how the traces are builtCommit 3cd90214b70f (&quot;vfio: ccw: add tracepoints for interesting errorpaths&quot;) added a quick trace point to determine where a channel programfailed while being processed.  It&apos;s a great addition, but adding moretraces to vfio-ccw is more cumbersome than it needs to be.Let&apos;s refactor how this is done, so that additional traces are easierto add and can exist outside of the FSM if we ever desire.Signed-off-by: Eric Farman &lt;farman@linux.ibm.com&gt;Reviewed-by: Cornelia Huck &lt;cohuck@redhat.com&gt;Message-Id: &lt;20191016142040.14132-2-farman@linux.ibm.com&gt;Acked-by: Halil Pasic &lt;pasic@linux.ibm.com&gt;Signed-off-by: Cornelia Huck &lt;cohuck@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Wed, 16 Oct 2019 14:20:37 +0000</pubDate>
        <dc:creator>Eric Farman &lt;farman@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>d5afd5d1 - vfio-ccw: add handling for async channel instructions</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#d5afd5d1</link>
        <description>vfio-ccw: add handling for async channel instructionsAdd a region to the vfio-ccw device that can be used to submitasynchronous I/O instructions. ssch continues to be handled by theexisting I/O region; the new region handles hsch and csch.Interrupt status continues to be reported through the same channelsas for ssch.Acked-by: Eric Farman &lt;farman@linux.ibm.com&gt;Reviewed-by: Farhan Ali &lt;alifm@linux.ibm.com&gt;Signed-off-by: Cornelia Huck &lt;cohuck@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Mon, 23 Jul 2018 14:03:27 +0000</pubDate>
        <dc:creator>Cornelia Huck &lt;cohuck@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>3cd90214 - vfio: ccw: add tracepoints for interesting error paths</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#3cd90214</link>
        <description>vfio: ccw: add tracepoints for interesting error pathsAdd some tracepoints so we can inspect what is not working as is should.Signed-off-by: Halil Pasic &lt;pasic@linux.ibm.com&gt;Signed-off-by: Dong Jia Shi &lt;bjsdjshi@linux.ibm.com&gt;Message-Id: &lt;20180523025645.8978-5-bjsdjshi@linux.ibm.com&gt;Signed-off-by: Cornelia Huck &lt;cohuck@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Wed, 23 May 2018 02:56:45 +0000</pubDate>
        <dc:creator>Halil Pasic &lt;pasic@linux.ibm.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/s390/cio/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/s390/cio/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>bbe37e4c - vfio: ccw: introduce a finite state machine</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#bbe37e4c</link>
        <description>vfio: ccw: introduce a finite state machineThe current implementation doesn&apos;t check if the subchannel is in aproper device state when handling an event. Let&apos;s introducea finite state machine to manage the state/event change.Signed-off-by: Dong Jia Shi &lt;bjsdjshi@linux.vnet.ibm.com&gt;Message-Id: &lt;20170317031743.40128-14-bjsdjshi@linux.vnet.ibm.com&gt;Signed-off-by: Cornelia Huck &lt;cornelia.huck@de.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Fri, 17 Mar 2017 03:17:40 +0000</pubDate>
        <dc:creator>Dong Jia Shi &lt;bjsdjshi@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>84cd8fc4 - vfio: ccw: register vfio_ccw to the mediated device framework</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#84cd8fc4</link>
        <description>vfio: ccw: register vfio_ccw to the mediated device frameworkTo make vfio support subchannel devices, we need to leverage themediated device framework to create a mediated device for thesubchannel device.This registers the subchannel device to the mediated deviceframework during probe to enable mediated device creation.Reviewed-by: Pierre Morel &lt;pmorel@linux.vnet.ibm.com&gt;Signed-off-by: Dong Jia Shi &lt;bjsdjshi@linux.vnet.ibm.com&gt;Message-Id: &lt;20170317031743.40128-7-bjsdjshi@linux.vnet.ibm.com&gt;Signed-off-by: Cornelia Huck &lt;cornelia.huck@de.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Fri, 17 Mar 2017 03:17:33 +0000</pubDate>
        <dc:creator>Dong Jia Shi &lt;bjsdjshi@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>0a19e61e - vfio: ccw: introduce channel program interfaces</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#0a19e61e</link>
        <description>vfio: ccw: introduce channel program interfacesIntroduce ccwchain structure and helper functions that can be used tohandle a channel program issued from a virtual machine.The following limitations apply:1. Supports only prefetch enabled mode.2. Supports idal(c64) ccw chaining.3. Supports 4k idaw.4. Supports ccw1.5. Supports direct ccw chaining by translating them to idal ccws.CCW translation requires to leverage the vfio_(un)pin_pages interfacesto pin/unpin sets of mem pages frequently. Currently we have a lack ofsupport to do this in an efficient way. So we introduce pfn_array datastructure and helper functions to handle pin/unpin operations here.Signed-off-by: Dong Jia Shi &lt;bjsdjshi@linux.vnet.ibm.com&gt;Message-Id: &lt;20170317031743.40128-6-bjsdjshi@linux.vnet.ibm.com&gt;Signed-off-by: Cornelia Huck &lt;cornelia.huck@de.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Fri, 17 Mar 2017 03:17:32 +0000</pubDate>
        <dc:creator>Dong Jia Shi &lt;bjsdjshi@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>63f1934d - vfio: ccw: basic implementation for vfio_ccw driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#63f1934d</link>
        <description>vfio: ccw: basic implementation for vfio_ccw driverTo make vfio support subchannel devices, we need a css driver forthe vfio subchannels. This patch adds a basic vfio-ccw subchanneldriver for this purpose.To enable VFIO for vfio-ccw, enable S390_CCW_IOMMU config optionand configure VFIO as required.Acked-by: Pierre Morel &lt;pmorel@linux.vnet.ibm.com&gt;Signed-off-by: Dong Jia Shi &lt;bjsdjshi@linux.vnet.ibm.com&gt;Message-Id: &lt;20170317031743.40128-5-bjsdjshi@linux.vnet.ibm.com&gt;Signed-off-by: Cornelia Huck &lt;cornelia.huck@de.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Fri, 17 Mar 2017 03:17:31 +0000</pubDate>
        <dc:creator>Dong Jia Shi &lt;bjsdjshi@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>11b64c8a - s390/cio: Change I/O instructions from inline to normal functions</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#11b64c8a</link>
        <description>s390/cio: Change I/O instructions from inline to normal functionsAdding tracepoints to inline functions adds tracepoint invocation codefor each instance where the function is inlined. The resulting increasein kernel code size can have negative impact: - More cache misses in instruction cache - Reduced amount of DMA-capable memoryTherefore change all functions implementing I/O instructions from inlineto normal functions.Bloat-o-meter summary after change (using performance_defconfig):  add/remove: 24/2 grow/shrink: 4/39 up/down: 2205/-4858 (-2653)Signed-off-by: Peter Oberparleiter &lt;oberpar@linux.vnet.ibm.com&gt;Acked-by: Cornelia Huck &lt;cornelia.huck@de.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Fri, 18 Dec 2015 11:59:40 +0000</pubDate>
        <dc:creator>Peter Oberparleiter &lt;oberpar@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>42248979 - s390/cio: Introduce common I/O layer tracepoints</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#42248979</link>
        <description>s390/cio: Introduce common I/O layer tracepointsAdd tracepoints to interrupt handler and core inline assemblies used bythe s390 common I/O layer. These tracepoints can be used to monitor andvalidate hardware and hypervisor requests and responses.Signed-off-by: Peter Oberparleiter &lt;oberpar@linux.vnet.ibm.com&gt;Reviewed-by: Sebastian Ott &lt;sebott@linux.vnet.ibm.com&gt;Reviewed-by: Cornelia Huck &lt;cornelia.huck@de.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Fri, 18 Dec 2015 11:59:36 +0000</pubDate>
        <dc:creator>Peter Oberparleiter &lt;oberpar@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>eadb86ab - s390/cio: add eadm subchannel driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#eadb86ab</link>
        <description>s390/cio: add eadm subchannel driverThis driver allows usage of EADM subchannels. EADM subchannelsact as a communication vehicle for SCM increments.Signed-off-by: Sebastian Ott &lt;sebott@linux.vnet.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Tue, 28 Aug 2012 14:48:16 +0000</pubDate>
        <dc:creator>Sebastian Ott &lt;sebott@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>1d1c8f78 - s390: add scm bus driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#1d1c8f78</link>
        <description>s390: add scm bus driverBus driver to manage Storage Class Memory.Signed-off-by: Sebastian Ott &lt;sebott@linux.vnet.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Tue, 28 Aug 2012 14:46:26 +0000</pubDate>
        <dc:creator>Sebastian Ott &lt;sebott@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>6486cda6 - [S390] qdio: convert global statistics to per-device stats</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#6486cda6</link>
        <description>[S390] qdio: convert global statistics to per-device statsRevamp the qdio performance statistics and move them from procfs todebugfs using the seq_file interface. Since the statistics are notintended for the general user the removal of /proc/qdio_perf shouldnot surprise anyone.The per device statistics are disabled by default, writing 1 to/&lt;debugfs mountpoint&gt;/qdio/&lt;device bus ID&gt;/statistics enables thestatistics for the given device.Signed-off-by: Jan Glauber &lt;jang@linux.vnet.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Mon, 04 Jan 2010 08:05:42 +0000</pubDate>
        <dc:creator>Jan Glauber &lt;jang@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>e1f0fbd6 - [S390] cio: consistent infrastructure for internal I/O requests</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#e1f0fbd6</link>
        <description>[S390] cio: consistent infrastructure for internal I/O requestsReduce code duplication by introducing a central infrastructure toperform an internal I/O operation on a CCW device.Signed-off-by: Peter Oberparleiter &lt;peter.oberparleiter@de.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Mon, 07 Dec 2009 11:51:25 +0000</pubDate>
        <dc:creator>Peter Oberparleiter &lt;peter.oberparleiter@de.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>62733e5a - [S390] cio: move scsw helper functions to header file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#62733e5a</link>
        <description>[S390] cio: move scsw helper functions to header fileAll scsw helper functions are very short and usage of them shouldn&apos;tresult in function calls. Therefore we move them to a separate headerfile.Also saves a lot of EXPORT_SYMBOLs.Signed-off-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Fri, 11 Sep 2009 08:28:15 +0000</pubDate>
        <dc:creator>Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>f5daba1d - [S390] split/move machine check handler code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#f5daba1d</link>
        <description>[S390] split/move machine check handler codeSplit machine check handler code and move it to cio and kernel codewhere it belongs to. No functional change.Signed-off-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Thu, 26 Mar 2009 14:24:01 +0000</pubDate>
        <dc:creator>Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>779e6e1c - [S390] qdio: new qdio driver.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/s390/cio/Makefile#779e6e1c</link>
        <description>[S390] qdio: new qdio driver.List of major changes:- split qdio driver into several files- seperation of thin interrupt code- improved handling for multiple thin interrupt devices- inbound and outbound processing now always runs in tasklet context- significant less tasklet schedules per interrupt needed- merged qebsm with non-qebsm handling- cleanup qdio interface and added kerneldoc- coding styleReviewed-by: Cornelia Huck &lt;cornelia.huck@de.ibm.com&gt;Reviewed-by: Utz Bacher &lt;utz.bacher@de.ibm.com&gt;Reviewed-by: Ursula Braun &lt;braunu@de.ibm.com&gt;Signed-off-by: Jan Glauber &lt;jang@linux.vnet.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;Signed-off-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/s390/cio/Makefile</description>
        <pubDate>Thu, 17 Jul 2008 15:16:48 +0000</pubDate>
        <dc:creator>Jan Glauber &lt;jang@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
</channel>
</rss>
