public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: <libc-alpha@sourceware.org>, Florian Weimer <fweimer@redhat.com>,
	Szabolcs Nagy <szabolcs.nagy@arm.com>,
	"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH v7 0/1] RFC: Add <sys/tagged-address.h>
Date: Fri, 24 Sep 2021 18:08:32 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2109241803540.4038824@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20210924165338.2326917-1-hjl.tools@gmail.com>

On Fri, 24 Sep 2021, H.J. Lu via Libc-alpha wrote:

> Changes in v7:
> 
> 1. Move set_translated_address_mask to libc_nonshared.a.

Code in *_nonshared.a or crt*.o should include the LGPL exception wording:

   In addition to the permissions in the GNU Lesser General Public
   License, the Free Software Foundation gives you unlimited
   permission to link the compiled version of this file with other
   programs, and to distribute those programs without any restriction
   coming from the use of this file. (The GNU Lesser General Public
   License restrictions do apply in other respects; for example, they
   cover modification of the file, and distribution when not linked
   into another program.)

   Note that people who make modified versions of this file are not
   obligated to grant this special exception for their modified
   versions; it is their choice whether to do so. The GNU Lesser
   General Public License gives permission to release a modified
   version without this exception; this exception also makes it
   possible to release a modified version which carries forward this
   exception.

(The point being that people linking with glibc should be able to meet 
their LGPL obligations by linking dynamically, without also needing to 
provide a way to relink with modified versions of the *_nonshared.a code.)

Presumably when we get DCO contributions to such files we also need to 
adjust the exception wording accordingly regarding who gives the above 
permission.

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2021-09-24 18:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24 16:53 H.J. Lu
2021-09-24 16:53 ` [PATCH v7 1/1] <sys/tagged-address.h>: An API for tagged address H.J. Lu
2021-10-04 13:58   ` H.J. Lu
2021-09-24 18:08 ` Joseph Myers [this message]
2021-09-24 18:39   ` [PATCH v7 0/1] RFC: Add <sys/tagged-address.h> H.J. Lu
2021-09-24 18:53     ` Joseph Myers
2021-09-24 18:58       ` H.J. Lu
2021-09-24 19:34         ` Joseph Myers
2021-09-24 22:00           ` H.J. Lu
2021-11-15 13:34 ` Florian Weimer
2021-11-15 13:49   ` H.J. Lu

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=alpine.DEB.2.22.394.2109241803540.4038824@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=libc-alpha@sourceware.org \
    --cc=szabolcs.nagy@arm.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).