public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/7] kconfig: move CONFIG_SYS_HZ to lib/Kconfig
Date: Fri, 26 Sep 2014 12:38:51 +0200	[thread overview]
Message-ID: <201409261238.52006.marex@denx.de> (raw)
In-Reply-To: <1411727024-19153-2-git-send-email-yamada.m@jp.panasonic.com>

On Friday, September 26, 2014 at 12:23:22 PM, Masahiro Yamada wrote:
> CONFIG_SYS_HZ is always defined as 1000 in config_fallbacks.h
> (but some boards still have redundant definitions).
> 
> This commit moves the definition and the document in README to
> Kconfig.  Since lib/Kconfig can assure that CONFIG_SYS_HZ is 1000,
> the sanity check in lib/time.c can be removed.
> 
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>

Nice,

Reviewed-by: Marek Vasut <marex@denx.de>

Best regards,
Marek Vasut

  reply	other threads:[~2014-09-26 10:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 10:23 [U-Boot] [PATCH 0/7] kconfig: Move CONFIG_SYS_HZ and CONFIG_USE_PRIVATE_LIBGCC, bug fixes Masahiro Yamada
2014-09-26 10:23 ` [U-Boot] [PATCH 1/7] kconfig: move CONFIG_SYS_HZ to lib/Kconfig Masahiro Yamada
2014-09-26 10:38   ` Marek Vasut [this message]
2014-09-26 10:23 ` [U-Boot] [PATCH 2/7] x86: set CONFIG_USE_PRIVATE_LIBGCC to y Masahiro Yamada
2014-10-06 20:14   ` Simon Glass
2014-09-26 10:23 ` [U-Boot] [PATCH 3/7] kbuild: drop CONFIG_USE_PRIVATE_LIBGCC=<path/to/libgcc> syntax Masahiro Yamada
2014-10-06 20:15   ` Simon Glass
2014-09-26 10:23 ` [U-Boot] [PATCH 4/7] kconfig: move CONFIG_USE_PRIVATE_LIBGCC to Kconfig Masahiro Yamada
2014-10-06 20:15   ` Simon Glass
2014-09-26 10:23 ` [U-Boot] [PATCH 5/7] kbuild: fix a bug of the u-boot-spl link rule Masahiro Yamada
2014-09-26 10:23 ` [U-Boot] [PATCH 6/7] kconfig: invoke silentoldconfig if spl, tpl/.config is updated Masahiro Yamada
2014-09-26 10:23 ` [U-Boot] [PATCH 7/7] mips: enable CONFIG_USE_PRIVATE_LIBGCC by default Masahiro Yamada
2014-10-08 10:16   ` Daniel Schwierzeck

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=201409261238.52006.marex@denx.de \
    --to=marex@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox