diff options
author | Kinsey Moore <kinsey.moore@oarcorp.com> | 2022-04-14 12:32:14 -0500 |
---|---|---|
committer | Vijay Kumar Banerjee <vijay@rtems.org> | 2022-06-01 21:23:41 -0600 |
commit | 0b367b535083535896607710bbe8a46f8f6e0c74 (patch) | |
tree | ab3a45915a3a3400365c9842a2dd9a1647b510dc /COPYING.lwip | |
parent | 5ad5279ca879c3cf0faf3141c84067bdf232c3a2 (diff) |
lwip: Split sources into origin directories
Moving forward, each origin directory should have its own top-level
COPYING.origin file to describe its license as well as a ORIGIN.origin
file to describe where the code is sourced from.
Diffstat (limited to 'COPYING.lwip')
-rw-r--r-- | COPYING.lwip | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/COPYING.lwip b/COPYING.lwip new file mode 100644 index 0000000..90465f5 --- /dev/null +++ b/COPYING.lwip @@ -0,0 +1,25 @@ +Copyright (c) 2001, 2002 Swedish Institute of Computer Science. +All rights reserved. + +Redistribution and use in source and binary forms, with or without modification, +are permitted provided that the following conditions are met: + +1. Redistributions of source code must retain the above copyright notice, + this list of conditions and the following disclaimer. +2. Redistributions in binary form must reproduce the above copyright notice, + this list of conditions and the following disclaimer in the documentation + and/or other materials provided with the distribution. +3. The name of the author may not be used to endorse or promote products + derived from this software without specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED +WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT +SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, +EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT +OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING +IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY +OF SUCH DAMAGE. + |