From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PULL_REQUEST,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0D37BC3A5A7 for ; Fri, 30 Aug 2019 12:57:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D67E821874 for ; Fri, 30 Aug 2019 12:57:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727999AbfH3M5E (ORCPT ); Fri, 30 Aug 2019 08:57:04 -0400 Received: from mail-qt1-f193.google.com ([209.85.160.193]:36318 "EHLO mail-qt1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727522AbfH3M5E (ORCPT ); Fri, 30 Aug 2019 08:57:04 -0400 Received: by mail-qt1-f193.google.com with SMTP id z4so7487045qtc.3; Fri, 30 Aug 2019 05:57:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SFaIBBUhr4/2SlKlC0SL+JS7SwhLYOWGWRxz8fCIXxs=; b=V7y82OeYxHoKF2bMgFWXDxbpr5IM9dUbPZ9UDk1SoC+/u4ItFqpuSO3uNH7DB9Rx9w qYPTqv5OINm45mVxdoC9D0lh11juJGQX5OiDqOU8G/RdBEb6Jc97JExC74Iiwz8VQG8F CLoP6DRB/xEUVlZVyZWtxBBYigkOAtQiqsCght6YPNvzmX3VSplR0WUG1w37cgN17ixT Ap9Azd5HAYqwsPaF7NGJVvOb/8Sl9JE2f4SC1xbaDeGpYSPhHG+fFJvA+mYf0SVwnzNG zxhrpa1WUDa2ezgDKlDGm5itn0+RSq1w5OWNyLRf31dD0wdaTBJincXJVoL/LzwGvWNI Bjhw== X-Gm-Message-State: APjAAAXGt9rQMoZLZn322xlpnh4zQagQ/XxEJ7DTM11yzOpuhVrAYn7H r9elxp7LZmbkW0JtwpWXkkLCB7bwywu1kciUgiE= X-Google-Smtp-Source: APXvYqx86F6I04uUf5dj55lbh3ezYYy6ct+9ri3fU2IjZXZtb6IRyo6Yls4GC5k0q7MYBeyK3/385Tfjt0p1owjzSts= X-Received: by 2002:ac8:117:: with SMTP id e23mr15085989qtg.18.1567169823216; Fri, 30 Aug 2019 05:57:03 -0700 (PDT) MIME-Version: 1.0 References: <20190829041132.26677-1-deepa.kernel@gmail.com> In-Reply-To: <20190829041132.26677-1-deepa.kernel@gmail.com> From: Arnd Bergmann Date: Fri, 30 Aug 2019 14:56:46 +0200 Message-ID: Subject: Re: [GIT PULL] vfs: Add support for timestamp limits To: Deepa Dinamani Cc: Al Viro , Andreas Dilger , aivazian.tigran@gmail.com, "Darrick J. Wong" , David Sterba , gregkh , Jeff Layton , Kees Cook , me@bobcopeland.com, Russell King - ARM Linux , Linux Kernel Mailing List , Linux FS-devel Mailing List , y2038 Mailman List Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Thu, Aug 29, 2019 at 6:12 AM Deepa Dinamani 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