<?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>2e3a191e - block: add support for partition table defined in OF</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/partitions/Makefile#2e3a191e</link>
        <description>block: add support for partition table defined in OFAdd support for partition table defined in Device Tree. Similar to howit&apos;s done with MTD, add support for defining a fixed partition table indevice tree.A common scenario for this is fixed block (eMMC) embedded devices thathave no MBR or GPT partition table to save storage space. Bootloaderaccess the block device with absolute address of data.This is to complete the functionality with an equivalent implementationwith providing partition table with bootargs, for case where the booargscan&apos;t be modified and tweaking the Device Tree is the only solution tohave an usabe partition table.The implementation follow the fixed-partitions parser used on MTDdevices where a &quot;partitions&quot; node is expected to be declared with&quot;fixed-partitions&quot; compatible in the OF node of the disk device(mmc-card for eMMC for example) and each child node declare a labeland a reg with offset and size. If label is not declared, the node nameis used as fallback. Eventually is also possible to declare the read-onlyproperty to flag the partition as read-only.Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Link: https://lore.kernel.org/r/20241002221306.4403-6-ansuelsmth@gmail.comSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/partitions/Makefile</description>
        <pubDate>Wed, 02 Oct 2024 22:11:45 +0000</pubDate>
        <dc:creator>Christian Marangi &lt;ansuelsmth@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>387048bf - block: merge partition-generic.c and check.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/partitions/Makefile#387048bf</link>
        <description>block: merge partition-generic.c and check.cMerge block/partition-generic.c and block/partitions/check.c intoa single block/partitions/core.c as the content is closely relatedand both files are tiny.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/partitions/Makefile</description>
        <pubDate>Tue, 24 Mar 2020 07:25:30 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&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/block/partitions/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/block/partitions/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>bab55417 - block: support embedded device command line partition</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/partitions/Makefile#bab55417</link>
        <description>block: support embedded device command line partitionRead block device partition table from command line.  The partition usedfor fixed block device (eMMC) embedded device.  It is no MBR, savestorage space.  Bootloader can be easily accessed by absolute address ofdata on the block device.  Users can easily change the partition.This code reference MTD partition, source &quot;drivers/mtd/cmdlinepart.c&quot;About the partition verbose reference&quot;Documentation/block/cmdline-partition.txt&quot;[akpm@linux-foundation.org: fix printk text][yongjun_wei@trendmicro.com.cn: fix error return code in parse_parts()]Signed-off-by: Cai Zhiyong &lt;caizhiyong@huawei.com&gt;Cc: Karel Zak &lt;kzak@redhat.com&gt;Cc: &quot;Wanglin (Albert)&quot; &lt;albert.wanglin@huawei.com&gt;Cc: Marius Groeger &lt;mag@sysgo.de&gt;Cc: David Woodhouse &lt;dwmw2@infradead.org&gt;Cc: Jens Axboe &lt;axboe@kernel.dk&gt;Cc: Brian Norris &lt;computersforpeace@gmail.com&gt;Cc: Artem Bityutskiy &lt;dedekind@infradead.org&gt;Signed-off-by: Wei Yongjun &lt;yongjun_wei@trendmicro.com.cn&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/block/partitions/Makefile</description>
        <pubDate>Wed, 11 Sep 2013 21:20:09 +0000</pubDate>
        <dc:creator>Cai Zhiyong &lt;caizhiyong@huawei.com&gt;</dc:creator>
    </item>
<item>
        <title>6ceea22b - partitions: add aix lvm partition support files</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/partitions/Makefile#6ceea22b</link>
        <description>partitions: add aix lvm partition support filesAdd partitions/aix.h and partitions/aix.c.AIX LVM permits to make &quot;logical volumes&quot; which are made of multipleslices of multiple disks.  The new code allows only access to the&quot;logical volumes&quot; which are made of one slice on the probed disk, aslice being a contiguous disk area.  The code also detects &quot;logicalvolumes&quot; made of multiple slices on the probed disk, but can notdescribe them to the partition layer, because the partition layergeneric code does not support that.  When such non-contiguous &quot;logicalvolumes&quot; are detected, a diagnostic message is printed.[akpm@linux-foundation.org: coding-style fixes]Signed-off-by: Philippe De Muyter &lt;phdm@macqel.be&gt;Cc: Karel Zak &lt;kzak@redhat.com&gt;Cc: Jens Axboe &lt;axboe@kernel.dk&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/block/partitions/Makefile</description>
        <pubDate>Mon, 08 Jul 2013 23:01:29 +0000</pubDate>
        <dc:creator>Philippe De Muyter &lt;phdm@macqel.be&gt;</dc:creator>
    </item>
<item>
        <title>9be96f3f - move fs/partitions to block/</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/partitions/Makefile#9be96f3f</link>
        <description>move fs/partitions to block/Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;

            List of files:
            /linux-6.15/block/partitions/Makefile</description>
        <pubDate>Fri, 16 Sep 2011 04:25:05 +0000</pubDate>
        <dc:creator>Al Viro &lt;viro@zeniv.linux.org.uk&gt;</dc:creator>
    </item>
</channel>
</rss>
