| Message ID | 1302015561-21047-26-git-send-email-mmarek@suse.cz (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Tue, Apr 05, 2011 at 04:59:12PM +0200, Michal Marek wrote: > The kernel already prints its build timestamp during boot, no need to > repeat it in random drivers and produce different object files each > time. What about drivers built as modules, which may be compiled at a different time than the rest of the kernel? Matt
On Tue, Apr 05, 2011 at 10:50:10AM -0700, Matthew Dharm wrote: > On Tue, Apr 05, 2011 at 04:59:12PM +0200, Michal Marek wrote: > > The kernel already prints its build timestamp during boot, no need to > > repeat it in random drivers and produce different object files each > > time. > > What about drivers built as modules, which may be compiled at a different > time than the rest of the kernel? We don't care :) thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/drivers/usb/misc/ftdi-elan.c b/drivers/usb/misc/ftdi-elan.c index 7839c98..b16bd3c 100644 --- a/drivers/usb/misc/ftdi-elan.c +++ b/drivers/usb/misc/ftdi-elan.c @@ -2889,8 +2889,7 @@ static struct usb_driver ftdi_elan_driver = { static int __init ftdi_elan_init(void) { int result; - printk(KERN_INFO "driver %s built at %s on %s\n", ftdi_elan_driver.name, - __TIME__, __DATE__); + printk(KERN_INFO "driver %s\n", ftdi_elan_driver.name); mutex_init(&ftdi_module_lock); INIT_LIST_HEAD(&ftdi_static_list); status_queue = create_singlethread_workqueue("ftdi-status-control");
The kernel already prints its build timestamp during boot, no need to repeat it in random drivers and produce different object files each time. Cc: Tony Olech <tony.olech@elandigitalsystems.com> Cc: linux-usb@vger.kernel.org Signed-off-by: Michal Marek <mmarek@suse.cz> --- drivers/usb/misc/ftdi-elan.c | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-)