All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPDX-License-Identifier: adding a comment section?
Date: Mon, 29 Jul 2013 21:51:22 +0200	[thread overview]
Message-ID: <20130729195122.76FC23803F3@gemini.denx.de> (raw)
In-Reply-To: <51F666A4.9060406@ti.com>

Dear Tom,

In message <51F666A4.9060406@ti.com> you wrote:
>
> > drivers/net/ne2000.h drivers/net/ne2000.c 
> > drivers/net/ne2000_base.h drivers/net/ne2000_base.c
...
> I grabbed (because of the omap watchdog patch) 2.4.17, and that's (a)
> older than our ne2k driver and (b) Already a GPLv2 and not 'or later'.
>  This is, I think, GPL-2.0.

I see. Thanks for pointing out.

> > SPDX-License-Comments:
> > 
> > which could be used to mark a text section that would contain such 
> > explanations.
> > 
> > Wound this make sense, or do you have a better suggestion?
> 
> Sounds good.  In this case we would say something like "Linux Kernel
> driver and eCos driver files both used as reference".

Right.  Thanks !

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If a packet hits a pocket on a socket on a port,
And the bus is interrupted as a very last resort,
And the address of the memory makes your floppy disk abort,
Then the socket packet pocket has an error to report! - Ken Burchill?

      reply	other threads:[~2013-07-29 19:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-28 15:40 [U-Boot] SPDX-License-Identifier: adding a comment section? Wolfgang Denk
2013-07-28 18:19 ` Roger Meier
2013-07-29 12:57 ` Tom Rini
2013-07-29 19:51   ` Wolfgang Denk [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=20130729195122.76FC23803F3@gemini.denx.de \
    --to=wd@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.