public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] "All rights reserved" in drivers/mtd/nand/nand_util.c
Date: Fri, 11 Sep 2009 17:10:36 -0500	[thread overview]
Message-ID: <4AAACADC.7090502@freescale.com> (raw)
In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D927088F6@dlee01.ent.ti.com>

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

      reply	other threads:[~2009-09-11 22:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 21:58 [U-Boot] "All rights reserved" in drivers/mtd/nand/nand_util.c Scott Wood
2009-09-08 14:10 ` Paulraj, Sandeep
2009-09-11 18:32   ` Scott Wood
2009-09-11 21:48     ` Paulraj, Sandeep
2009-09-11 22:10       ` Scott Wood [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AAACADC.7090502@freescale.com \
    --to=scottwood@freescale.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox