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]

Message-ID: <20160816185320.GB6513@kroah.com>
Date:	Tue, 16 Aug 2016 20:53:20 +0200
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Deepa Dinamani <deepa.kernel@...il.com>
Cc:	Linux FS-devel Mailing List <linux-fsdevel@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Arnd Bergmann <arnd@...db.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Theodore Ts'o <tytso@....edu>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	y2038 Mailman List <y2038@...ts.linaro.org>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	Adrian Hunter <adrian.hunter@...el.com>,
	Anna Schumaker <anna.schumaker@...app.com>,
	Brian Uchino <buchino@...co.com>,
	ceph-devel <ceph-devel@...r.kernel.org>,
	Chris Mason <clm@...com>, Changman Lee <cm224.lee@...sung.com>,
	Artem Bityutskiy <dedekind1@...il.com>,
	David Sterba <dsterba@...e.com>,
	Evgeniy Dushistov <dushistov@...l.ru>,
	Alex Elder <elder@...nel.org>, Eric Paris <eparis@...hat.com>,
	Hiral Patel <hiralpat@...co.com>,
	Ilya Dryomov <idryomov@...il.com>, Jan Kara <jack@...e.com>,
	Jaegeuk Kim <jaegeuk@...nel.org>, Josef Bacik <jbacik@...com>,
	"James E.J. Bottomley" <jejb@...ux.vnet.ibm.com>,
	jfs-discussion@...ts.sourceforge.net,
	Joel Becker <jlbec@...lplan.org>,
	John Stultz <john.stultz@...aro.org>, linux-audit@...hat.com,
	linux-btrfs <linux-btrfs@...r.kernel.org>,
	linux-ext4@...r.kernel.org,
	"Linux F2FS DEV, Mailing List" 
	<linux-f2fs-devel@...ts.sourceforge.net>,
	linux-mtd <linux-mtd@...ts.infradead.org>,
	Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
	Linux SCSI List <linux-scsi@...r.kernel.org>,
	lustre-devel@...ts.lustre.org,
	"Martin K. Petersen" <martin.petersen@...cle.com>,
	Mark Fasheh <mfasheh@...e.com>, ocfs2-devel@....oracle.com,
	Paul Moore <paul@...l-moore.com>, Sage Weil <sage@...hat.com>,
	Steve French <sfrench@...ba.org>,
	Dave Kleikamp <shaggy@...nel.org>,
	Suma Ramars <sramars@...co.com>,
	Trond Myklebust <trond.myklebust@...marydata.com>,
	"Yan, Zheng" <zyan@...hat.com>
Subject: Re: [GIT PULL] [PATCH v4 00/26] Delete CURRENT_TIME and
 CURRENT_TIME_SEC macros

On Tue, Aug 16, 2016 at 11:18:52AM -0700, Deepa Dinamani wrote:
> Thank you for the suggestion.
> 
> > Who are you execting to pull this huge patch series?
> 
> The last pull request was addressed to Al as per Arnd's suggestion.
> I'm not completely sure who should it be addressed to.
> 
> > 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.
> 
> Arnd and I tried to do this a few ways.
> 
> We can try to introduce the api first like you suggest.
> 
> There are a few Acks already on the patches.
> And, patches 2-5 also need to be merged through some common tree like
> yours or Andrew's as you suggest.
> 
> So, if everyone is ok, I could do the following:
> 
> 1. Post patches 1-5 for rc-2.

-rc2 is already released, and we aren't adding new apis this late in the
release cycle, sorry.

> 2. Post all other patches to respective maintainers after rc-2
> 3. Then after patches get ignored or merged, post remaining as a
> series for you or Andrew to pick up.

The apis need to be aimed for 4.9-rc1, it's too late for 4.8, sorry.

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