From: Borislav Petkov <bp@alien8.de>
To: "Ksenija Stanojević" <ksenija.stanojevic@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: include: asm: Fix build warning
Date: Tue, 29 Sep 2015 19:31:09 +0200 [thread overview]
Message-ID: <20150929173109.GD3534@pd.tnic> (raw)
In-Reply-To: <CAL7P5jKNdL9BADKKLNk6td+YoQmcaq4vc2kfvJpiLLqN0DZ72w@mail.gmail.com>
On Tue, Sep 29, 2015 at 07:19:32PM +0200, Ksenija Stanojević wrote:
> On Tue, Sep 29, 2015 at 7:16 PM, Borislav Petkov <bp@alien8.de> wrote:
> > On Tue, Sep 29, 2015 at 07:12:07PM +0200, Ksenija Stanojević wrote:
> >> when building with:
> >> make drivers/staging/oplc_dcon/olpc_dcon.o
> >> I get this warnings.
> >
> > Yeah, you can't pick out single files from the source tree and try to
> > build them and expect that to always work. That olpc_dcon think depends
> > on CONFIG_OLPC so if you go enable it in Kconfig, you would have to have
> > enabled CONFIG_OLPC first.
> >
> Ok, thanks!
Sure, no probs.
Btw, if you really want to try to fix some bugs, you could try to build
the kernel with
make -j<number-of-cores-on-your-machine> W=n 2>build-warnings.log
where n is 1, 2 or 3 (or any subset of those) and try to analyze them.
Look at the output in build-warnings.log and try to understand why the
compiler is complaining and whether it makes sense.
Some of them might be worth fixing. Most of them are bogus and/or fixing
them would require just too much code changes for no real gain but some
of the warnings do make sense.
Also, you could do
make allmodconfig
before that so that you can build *everything* and catch all warnings.
HTH.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
prev parent reply other threads:[~2015-09-29 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 16:25 [PATCH] x86: include: asm: Fix build warning Ksenija Stanojevic
2015-09-29 17:06 ` Borislav Petkov
2015-09-29 17:08 ` H. Peter Anvin
2015-09-29 17:12 ` Ksenija Stanojević
2015-09-29 17:16 ` Borislav Petkov
2015-09-29 17:19 ` Ksenija Stanojević
2015-09-29 17:31 ` Borislav Petkov [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=20150929173109.GD3534@pd.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=ksenija.stanojevic@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox