All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 1/2] Move #ifdef(CONFIG_DISPLAY_CPUINFO) from caller to callee
Date: Wed, 19 Feb 2014 16:10:09 -0500	[thread overview]
Message-ID: <20140219211009.GK19081@bill-the-cat> (raw)
In-Reply-To: <1392283827-4710-2-git-send-email-yamada.m@jp.panasonic.com>

On Thu, Feb 13, 2014 at 06:30:26PM +0900, Masahiro Yamada wrote:

> - When CONFIG_DISPLAY_CPUINFO is not enabled,
>    print_cpuinfo() should be defined as an empty function
>    in a header, include/common.h
> 
>  - Remove #ifdef CONFIG_DISPLAY_CPUINFO .. #endif
>    from caller, common/board_f.c and arch/arm/lib/board.c
> 
>  - Remove redundant prototypes in arch/arm/lib/board.c,
>    arch/arm/include/asm/arch-am33x/sys_proto.h and
>    board/nokia/rx51/rx51.h, keeping the one in include/common.h
> 
>  - Add #ifdef CONFIG_DISPLAY_CPUINFO to the func definition
>    where it is missing
> 
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140219/71e5370b/attachment.pgp>

  reply	other threads:[~2014-02-19 21:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13  9:30 [U-Boot] [PATCH 0/2] Coding style to avoid #ifdef everywhere Masahiro Yamada
2014-02-13  9:30 ` [U-Boot] [PATCH 1/2] Move #ifdef(CONFIG_DISPLAY_CPUINFO) from caller to callee Masahiro Yamada
2014-02-19 21:10   ` Tom Rini [this message]
2014-02-13  9:30 ` [U-Boot] [PATCH 2/2] Move CONFIG_DISPLAY_CPUINFO to Makefile Masahiro Yamada
2014-02-19 21:10   ` [U-Boot] [U-Boot,2/2] " Tom Rini

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=20140219211009.GK19081@bill-the-cat \
    --to=trini@ti.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.