linux-kernel - Re: [PATCH v4 17/25] timekeeping:Introduce the timekeeping

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 2 Jun 2015 21:20:37 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Baolin Wang <baolin.wang@...aro.org>
cc:	arnd@...db.de, john.stultz@...aro.org, heenasirwani@...il.com,
	pang.xunlei@...aro.org, peterz@...radead.org,
	rafael.j.wysocki@...el.com, linux-kernel@...r.kernel.org,
	y2038@...ts.linaro.org
Subject: Re: [PATCH v4 17/25] timekeeping:Introduce the timekeeping_clocktai()
 function with timespec64 type

On Mon, 1 Jun 2015, Baolin Wang wrote:

> Subject: timekeeping:Introduce the timekeeping_clocktai() function with timespec64 type

You are not introducing anything new. You change the implementation.

> This patch converts the timespec type to timespec64 type for
> timekeeping_clocktai() function which is used only in the
> posix-timers.c file, that makes it ready for 2038 issue.
> 
> And remove the declaration of timekeeping_clocktai() in
> kernel/time/timekeeping.h file, cause nothing uses that
> declaration now, and it would conflict with the inline
> definition in the include/linux/timekeeping.h file.
> 
> Also introduce the clock_get64 callback pointer for the k_clock
> structure, and convert the timespec type to timespec64 type for
> the posix_get_tai() function.

Stop explaining WHAT your patches are doing. 

Thanks,

	tglx
--
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/