<?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>01c7a597 - fs: dlm: remove deprecated code parts</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/dlm/Makefile#01c7a597</link>
        <description>fs: dlm: remove deprecated code partsThis patch removes code parts which was declared deprecated bycommit 6b0afc0cc3e9 (&quot;fs: dlm: don&apos;t use deprecated timeout features bydefault&quot;). This contains the following dlm functionality:- start a cancel of a dlm request did not complete after certain timeout:  The current way how dlm cancellation works and interfering with other  dlm requests triggered by the user can end in an overlapping and  returning in -EBUSY. The most user don&apos;t handle this case and are  unaware that DLM can return such errno in such situation. Due the  timeout the user are mostly unaware when this happens.- start a netlink warning messages for user space if dlm requests did  not complete after certain timeout:  This feature was never being built in the only known dlm user space side.  As we are to remove the timeout cancellation feature we can directly  remove this feature as well.There might be the possibility to bring the timeout cancellation featureback. However the current way of handling the -EBUSY case which is onlya software limitation and not a hardware limitation should be changed.We minimize the current code base in DLM cancellation feature to not haveto deal with those existing features while solving the DLM cancellationfeature in general.UAPI define DLM_LSFL_TIMEWARN is commented as deprecated and reservedvalue. We should avoid at first to give it a new meaning but letpossible users still compile by keeping this define. In far future wecan give this flag a new meaning. The same for the DLM_LKF_TIMEOUT lockrequest flag.Signed-off-by: Alexander Aring &lt;aahringo@redhat.com&gt;Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;

            List of files:
            /linux-6.15/fs/dlm/Makefile</description>
        <pubDate>Mon, 06 Mar 2023 20:48:11 +0000</pubDate>
        <dc:creator>Alexander Aring &lt;aahringo@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>6b0afc0c - fs: dlm: don&apos;t use deprecated timeout features by default</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/dlm/Makefile#6b0afc0c</link>
        <description>fs: dlm: don&apos;t use deprecated timeout features by defaultThis patch will disable use of deprecated timeout features ifCONFIG_DLM_DEPRECATED_API is not set.  The deprecated featureswill be removed in upcoming kernel release v6.2.Signed-off-by: Alexander Aring &lt;aahringo@redhat.com&gt;Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;

            List of files:
            /linux-6.15/fs/dlm/Makefile</description>
        <pubDate>Wed, 22 Jun 2022 18:45:23 +0000</pubDate>
        <dc:creator>Alexander Aring &lt;aahringo@redhat.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/fs/dlm/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/fs/dlm/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>2402211a - dlm: move plock code from gfs2</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/dlm/Makefile#2402211a</link>
        <description>dlm: move plock code from gfs2Move the code that handles cluster posix locks from gfs2 into the dlmso that it can be used by both gfs2 and ocfs2.Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;

            List of files:
            /linux-6.15/fs/dlm/Makefile</description>
        <pubDate>Fri, 14 Mar 2008 20:09:15 +0000</pubDate>
        <dc:creator>David Teigland &lt;teigland@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>3ae1acf9 - [DLM] add lock timeouts and warnings [2/6]</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/dlm/Makefile#3ae1acf9</link>
        <description>[DLM] add lock timeouts and warnings [2/6]New features: lock timeouts and time warnings.  If the DLM_LKF_TIMEOUTflag is set, then the request/conversion will be canceled after waitingthe specified number of centiseconds (specified per lock).  This featureis only available for locks requested through libdlm (can be enabled forkernel dlm users if there&apos;s a use for it.)If the new DLM_LSFL_TIMEWARN flag is set when creating the lockspace, thena warning message will be sent to userspace (using genetlink) after arequest/conversion has been waiting for a given number of centiseconds(configurable per node).  The time warnings will be used in the futureto do deadlock detection in userspace.Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;Signed-off-by: Steven Whitehouse &lt;swhiteho@redhat.com&gt;

            List of files:
            /linux-6.15/fs/dlm/Makefile</description>
        <pubDate>Fri, 18 May 2007 13:59:31 +0000</pubDate>
        <dc:creator>David Teigland &lt;teigland@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>6ed7257b - [DLM] Consolidate transport protocols</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/dlm/Makefile#6ed7257b</link>
        <description>[DLM] Consolidate transport protocolsThis patch consolidates the TCP &amp; SCTP protocols for the DLM into a single fileand makes it switchable at run-time (well, at least before the DLM actuallystarts up!)For RHEL5 this patch requires Neil Horman&apos;s patch that expands the in-kernelsocket API but that has already been twice ACKed so it should be OK.The patch adds a new lowcomms.c file that replaces the existing lowcomms-sctp.c&amp; lowcomms-tcp.c files.Signed-off-By: Patrick Caulfield &lt;pcaulfie@redhat.com&gt;Signed-off-by: Steven Whitehouse &lt;swhiteho@redhat.com&gt;

            List of files:
            /linux-6.15/fs/dlm/Makefile</description>
        <pubDate>Tue, 17 Apr 2007 14:39:57 +0000</pubDate>
        <dc:creator>Patrick Caulfield &lt;pcaulfie@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>fdda387f - [DLM] Add support for tcp communications</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/dlm/Makefile#fdda387f</link>
        <description>[DLM] Add support for tcp communicationsThe following patch adds a TCP based communications layerto the DLM which is compile time selectable. The existing SCTPlayer gives the advantage of allowing multihoming, whereasthe TCP layer has been heavily tested in previous versions ofthe DLM and is known to be robust and therefore can be used asa baseline for performance testing.Signed-off-by: Patrick Caulfield &lt;pcaulfie@redhat.com&gt;Signed-off-by: Steven Whitehouse &lt;swhiteho@redhat.com&gt;

            List of files:
            /linux-6.15/fs/dlm/Makefile</description>
        <pubDate>Thu, 02 Nov 2006 16:19:21 +0000</pubDate>
        <dc:creator>Patrick Caulfield &lt;pcaulfie@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>597d0cae - [DLM] dlm: user locks</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/dlm/Makefile#597d0cae</link>
        <description>[DLM] dlm: user locksThis changes the way the dlm handles user locks.  The core dlm is nowaware of user locks so they can be dealt with more efficiently.  There isno more dlm_device module which previously managed its own duplicate copyof every user lock.Signed-off-by: Patrick Caulfield &lt;pcaulfie@redhat.com&gt;Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;Signed-off-by: Steven Whitehouse &lt;swhiteho@redhat.com&gt;

            List of files:
            /linux-6.15/fs/dlm/Makefile</description>
        <pubDate>Wed, 12 Jul 2006 21:44:04 +0000</pubDate>
        <dc:creator>David Teigland &lt;teigland@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>e7fd4179 - [DLM] The core of the DLM for GFS2/CLVM</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/dlm/Makefile#e7fd4179</link>
        <description>[DLM] The core of the DLM for GFS2/CLVMThis is the core of the distributed lock manager which is requiredto use GFS2 as a cluster filesystem. It is also used by CLVM andcan be used as a standalone lock manager independantly of eitherof these two projects.It implements VAX-style locking modes.Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;Signed-off-by: Steve Whitehouse &lt;swhiteho@redhat.com&gt;

            List of files:
            /linux-6.15/fs/dlm/Makefile</description>
        <pubDate>Wed, 18 Jan 2006 09:30:29 +0000</pubDate>
        <dc:creator>David Teigland &lt;teigland@redhat.com&gt;</dc:creator>
    </item>
</channel>
</rss>
