From: Jiri Slaby <jslaby@suse.cz>
To: dedekind1@gmail.com
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, jirislaby@gmail.com,
linux-kernel@vger.kernel.org, Jiri Slaby <jslaby@suse.cz>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-mtd@lists.infradead.org, Michal Marek <mmarek@suse.cz>
Subject: [PATCH] ubifs: remove __DATE__ and __TIME__
Date: Thu, 9 Aug 2012 19:43:14 +0200 [thread overview]
Message-ID: <1344534194-16321-1-git-send-email-jslaby@suse.cz> (raw)
This tag is useless and it breaks automatic builds. It causes rebuilds
for packages that depend on kernel for no real reason.
Further, quoting Michal, who removed most of the users already:
The kernel already prints its build timestamp during boot, no need to
repeat it in random drivers and produce different object files each
time.
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Cc: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: linux-mtd@lists.infradead.org
Cc: Michal Marek <mmarek@suse.cz>
---
fs/ubifs/super.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/ubifs/super.c b/fs/ubifs/super.c
index e354832..67af316 100644
--- a/fs/ubifs/super.c
+++ b/fs/ubifs/super.c
@@ -1431,7 +1431,6 @@ static int mount_ubifs(struct ubifs_info *c)
ubifs_msg("reserved for root: %llu bytes (%llu KiB)",
c->report_rp_size, c->report_rp_size >> 10);
- dbg_msg("compiled on: " __DATE__ " at " __TIME__);
dbg_msg("min. I/O unit size: %d bytes", c->min_io_size);
dbg_msg("max. write size: %d bytes", c->max_write_size);
dbg_msg("LEB size: %d bytes (%d KiB)",
--
1.7.10.4
next reply other threads:[~2012-08-09 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 17:43 Jiri Slaby [this message]
2012-08-24 11:54 ` [PATCH] ubifs: remove __DATE__ and __TIME__ Artem Bityutskiy
2012-08-24 11:51 ` Jiri Slaby
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=1344534194-16321-1-git-send-email-jslaby@suse.cz \
--to=jslaby@suse.cz \
--cc=adrian.hunter@intel.com \
--cc=dedekind1@gmail.com \
--cc=jirislaby@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mmarek@suse.cz \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).