From: Greg KH <gregkh@linuxfoundation.org>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Alexander Viro <viro@zeniv.linux.org.uk>,
y2038 Mailman List <y2038@lists.linaro.org>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Adrian Hunter <adrian.hunter@intel.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Brian Uchino <buchino@cisco.com>,
ceph-devel <ceph-devel@vger.kernel.org>, Chris Mason <clm@fb.com>,
Changman Lee <cm224.lee@samsung.com>,
Artem Bityutskiy <dedekind1@gmail.com>,
David Sterba <dsterba@suse.com>,
Evgeniy Dushistov <dushistov@mail.ru>,
Alex Elder <elder@kernel.org>, Eric Paris <eparis@redhat.com>,
Hiral Patel <hiralpat@cisco.com>,
Ilya Dryomov <idryomov@gmail.com>, Jan Kara <jack@suse.com>,
Jaegeuk Kim <jaegeuk@kernel.org>, Josef Bacik <jbacik@fb.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
jfs-discussion@lists.sourceforge.net,
Joel Becker <jlbec@evilplan.org>,
John Stultz <john.stultz@linaro.org>,
linux-audit@redhat.com, linux-btrfs <linux-btrfs@vger.kernel.org>,
linux-ext4@vger.kernel.org, "Linux F2FS DEV,
Mailing List" <linux-f2fs-devel@lists.sourceforge.net>,
linux-mtd <linux-mtd@lists.infradead.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux SCSI List <linux-scsi@vger.kernel.org>,
lustre-devel@lists.lustre.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Mark Fasheh <mfasheh@suse.com>,
ocfs2-devel@oss.oracle.com, Paul Moore <paul@paul-moore.com>,
Sage Weil <sage@redhat.com>, Steve French <sfrench@samba.org>,
Dave Kleikamp <shaggy@kernel.org>,
Suma Ramars <sramars@cisco.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
"Yan, Zheng" <zyan@redhat.com>
Subject: Re: [GIT PULL] [PATCH v4 00/26] Delete CURRENT_TIME and CURRENT_TIME_SEC macros
Date: Tue, 16 Aug 2016 20:53:20 +0200 [thread overview]
Message-ID: <20160816185320.GB6513@kroah.com> (raw)
In-Reply-To: <CABeXuvp027DZR0=zQPp86oGdi2B+Gh16z8_FyoY5UDUdHXAngA@mail.gmail.com>
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
next prev parent reply other threads:[~2016-08-16 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 22:48 [GIT PULL] [PATCH v4 00/26] Delete CURRENT_TIME and CURRENT_TIME_SEC macros Deepa Dinamani
2016-08-13 22:48 ` [PATCH v4 10/26] fs: btrfs: Use ktime_get_real_ts for root ctime Deepa Dinamani
2016-08-15 13:26 ` David Sterba
2016-08-15 16:23 ` [GIT PULL] [PATCH v4 00/26] Delete CURRENT_TIME and CURRENT_TIME_SEC macros Greg KH
2016-08-16 18:18 ` Deepa Dinamani
2016-08-16 18:53 ` Greg KH [this message]
2016-08-23 14:51 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160816185320.GB6513@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adilger.kernel@dilger.ca \
--cc=adrian.hunter@intel.com \
--cc=anna.schumaker@netapp.com \
--cc=arnd@arndb.de \
--cc=buchino@cisco.com \
--cc=ceph-devel@vger.kernel.org \
--cc=clm@fb.com \
--cc=cm224.lee@samsung.com \
--cc=dedekind1@gmail.com \
--cc=deepa.kernel@gmail.com \
--cc=dsterba@suse.com \
--cc=dushistov@mail.ru \
--cc=elder@kernel.org \
--cc=eparis@redhat.com \
--cc=hiralpat@cisco.com \
--cc=idryomov@gmail.com \
--cc=jack@suse.com \
--cc=jaegeuk@kernel.org \
--cc=jbacik@fb.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=jlbec@evilplan.org \
--cc=john.stultz@linaro.org \
--cc=linux-audit@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=martin.petersen@oracle.com \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=paul@paul-moore.com \
--cc=sage@redhat.com \
--cc=sfrench@samba.org \
--cc=shaggy@kernel.org \
--cc=sramars@cisco.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=trond.myklebust@primarydata.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=y2038@lists.linaro.org \
--cc=zyan@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).