From: Arnd Bergmann <arnd@arndb.de>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Andreas Dilger <adilger@dilger.ca>,
aivazian.tigran@gmail.com,
"Darrick J. Wong" <darrick.wong@oracle.com>,
David Sterba <dsterba@suse.com>,
gregkh <gregkh@linuxfoundation.org>,
Jeff Layton <jlayton@kernel.org>,
Kees Cook <keescook@chromium.org>,
me@bobcopeland.com,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
y2038 Mailman List <y2038@lists.linaro.org>
Subject: Re: [GIT PULL] vfs: Add support for timestamp limits
Date: Fri, 30 Aug 2019 14:56:46 +0200 [thread overview]
Message-ID: <CAK8P3a1XjOMpuS12Xao1xqOLFOuz1Jb8dTAfrhLcE643sSkC5g@mail.gmail.com> (raw)
In-Reply-To: <20190829041132.26677-1-deepa.kernel@gmail.com>
On Thu, Aug 29, 2019 at 6:12 AM Deepa Dinamani <deepa.kernel@gmail.com> wrote:
>
> Hi Al, Arnd,
>
> This is a pull request for filling in min and max timestamps for filesystems.
> I've added all the acks, and dropped the adfs patch. That will be merged through
> Russell's tree.
>
> Thanks,
> Deepa
>
> The following changes since commit 5d18cb62218608a1388858880ad3ec76d6cb0d3b:
>
> Add linux-next specific files for 20190828 (2019-08-28 19:59:14 +1000)
>
> are available in the Git repository at:
>
> https://github.com/deepa-hub/vfs limits
Please rebase this branch on top of linux-5.3-rc6 and resend.
I can't pull a branch that contains linux-next.
Maybe drop the orangefs patch for now, at least until we have come
to a conclusion on that.
Arnd
next prev parent reply other threads:[~2019-08-30 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 4:11 [GIT PULL] vfs: Add support for timestamp limits Deepa Dinamani
2019-08-30 12:56 ` Arnd Bergmann [this message]
2019-08-30 15:47 ` [GIT PULL RESEND] " Deepa Dinamani
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=CAK8P3a1XjOMpuS12Xao1xqOLFOuz1Jb8dTAfrhLcE643sSkC5g@mail.gmail.com \
--to=arnd@arndb.de \
--cc=adilger@dilger.ca \
--cc=aivazian.tigran@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=deepa.kernel@gmail.com \
--cc=dsterba@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=jlayton@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=me@bobcopeland.com \
--cc=viro@zeniv.linux.org.uk \
--cc=y2038@lists.linaro.org \
/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).