mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Holger Schurig <holgerschurig@gmail.com>
To: barebox@lists.infradead.org
Subject: [PATCH 0/3] sandbox: prepare for static checkers
Date: Tue, 22 Jul 2014 09:57:19 +0200	[thread overview]
Message-ID: <1406015842-20754-1-git-send-email-holgerschurig@gmail.de> (raw)

From: Holger Schurig <holgerschurig@gmail.com>

I want to use different compilers and static checkers (e.g. clang's
scan-build) on Barebox.  As a preparatory step I want to maximize code
coverage in an non-crosscompilation environment.

This patch set prepares the tree so that "make ARCH=sandbox allyesconfig"
followed by "make ARCH=sandbox" works and compiles warning free (at least
with Debian's gcc-4.6).

Holger Schurig (3):
  sandbox: disable bareboxcrc32 in sandbox mode
  sandbox: allow "make ARCH=sandbox allyesconfig"
  sandbox: work around missing of_add_memory_bank()

 arch/arm/Kconfig                 |  2 ++
 arch/nios2/Kconfig               |  1 +
 arch/openrisc/Kconfig            |  1 +
 arch/ppc/Kconfig                 |  1 +
 common/Kconfig                   | 17 +++++++++++++++++
 drivers/ata/Kconfig              |  1 +
 drivers/input/Kconfig            |  2 +-
 drivers/net/Kconfig              |  4 ++++
 drivers/of/base.c                |  2 ++
 drivers/regulator/Kconfig        |  1 +
 drivers/usb/host/Kconfig         |  1 +
 drivers/video/imx-ipu-v3/Kconfig |  1 +
 12 files changed, 33 insertions(+), 1 deletion(-)

-- 
1.8.5.2


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2014-07-22  7:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22  7:57 Holger Schurig [this message]
2014-07-22 19:36 ` Sascha Hauer

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=1406015842-20754-1-git-send-email-holgerschurig@gmail.de \
    --to=holgerschurig@gmail.com \
    --cc=barebox@lists.infradead.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