From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/5] Do not use __DATE__ and __TIME__ anymore
Date: Thu, 17 Apr 2014 15:10:22 -0400 [thread overview]
Message-ID: <2480559.UGk5Fh3QCJ@vapier> (raw)
In-Reply-To: <1397721632-18797-1-git-send-email-yamada.m@jp.panasonic.com>
On Thu 17 Apr 2014 17:00:27 Masahiro Yamada wrote:
> The aim of this series is to prohibit using __DATE__ and __TIME__.
as long as the version.h isn't impacted, this should fine. i don't think it
is as it looks like the build will generate U_BOOT_DATE and U_BOOT_TIME into a
const string by hand.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140417/d21a8ee1/attachment.pgp>
prev parent reply other threads:[~2014-04-17 19:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 8:00 [U-Boot] [PATCH 0/5] Do not use __DATE__ and __TIME__ anymore Masahiro Yamada
2014-04-17 8:00 ` [U-Boot] [PATCH 1/5] rand: do not surround function declarations by #ifdef Masahiro Yamada
2014-04-17 8:00 ` [U-Boot] [PATCH 2/5] net: rename and refactor eth_rand_ethaddr() function Masahiro Yamada
2014-04-17 8:08 ` Joe Hershberger
2014-04-17 11:09 ` Wolfgang Denk
2014-04-17 8:00 ` [U-Boot] [PATCH 3/5] blackfin: replace bfin_gen_rand_mac() with eth_random_addr() Masahiro Yamada
2014-04-17 19:07 ` Mike Frysinger
2014-04-18 9:25 ` Masahiro Yamada
2014-04-17 8:00 ` [U-Boot] [PATCH 4/5] fs: ubifs: drop __DATE__ and __TIME__ Masahiro Yamada
2014-04-17 8:00 ` [U-Boot] [PATCH 5/5] kbuild: build with -Werror=date-time if the compiler supports it Masahiro Yamada
2014-04-17 11:07 ` [U-Boot] [PATCH 0/5] Do not use __DATE__ and __TIME__ anymore Wolfgang Denk
2014-04-17 11:41 ` Masahiro Yamada
2014-04-17 14:48 ` Wolfgang Denk
2014-04-17 19:10 ` Mike Frysinger [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=2480559.UGk5Fh3QCJ@vapier \
--to=vapier@gentoo.org \
--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.