linux-kernel - Re: [PATCH v3 1/2] time: Add the common weak version of update_persistent

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:	Wed, 29 Jul 2015 15:05:30 -0700
From:	John Stultz <john.stultz@...aro.org>
To:	Xunlei Pang <xlpang@....com>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	David Howells <dhowells@...hat.com>,
	Koichi Yasutake <yasutake.koichi@...panasonic.com>,
	linux-am33-list@...hat.com, Xunlei Pang <pang.xunlei@...aro.org>,
	Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v3 1/2] time: Add the common weak version of update_persistent_clock()

On Sun, Jul 26, 2015 at 3:45 AM, Xunlei Pang <xlpang@....com> wrote:
> From: Xunlei Pang <pang.xunlei@...aro.org>
>
> The weak update_persistent_clock64() calls update_persistent_clock(),
> if the architecture defines an update_persistent_clock64() to replace
> and remove its update_persistent_clock() version, when building the
> kernel the linker will throw an undefined symbol error, that is, any
> arch that switches to update_persistent_clock64() will have this issue.
>
> To solve the issue, we add the common weak update_persistent_clock().

So I'm ok with taking this patch.  I'm also ok with taking the
dependent MN10300 patch if I can get acks from maintainers.

Or if the MN10300 maintainers would prefer, they can take both patches w/ my:
   Acked-by: John Stultz <john.stultz@...aro.org>

thanks
-john
--
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/