Loading CREDITS +2 −4 Original line number Original line Diff line number Diff line Loading @@ -3643,11 +3643,9 @@ S: Cambridge. CB1 7EG S: England S: England N: Chris Wright N: Chris Wright E: chrisw@osdl.org E: chrisw@sous-sol.org D: hacking on LSM framework and security modules. D: hacking on LSM framework and security modules. S: c/o OSDL S: Portland, OR S: 12725 SW Millikan Way, Suite 400 S: Beaverton, OR 97005 S: USA S: USA N: Michal Wronski N: Michal Wronski Loading Documentation/cpu-hotplug.txt +24 −3 Original line number Original line Diff line number Diff line Loading @@ -11,6 +11,8 @@ Joel Schopp <jschopp@austin.ibm.com> Joel Schopp <jschopp@austin.ibm.com> ia64/x86_64: ia64/x86_64: Ashok Raj <ashok.raj@intel.com> Ashok Raj <ashok.raj@intel.com> s390: Heiko Carstens <heiko.carstens@de.ibm.com> Authors: Ashok Raj <ashok.raj@intel.com> Authors: Ashok Raj <ashok.raj@intel.com> Lots of feedback: Nathan Lynch <nathanl@austin.ibm.com>, Lots of feedback: Nathan Lynch <nathanl@austin.ibm.com>, Loading Loading @@ -44,10 +46,29 @@ maxcpus=n Restrict boot time cpus to n. Say if you have 4 cpus, using maxcpus=2 will only boot 2. You can choose to bring the maxcpus=2 will only boot 2. You can choose to bring the other cpus later online, read FAQ's for more info. other cpus later online, read FAQ's for more info. additional_cpus=n [x86_64 only] use this to limit hotpluggable cpus. additional_cpus*=n Use this to limit hotpluggable cpus. This option sets This option sets cpu_possible_map = cpu_present_map + additional_cpus cpu_possible_map = cpu_present_map + additional_cpus (*) Option valid only for following architectures - x86_64, ia64, s390 ia64 and x86_64 use the number of disabled local apics in ACPI tables MADT to determine the number of potentially hot-pluggable cpus. The implementation should only rely on this to count the #of cpus, but *MUST* not rely on the apicid values in those tables for disabled apics. In the event BIOS doesnt mark such hot-pluggable cpus as disabled entries, one could use this parameter "additional_cpus=x" to represent those cpus in the cpu_possible_map. s390 uses the number of cpus it detects at IPL time to also the number of bits in cpu_possible_map. If it is desired to add additional cpus at a later time the number should be specified using this option or the possible_cpus option. possible_cpus=n [s390 only] use this to set hotpluggable cpus. This option sets possible_cpus bits in cpu_possible_map. Thus keeping the numbers of bits set constant even if the machine gets rebooted. This option overrides additional_cpus. CPU maps and such CPU maps and such ----------------- ----------------- [More on cpumaps and primitive to manipulate, please check [More on cpumaps and primitive to manipulate, please check Loading Documentation/dvb/bt8xx.txt +5 −1 Original line number Original line Diff line number Diff line Loading @@ -111,4 +111,8 @@ source: linux/Documentation/video4linux/CARDLIST.bttv If you have problems with this please do ask on the mailing list. If you have problems with this please do ask on the mailing list. -- -- Authors: Richard Walker, Jamie Honan, Michael Hunold, Manu Abraham Authors: Richard Walker, Jamie Honan, Michael Hunold, Manu Abraham, Michael Krufky Documentation/feature-removal-schedule.txt +18 −0 Original line number Original line Diff line number Diff line Loading @@ -171,3 +171,21 @@ Why: The ISA interface is faster and should be always available. The I2C probing is also known to cause trouble in at least one case (see probing is also known to cause trouble in at least one case (see bug #5889.) bug #5889.) Who: Jean Delvare <khali@linux-fr.org> Who: Jean Delvare <khali@linux-fr.org> --------------------------- What: mount/umount uevents When: February 2007 Why: These events are not correct, and do not properly let userspace know when a file system has been mounted or unmounted. Userspace should poll the /proc/mounts file instead to detect this properly. Who: Greg Kroah-Hartman <gregkh@suse.de> --------------------------- What: Support for NEC DDB5074 and DDB5476 evaluation boards. When: June 2006 Why: Board specific code doesn't build anymore since ~2.6.0 and no users have complained indicating there is no more need for these boards. This should really be considered a last call. Who: Ralf Baechle <ralf@linux-mips.org> Documentation/filesystems/ntfs.txt +6 −0 Original line number Original line Diff line number Diff line Loading @@ -457,6 +457,12 @@ ChangeLog Note, a technical ChangeLog aimed at kernel hackers is in fs/ntfs/ChangeLog. Note, a technical ChangeLog aimed at kernel hackers is in fs/ntfs/ChangeLog. 2.1.26: - Implement support for sector sizes above 512 bytes (up to the maximum supported by NTFS which is 4096 bytes). - Enhance support for NTFS volumes which were supported by Windows but not by Linux due to invalid attribute list attribute flags. - A few minor updates and bug fixes. 2.1.25: 2.1.25: - Write support is now extended with write(2) being able to both - Write support is now extended with write(2) being able to both overwrite existing file data and to extend files. Also, if a write overwrite existing file data and to extend files. Also, if a write Loading Loading
CREDITS +2 −4 Original line number Original line Diff line number Diff line Loading @@ -3643,11 +3643,9 @@ S: Cambridge. CB1 7EG S: England S: England N: Chris Wright N: Chris Wright E: chrisw@osdl.org E: chrisw@sous-sol.org D: hacking on LSM framework and security modules. D: hacking on LSM framework and security modules. S: c/o OSDL S: Portland, OR S: 12725 SW Millikan Way, Suite 400 S: Beaverton, OR 97005 S: USA S: USA N: Michal Wronski N: Michal Wronski Loading
Documentation/cpu-hotplug.txt +24 −3 Original line number Original line Diff line number Diff line Loading @@ -11,6 +11,8 @@ Joel Schopp <jschopp@austin.ibm.com> Joel Schopp <jschopp@austin.ibm.com> ia64/x86_64: ia64/x86_64: Ashok Raj <ashok.raj@intel.com> Ashok Raj <ashok.raj@intel.com> s390: Heiko Carstens <heiko.carstens@de.ibm.com> Authors: Ashok Raj <ashok.raj@intel.com> Authors: Ashok Raj <ashok.raj@intel.com> Lots of feedback: Nathan Lynch <nathanl@austin.ibm.com>, Lots of feedback: Nathan Lynch <nathanl@austin.ibm.com>, Loading Loading @@ -44,10 +46,29 @@ maxcpus=n Restrict boot time cpus to n. Say if you have 4 cpus, using maxcpus=2 will only boot 2. You can choose to bring the maxcpus=2 will only boot 2. You can choose to bring the other cpus later online, read FAQ's for more info. other cpus later online, read FAQ's for more info. additional_cpus=n [x86_64 only] use this to limit hotpluggable cpus. additional_cpus*=n Use this to limit hotpluggable cpus. This option sets This option sets cpu_possible_map = cpu_present_map + additional_cpus cpu_possible_map = cpu_present_map + additional_cpus (*) Option valid only for following architectures - x86_64, ia64, s390 ia64 and x86_64 use the number of disabled local apics in ACPI tables MADT to determine the number of potentially hot-pluggable cpus. The implementation should only rely on this to count the #of cpus, but *MUST* not rely on the apicid values in those tables for disabled apics. In the event BIOS doesnt mark such hot-pluggable cpus as disabled entries, one could use this parameter "additional_cpus=x" to represent those cpus in the cpu_possible_map. s390 uses the number of cpus it detects at IPL time to also the number of bits in cpu_possible_map. If it is desired to add additional cpus at a later time the number should be specified using this option or the possible_cpus option. possible_cpus=n [s390 only] use this to set hotpluggable cpus. This option sets possible_cpus bits in cpu_possible_map. Thus keeping the numbers of bits set constant even if the machine gets rebooted. This option overrides additional_cpus. CPU maps and such CPU maps and such ----------------- ----------------- [More on cpumaps and primitive to manipulate, please check [More on cpumaps and primitive to manipulate, please check Loading
Documentation/dvb/bt8xx.txt +5 −1 Original line number Original line Diff line number Diff line Loading @@ -111,4 +111,8 @@ source: linux/Documentation/video4linux/CARDLIST.bttv If you have problems with this please do ask on the mailing list. If you have problems with this please do ask on the mailing list. -- -- Authors: Richard Walker, Jamie Honan, Michael Hunold, Manu Abraham Authors: Richard Walker, Jamie Honan, Michael Hunold, Manu Abraham, Michael Krufky
Documentation/feature-removal-schedule.txt +18 −0 Original line number Original line Diff line number Diff line Loading @@ -171,3 +171,21 @@ Why: The ISA interface is faster and should be always available. The I2C probing is also known to cause trouble in at least one case (see probing is also known to cause trouble in at least one case (see bug #5889.) bug #5889.) Who: Jean Delvare <khali@linux-fr.org> Who: Jean Delvare <khali@linux-fr.org> --------------------------- What: mount/umount uevents When: February 2007 Why: These events are not correct, and do not properly let userspace know when a file system has been mounted or unmounted. Userspace should poll the /proc/mounts file instead to detect this properly. Who: Greg Kroah-Hartman <gregkh@suse.de> --------------------------- What: Support for NEC DDB5074 and DDB5476 evaluation boards. When: June 2006 Why: Board specific code doesn't build anymore since ~2.6.0 and no users have complained indicating there is no more need for these boards. This should really be considered a last call. Who: Ralf Baechle <ralf@linux-mips.org>
Documentation/filesystems/ntfs.txt +6 −0 Original line number Original line Diff line number Diff line Loading @@ -457,6 +457,12 @@ ChangeLog Note, a technical ChangeLog aimed at kernel hackers is in fs/ntfs/ChangeLog. Note, a technical ChangeLog aimed at kernel hackers is in fs/ntfs/ChangeLog. 2.1.26: - Implement support for sector sizes above 512 bytes (up to the maximum supported by NTFS which is 4096 bytes). - Enhance support for NTFS volumes which were supported by Windows but not by Linux due to invalid attribute list attribute flags. - A few minor updates and bug fixes. 2.1.25: 2.1.25: - Write support is now extended with write(2) being able to both - Write support is now extended with write(2) being able to both overwrite existing file data and to extend files. Also, if a write overwrite existing file data and to extend files. Also, if a write Loading
