All of lore.kernel.org
 help / color / mirror / Atom feed
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 12:08:31 +0100	[thread overview]
Message-ID: <5477208.ntDhW1kj3a@wuerfel> (raw)
In-Reply-To: <705062da-a84a-41ee-8905-d600ea41529c@googlegroups.com>

On Tuesday 09 February 2016 01:01:37 Bhumika Goyal wrote:
> Thank you Arnd .I am not getting any warnings with "make drivers/staging". 
> Can I know the reason for previous warnings when I used "make M" ?
> 
> 

The differences are very subtle:

make drivers/staging

   always succeeds, does nothing at all because the directory exists

make drivers/staging/

   descends into that directory to build all the files in it, but does
   not try to link the modules

make M=drivers/staging

   From the output you get, I think this must try to link the modules
   against the previously-build vmlinux file, which for some reason
   fails here. I suggested doing 'make' to rebuild everything including
   vmlinux, so it is up-to-date with your current configuration.

	Arnd


  reply	other threads:[~2016-02-09 11:08 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 ` [Outreachy kernel] " Arnd Bergmann
2016-02-09  9:01   ` Bhumika Goyal
2016-02-09 11:08     ` Arnd Bergmann [this message]
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=5477208.ntDhW1kj3a@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.