Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756849Ab1EZIWJ (ORCPT ); Thu, 26 May 2011 04:22:09 -0400 Received: from mx1.melware.net ([78.47.171.162]:49889 "EHLO mx1.melware.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756599Ab1EZIWF (ORCPT ); Thu, 26 May 2011 04:22:05 -0400 X-Greylist: delayed 402 seconds by postgrey-1.27 at vger.kernel.org; Thu, 26 May 2011 04:22:04 EDT Date: Thu, 26 May 2011 10:15:21 +0200 (CEST) From: Armin Schindler To: Michal Marek cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH 12/34] isdn/diva: Drop __TIME__ usage In-Reply-To: <4DDD68C3.7000004@suse.cz> Message-ID: References: <1302015561-21047-1-git-send-email-mmarek@suse.cz> <1302015561-21047-13-git-send-email-mmarek@suse.cz> <4DDD68C3.7000004@suse.cz> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) Organization: Cytronics & Melware MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1016 Lines: 28 On Wed, 25 May 2011, Michal Marek wrote: > Dne 5.4.2011 17:10, Armin Schindler napsal(a): >> On Tue, 5 Apr 2011, 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. >> >> The module can be build separately from the kernel, therefore it can have >> an own build timestamp. > > So the module timestamp and kernel timestamp vary by a couple of > minutes. But is it really a problem? It could be a lot more than minutes. But it isn't a problem. I just tried to keep the sources in sync with out-of-tree version. > I don't think so. So is there an > objection against applying this patch? No objection. Please go ahead with the patch. Thanks Armin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/