All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH][RFC] Update U-Boot's build timestamp on every	compile
Date: Fri, 17 Oct 2008 17:55:02 -0500	[thread overview]
Message-ID: <1224284102.18428.309.camel@localhost.localdomain> (raw)
In-Reply-To: <1224283881-24626-1-git-send-email-ptyser@xes-inc.com>

On Fri, 2008-10-17 at 17:51 -0500, Peter Tyser wrote:
> Use the GNU 'date' command to auto-generate a new U-Boot
> timestamp on every compile.
> 
> Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
> ---
> I noticed that the build time of U-Boot was not updated on every
> compile which occassionally threw me for a loop as to whether
> a new U-Boot binary was programmed, etc.  This patch updates
> a U_BOOT_DATE define on every compile which can then be used
> in place of the multiple "__DATE__ - __TIME__" preprocessor
> macros that are currently used.
> 
> This also ensures the timestamp will be the same for a board
> if it uses __TIME__ in multiple files.
> 
> Let me know if this would be accepted into mainline and I'll
> generate a formal patch updating all __DATE__/__TIME__
> references.

Instead of U_BOOT_DATE, we could use U_BOOT_DATE (month, day, year) and
U_BOOT_TIME (24 hour time) to provide more granularity if others want
that level of control.

Peter

  reply	other threads:[~2008-10-17 22:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 22:51 [U-Boot] [PATCH][RFC] Update U-Boot's build timestamp on every compile Peter Tyser
2008-10-17 22:55 ` Peter Tyser [this message]
2008-10-21  0:59 ` Kim Phillips
2008-10-21  2:02   ` Peter Tyser
2008-10-21  7:04     ` Wolfgang Denk
2008-10-21 14:40       ` Peter Tyser
2008-10-21 14:51         ` Jerry Van Baren
2008-10-21 15:02           ` Wolfgang Denk
2008-10-21 15:17             ` Peter Tyser
2008-10-21 14:57         ` Stefan Roese
2008-10-21 15:04           ` Wolfgang Denk
2008-10-21 14:59         ` Wolfgang Denk
2008-10-21 18:52           ` Andy Fleming
2008-10-21 19:03             ` Peter Tyser

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=1224284102.18428.309.camel@localhost.localdomain \
    --to=ptyser@xes-inc.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.