All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Arnd Bergmann <arnd@arndb.de>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] Doubt regarding build warnings
Date: Tue, 9 Feb 2016 16:55:59 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.10.1602091655340.2578@hadrien> (raw)
In-Reply-To: <2414518.udrIPO2x22@wuerfel>

On Tue, 9 Feb 2016, Arnd Bergmann wrote:

> On Tuesday 09 February 2016 16:49:31 Julia Lawall wrote:
> > On Tue, 9 Feb 2016, Arnd Bergmann wrote:
> >
> > > On Tuesday 09 February 2016 16:18:55 Julia Lawall wrote:
> > > >     make M=drivers/staging: This seems to try to link the modules in a
> > > > previously build vmlinux file.
> > > >
> > > > Make path/ could be a reasonable choice for a localized change within a
> > > > single driver, or for a change localized to drivers staging. In any case,
> > > > as a minimum always check that compilation produces a .o file for every
> > > > file that your patch changes. If there is no .o file, you have not
> > > > compiled the file, and you need to look for other compiler options.
> > >
> > > Ok, sounds good. I've added a little bit more detail now:
> > >
> > > http://kernelnewbies.org/FirstKernelPatch?action=diff&rev2=25&rev1=24
> >
> > Thanks.  What is -sj2?
> >
> >
>
> -s is 'silent', -j2 is used to build on two threads in parallel rather than
> one. On second thought, I'll remove those again, as this prevents you
> from seeing which files get built.

-j2 could be left, but one could also infer it from the rest.

thanks,
julia


  reply	other threads:[~2016-02-09 15:56 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
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 [this message]
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=alpine.DEB.2.10.1602091655340.2578@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=arnd@arndb.de \
    --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.