All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] arm: printf() is not available in some SPL configurations
Date: Tue, 22 Nov 2011 14:20:33 -0600	[thread overview]
Message-ID: <4ECC0411.2090100@freescale.com> (raw)
In-Reply-To: <4ECB622A.3070408@gmail.com>

On 11/22/2011 02:49 AM, Andreas Bie?mann wrote:
> Well, you can do it that way but I guess there are several places where
> printf() will be needed by some drivers in SPL. Therefore I think it is
> better to provide printf() for SPL than to ifdef out all the printf's.
> 
> So how about providing an empty
> 
> #if !defined(CONFIG_SPL_BUILD) || defined(CONFIG_SPL_LIBCOMMON_SUPPORT)
> #define printf(x)
> #endif
> 
> somewhere in the SPL code?

Use an inline function instead so the arguments are consumed and it
doesn't cause unused-variable warnings.

-Scott

      parent reply	other threads:[~2011-11-22 20:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  8:26 [U-Boot] [PATCH v3] arm: printf() is not available in some SPL configurations Christian Riesch
2011-11-22  8:49 ` Andreas Bießmann
2011-11-22  9:08   ` Christian Riesch
2011-11-22 20:20   ` Scott Wood [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=4ECC0411.2090100@freescale.com \
    --to=scottwood@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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.