staging:lustre: Update license and copyright for kernel comm
PATCH 5/5 staging:lustre: Update license and copyright for kernel comm
Quoted 6 lines · James Simmons
From: frank zago <[email protected]>
Point to the right place for GNU license. Update Intel copyright. Update Nathan Rutmans email address. This was broken out of the original patch 14270.
Quoted 7 lines
[...]
- * http://www.sun.com/software/products/lustre/docs/GPLv2.pdf
- *
- * Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,
- * CA 95054 USA or visit www.sun.com if you need additional information or
- * have any questions.
That text is in every files. You should kill all references.
-thanks-
Simmons
PATCH 5/5 staging:lustre: Update license and copyright for kernel comm
Quoted 8 lines
Quoted 6 lines
- * http://www.sun.com/software/products/lustre/docs/GPLv2.pdf
- *
- * Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,
- * CA 95054 USA or visit www.sun.com if you need additional information or
- * have any questions.That text is in every files. You should kill all references.
That would be a mighty big patch. A patch already exist in our development branch to update the copyright so that will be eventually backported to the staging tree. I can look into updating the rest after the copyright patch lands. Then I will port to the staging tree.
PATCH 5/5 staging:lustre: Update license and copyright for kernel comm
Quoted 10 lines · James A.
Quoted 8 lines
Quoted 6 lines
- * http://www.sun.com/software/products/lustre/docs/GPLv2.pdf
- *
- * Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,
- * CA 95054 USA or visit www.sun.com if you need additional information or
- * have any questions.That text is in every files. You should kill all references.
That would be a mighty big patch.
I can take "mighty big patches" like this quite easily, please send it to me, don't mess with this "development branch of an external tree" nonsense, which I'm _REALLY_ getting tired of.
Please drop that tree and only use the in-kernel version. If that doesn't work for you, then we need to drop the in-kernel version as it's pretty obvious no one is actually using this in-kernel code.
thanks,
greg k-h