From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Date: Fri, 11 Sep 2009 17:10:36 -0500 Subject: [U-Boot] "All rights reserved" in drivers/mtd/nand/nand_util.c In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D927088F6@dlee01.ent.ti.com> References: <4A9EEA68.2080203@freescale.com> <0554BEF07D437848AF01B9C9B5F0BC5D924755FB@dlee01.ent.ti.com> <4AAA97C5.1090409@freescale.com> <0554BEF07D437848AF01B9C9B5F0BC5D927088F6@dlee01.ent.ti.com> Message-ID: <4AAACADC.7090502@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Paulraj, Sandeep wrote: >> Paulraj, Sandeep wrote: >>> I don't think we received a patch. >>> >>> How are we moving forward as this is required for the NAND driver to >> work. >> >> I guess we start rewriting it > 1) What about all the necessary hooks to other parts of the NAND driver. I don't follow... > 2) What about all the very valid commits and changes to this file in the last so many years. Any identifiable sections that are not derived from the original commit can presumably be kept, though determining the proper license status of contributed code without an explicit copyright statement[1] is fuzzy enough in the absence of a bad license being present on the file being contributed to. [1] I don't trust signed-off-by; I imagine many use it without ever having read what it was supposed to mean in a different project, especially when git automates it with a simple flag. That seems more likely to be a practical problem than "all rights reserved"... > -- and/or try to find any upstream code >> Guido may >> have based it on. > > You can associate parts of this file from U-boot 1.2.0(maybe even an earlier > version) with the reference code mentioned in the file. The code referred to > is from mtd-utils. I could not find any similarities between the current mtd > utils code and the current sate of the file obviously due to point 2) I made > above > Frankly I am at a loss to figure out how somebody could rewrite a file and not use most of the code. > > The company still exists! Maybe we write an e-mail to them! Calm down... I did write an e-mail to the person that submitted the code (it's the thread we're replying to) and claimed that copyright. I assumed that would be the person with the best knowledge of whom to contact in that company. If you want to find the right person to contact without his help, go ahead -- but that seems like more work to me than rewriting a relatively small chunk of code. Especially since, as you note, big chunks of the file are not from that original commit, and what was in the original commit may have come from another upstream project. -Scott