From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>
Subject: Re: [PATCH v2] bcm/CmHost.c: Fix noisy compile warnings
Date: Thu, 16 Oct 2014 11:09:57 +0300 [thread overview]
Message-ID: <20141016080957.GS26918@mwanda> (raw)
In-Reply-To: <1413446382.2412.57.camel@jtkirshe-mobl>
COMPILE_TEST is just so that you can view build warnings. We would say:
depends on USB && NET && (!64BIT || COMPILE_TEST)
of
depends on USB && NET && (X86_32 || (X86 && COMPILE_TEST))
If you don't have USB or NET, you're get build errors but they don't
indicate bugs. If you build on X86_64 the warnings are real bugs.
regards,
dan carpenter
next prev parent reply other threads:[~2014-10-16 8:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 19:01 Jeff Kirsher
2014-10-15 19:55 ` Dan Carpenter
2014-10-15 20:26 ` Jeff Kirsher
2014-10-16 7:52 ` Dan Carpenter
2014-10-16 7:59 ` Jeff Kirsher
2014-10-16 8:09 ` Dan Carpenter [this message]
2014-10-15 22:59 ` Jeff Kirsher
2014-10-16 8:13 ` Greg KH
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=20141016080957.GS26918@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=fabio.estevam@freescale.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.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
Powered by JetHome