mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Ram Pai <linuxram@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] crc generation fix for EXPORT_SYMBOL_GPL
Date: Mon, 06 Feb 2006 14:42:36 +0100	[thread overview]
Message-ID: <1139233357.3131.66.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1139203471.4641.41.camel@localhost>

On Sun, 2006-02-05 at 21:24 -0800, Ram Pai wrote:
> On Sat, 2006-02-04 at 21:31 +0100, Arjan van de Ven wrote:
> > On Wed, 2006-02-01 at 20:15 -0800, Ram Pai wrote:
> > > Currently genksym does not take into account the GPLness of the exported
> > > symbol while generating the crc for the exported symbol. Any symbol
> > > changes from EXPORT_SYMBOL to EXPORT_SYMBOL_GPL would not reflect in the
> > > Module.symvers file.  This patch fixes that problem.
> > 
> > and this is a problem.. why?
> 
> Tools that depend on Module.symvers wont be able to detect the change in
> GPLness of the exported symbols.

and that is relevant.. why?


> Eventually we want to generate a tool that can report API changes across
> kernel releases and put it in some friendly(docbook) format.

but a _GPL change isn't an API change though... either a module is legal
or it isn't. _GPL doesn't matter there...




  reply	other threads:[~2006-02-06 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02  4:15 Ram Pai
2006-02-04 20:31 ` Arjan van de Ven
2006-02-06  5:24   ` Ram Pai
2006-02-06 13:42     ` Arjan van de Ven [this message]
2006-02-06 14:09     ` Arjan van de Ven
2006-02-07  6:49       ` Ram Pai

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=1139233357.3131.66.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxram@us.ibm.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

all inboxes | Powered by JetHome®