linux-ext4 - Re: [GIT PULL] [PATCH v4 00/26] Delete CURRENT_TIME and CURRENT_TIME

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 15 Aug 2016 18:23:12 +0200
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Deepa Dinamani <deepa.kernel@...il.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	arnd@...db.de, tglx@...utronix.de, torvalds@...ux-foundation.org,
	tytso@....edu, viro@...iv.linux.org.uk, y2038@...ts.linaro.org,
	adilger.kernel@...ger.ca, adrian.hunter@...el.com,
	anna.schumaker@...app.com, buchino@...co.com,
	ceph-devel@...r.kernel.org, clm@...com, cm224.lee@...sung.com,
	dedekind1@...il.com, dsterba@...e.com, dushistov@...l.ru,
	elder@...nel.org, eparis@...hat.com, hiralpat@...co.com,
	idryomov@...il.com, jack@...e.com, jaegeuk@...nel.org,
	jbacik@...com, jejb@...ux.vnet.ibm.com,
	jfs-discussion@...ts.sourceforge.net, jlbec@...lplan.org,
	john.stultz@...aro.org, linux-audit@...hat.com,
	linux-btrfs@...r.kernel.org, linux-ext4@...r.kernel.org,
	linux-f2fs-devel@...ts.sourceforge.net,
	linux-mtd@...ts.infradead.org, linux-nfs@...r.kernel.org,
	linux-scsi@...r.kernel.org, lustre-devel@...ts.lustre.org,
	martin.petersen@...cle.com, mfasheh@...e.com,
	ocfs2-devel@....oracle.com, paul@...l-moore.com, sage@...hat.com,
	sfrench@...ba.org, shaggy@...nel.org, sramars@...co.com,
	trond.myklebust@...marydata.com, zyan@...hat.com
Subject: Re: [GIT PULL] [PATCH v4 00/26] Delete CURRENT_TIME and
 CURRENT_TIME_SEC macros

On Sat, Aug 13, 2016 at 03:48:12PM -0700, Deepa Dinamani wrote:
> The series is aimed at getting rid of CURRENT_TIME and CURRENT_TIME_SEC macros.
> The macros are not y2038 safe. There is no plan to transition them into being
> y2038 safe.
> ktime_get_* api's can be used in their place. And, these are y2038 safe.

Who are you execting to pull this huge patch series?

Why not just introduce the new api call, wait for that to be merged, and
then push the individual patches through the different subsystems?
After half of those get ignored, then provide a single set of patches
that can go through Andrew or my trees.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html