All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: James Hogan <james.hogan@imgtec.com>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
	Mike Frysinger <vapier@gentoo.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [PATCH 1/1] depmod: pass -P $CONFIG_SYMBOL_PREFIX
Date: Thu, 31 Jan 2013 11:37:27 +0100	[thread overview]
Message-ID: <510A4967.5070009@suse.cz> (raw)
In-Reply-To: <1359625303-11842-1-git-send-email-james.hogan@imgtec.com>

On 31.1.2013 10:41, James Hogan wrote:
> On architectures which have symbol prefixes, depmod emits lots of false
> warnings like this:
> 
> WARNING: $module.ko needs unknown symbol $symbol
> 
> This is because depmod isn't being passed the -P <symbol_prefix>
> arguments to specify the symbol prefix to ignore. This option is
> included since the 3.13 release of module-init-tools.
> 
> Update scripts/depmod.sh to take extra arguments which are passed
> through directly to depmod, and update the main Makefile to pass
> -P $(CONFIG_SYMBOL_PREFIX to scripts/depmod.sh, but only if
> CONFIG_SYMBOL_PREFIX is set and non-empty.

OK.


> scripts/depmod.sh also drops the -P arguments if depmod --version
> reports module-init-tools with a version number < 3.13.

You can replace the test with a simple

"$DEPMOD" -P _ --help 2>/dev/null >/dev/null

Michal

  reply	other threads:[~2013-01-31 10:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31  9:41 [PATCH 1/1] depmod: pass -P $CONFIG_SYMBOL_PREFIX James Hogan
2013-01-31  9:41 ` James Hogan
2013-01-31 10:37 ` Michal Marek [this message]
2013-01-31 10:50   ` James Hogan
2013-01-31 10:50     ` James Hogan
2013-01-31 11:11     ` Michal Marek
2013-02-03  6:17 ` Mike Frysinger
2013-02-05 10:33   ` James Hogan
2013-02-05 10:33     ` James Hogan
2013-02-05 23:18     ` Mike Frysinger

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=510A4967.5070009@suse.cz \
    --to=mmarek@suse.cz \
    --cc=james.hogan@imgtec.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier@gentoo.org \
    --cc=ysato@users.sourceforge.jp \
    /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.