From: Arnd Bergmann <arnd@arndb.de>
To: outreachy-kernel@googlegroups.com
Cc: Bhumika Goyal <bhumirks@gmail.com>
Subject: Re: [Outreachy kernel] Doubt regarding build warnings
Date: Tue, 09 Feb 2016 09:49:44 +0100 [thread overview]
Message-ID: <6075631.lJNnAgFSZy@wuerfel> (raw)
In-Reply-To: <ba8ae97e-c7c5-4383-bffc-a5eac3003e1d@googlegroups.com>
On Monday 08 February 2016 20:06:15 Bhumika Goyal wrote:
> I got these warning today while building the kernel. I already got some
> patches accepted but was not not getting any such warnings before.
> What can be the reason and how to fix? I used make M=drivers/staging for
> the build.
> The warnings are like:
>
> WARNING: "__cpu_online_mask"
> [drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko] undefined!
> WARNING: "__put_page" [drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko]
> undefined!
> WARNING: "__put_page" [drivers/staging/lustre/lustre/obdecho/obdecho.ko]
> undefined!
> WARNING: "__cpu_possible_mask"
> [drivers/staging/lustre/lustre/obdclass/obdclass.ko] undefined!
> WARNING: "__page_mapcount" [drivers/staging/lustre/lustre/llite/lustre.ko]
> undefined!
> WARNING: "__put_page" [drivers/staging/lustre/lustre/llite/lustre.ko]
> undefined!
> WARNING: "__cpu_possible_mask"
> [drivers/staging/lustre/lustre/libcfs/libcfs.ko] undefined!
> WARNING: "__cpu_online_mask"
> [drivers/staging/lustre/lustre/libcfs/libcfs.ko] undefined!
>
See if you get the same warnings when you do a whole kernel build, without the
"M=drivers/staging". I personally prefer "make drivers/staging/" instead of
"make M=drivers/staging", which has slightly different behavior.
Arnd
next prev parent reply other threads:[~2016-02-09 8:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 4:06 Doubt regarding build warnings Bhumika Goyal
2016-02-09 8:49 ` Arnd Bergmann [this message]
2016-02-09 9:01 ` [Outreachy kernel] " Bhumika Goyal
2016-02-09 11:08 ` Arnd Bergmann
2016-02-09 11:09 ` Julia Lawall
2016-02-09 14:38 ` Arnd Bergmann
2016-02-09 15:18 ` Julia Lawall
2016-02-09 15:46 ` Arnd Bergmann
2016-02-09 15:49 ` Julia Lawall
2016-02-09 15:54 ` Arnd Bergmann
2016-02-09 15:55 ` Julia Lawall
2016-02-09 15:57 ` Daniel Baluta
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=6075631.lJNnAgFSZy@wuerfel \
--to=arnd@arndb.de \
--cc=bhumirks@gmail.com \
--cc=outreachy-kernel@googlegroups.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 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.