From: Sam Ravnborg <sam@ravnborg.org>
To: Stephen Williams <steveicarus@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MODULE_LICENSE("GPL") not working for me
Date: Fri, 7 Oct 2011 20:18:26 +0200 [thread overview]
Message-ID: <20111007181826.GA20210@merkur.ravnborg.org> (raw)
In-Reply-To: <CAO3ZPq2RUjW7VQQSoN-S7QDuTYdCMuDfoykHSeXwr19MTnCb_A@mail.gmail.com>
On Fri, Oct 07, 2011 at 10:20:46AM -0700, Stephen Williams wrote:
> On Thu, Oct 6, 2011 at 3:30 PM, Stephen Williams <steveicarus@gmail.com> wrote:
> > I have some large drivers for use in embedded arm systems, and
> > I want them to be GPL, because I want to use some symbols exported
> > as GPL, and also because I just wanna. But it is not working for
> > me. I've attached my Makefile. I'm building from outside the kernel
> > tree, but that should be OK. (right?) I'm using the following script to
> > actually build:
>
> More information: I can see that the vidfor.o object file, indeed
> none of my *.o files, have a .modinfo section. In other situations
> where the licens stamp works, the .modinfo section is present.
> I'm using the CodeSourcery build of the arm toolchain, and in
> the simple cases (module that is a single source file) the
> modinfo information works. Hmm...
I lost the original mail...
Could you try to post the output of make V=2 when you build your module
and the Makefile fragment again.
Sam
next prev parent reply other threads:[~2011-10-07 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 22:30 Stephen Williams
2011-10-07 9:52 ` Arnd Bergmann
2011-10-07 17:20 ` Stephen Williams
2011-10-07 18:18 ` Sam Ravnborg [this message]
2011-10-08 0:36 ` Stephen Williams
2011-10-09 8:17 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2011-10-06 22:02 Stephen Williams
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=20111007181826.GA20210@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steveicarus@gmail.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®