All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] What does (P) in /proc/modules mean?
Date: Mon, 05 Mar 2007 03:49:25 +0000	[thread overview]
Message-ID: <20070305034925.GA28478@kroah.com> (raw)
In-Reply-To: <4b4be04a0703032005j69da5ddch208f375fc8e3e12e@mail.gmail.com>

On Sun, Mar 04, 2007 at 10:30:21PM +0100, Sam Ravnborg wrote:
> On Sun, Mar 04, 2007 at 10:23:59AM -0800, Randy Dunlap wrote:
> > On Sun, 4 Mar 2007 22:19:51 +1000 Badai Aqrandista wrote:
> > 
> > > Hi,
> > > 
> > > On 3/4/07, Randy Dunlap <rdunlap@xenotime.net> wrote:
> > > > I just tested this module on 2.6.20, no license issues/problems
> > > > at all.  So what kernel version were you using and what other
> > > > modules were loaded or had been loaded?
> > > 
> > > I think I found the cause. It's the Makefile. I copied the Makefile
> > > from ldd3 and it includes this line:
> > > 
> > > CFLAGS += $(DEBFLAGS) -I$(LDDINCDIR)
> 
> ldd3 is wrong. Never ever mess around with CFLAGS. Use EXTRA_CFLAGS
> which is there for a purpose.
> Copied Greg + Jon to notice them.

Thanks for letting us know, I think that for the few examples in LDD3
that use this, we didn't realize EXTRA_CFLAGS was possible (remember,
the book is quite old now...)

If we do a new release, this will be one of those things that we change.

thanks,

greg k-h
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

      parent reply	other threads:[~2007-03-05  3:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-04  4:05 [KJ] What does (P) in /proc/modules mean? Badai Aqrandista
2007-03-04  5:31 ` Randy Dunlap
2007-03-04  5:37 ` Randy Dunlap
2007-03-04 12:19 ` Badai Aqrandista
2007-03-04 18:23 ` Randy Dunlap
2007-03-04 21:30 ` Sam Ravnborg
2007-03-05  3:49 ` Greg KH [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=20070305034925.GA28478@kroah.com \
    --to=greg@kroah.com \
    --cc=kernel-janitors@vger.kernel.org \
    /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.