[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTikK+sYFOE4iCL7N8iZLO5bbx4K4FQ@mail.gmail.com>
Date: Tue, 5 Apr 2011 17:28:59 +0200
From: Gertjan van Wingerde <gwingerde@...il.com>
To: Michal Marek <mmarek@...e.cz>
Cc: linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
Ivo van Doorn <IvDoorn@...il.com>,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 19/34] rt2x00: Drop __TIME__ usage
On Tue, Apr 5, 2011 at 4:59 PM, Michal Marek <mmarek@...e.cz> 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.
>
> Cc: Ivo van Doorn <IvDoorn@...il.com>
> Cc: Gertjan van Wingerde <gwingerde@...il.com>
> Cc: linux-wireless@...r.kernel.org
> Cc: netdev@...r.kernel.org
> Signed-off-by: Michal Marek <mmarek@...e.cz>
Note that this timestamp is not in the kernel log, but in a special
debug file in debugfs.
However, I cannot see how a timestamp is actually useful for debugging
the driver, so
Acked-by: Gertjan van Wingerde <gwingerde@...il.com>
> ---
> drivers/net/wireless/rt2x00/rt2x00debug.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/wireless/rt2x00/rt2x00debug.c b/drivers/net/wireless/rt2x00/rt2x00debug.c
> index c92db32..66166ef 100644
> --- a/drivers/net/wireless/rt2x00/rt2x00debug.c
> +++ b/drivers/net/wireless/rt2x00/rt2x00debug.c
> @@ -568,7 +568,6 @@ static struct dentry *rt2x00debug_create_file_driver(const char *name,
> blob->data = data;
> data += sprintf(data, "driver:\t%s\n", intf->rt2x00dev->ops->name);
> data += sprintf(data, "version:\t%s\n", DRV_VERSION);
> - data += sprintf(data, "compiled:\t%s %s\n", __DATE__, __TIME__);
> blob->size = strlen(blob->data);
>
> return debugfs_create_blob(name, S_IRUSR, intf->driver_folder, blob);
> --
> 1.7.4.1
>
>
--
---
Gertjan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists