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=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 906BCC432C0 for ; Tue, 3 Dec 2019 19:49:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 606D220848 for ; Tue, 3 Dec 2019 19:49:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1575402576; bh=XZYdwxIyyXzrV+GgI6eO+IzRghYU+tO8fxY7E4KpR+4=; h=Subject:From:To:Cc:Date:In-Reply-To:References:List-ID:From; b=EPo/G/i50ryOpsb4I6JnYj3U/wfcKuRDvK9fcDfWXVgPMvLgpvc6pBb1bAlDPBmI/ tnbHXLq0LTW7kWp3dqB8ceHmpDdC0xhF0TAszC4pQx4QcCaSpv6QFggVLb0KBS361g y/SVZpuj8ST0sJKS1hnZJfuReltltiMZJUg76Rr4= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727333AbfLCTtb (ORCPT ); Tue, 3 Dec 2019 14:49:31 -0500 Received: from mail.kernel.org ([198.145.29.99]:39494 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726893AbfLCTtb (ORCPT ); Tue, 3 Dec 2019 14:49:31 -0500 Received: from tleilax.poochiereds.net (68-20-15-154.lightspeed.rlghnc.sbcglobal.net [68.20.15.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 381D220803; Tue, 3 Dec 2019 19:49:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1575402570; bh=XZYdwxIyyXzrV+GgI6eO+IzRghYU+tO8fxY7E4KpR+4=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=GBGFpXZ8pmDVTbUWqrO01MKmWInej3wCsbBIxpEFNf77grDTPWjQz5crY7RW0GAUl YAx2r1XowsvtsipWC5N7w+JAc3z71BDEHBGfg9CsuDuqPwegHUm6rojrKv9LmC8Al4 0Mc/VUmeti9VYQhTCOqKTcthgIqrObblIWLiZ5Zk= Message-ID: <24dc8c6760b3ea2797c13558d8eca124e2c629f1.camel@kernel.org> Subject: Re: [PATCH v2 3/6] fs: ceph: Delete timespec64_trunc() usage From: Jeff Layton To: Deepa Dinamani Cc: Alexander Viro , Linux Kernel Mailing List , Linux FS-devel Mailing List , Arnd Bergmann , ceph-devel , Ilya Dryomov Date: Tue, 03 Dec 2019 14:49:29 -0500 In-Reply-To: References: <20191203051945.9440-1-deepa.kernel@gmail.com> <20191203051945.9440-4-deepa.kernel@gmail.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.2 (3.34.2-1.fc31) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Tue, 2019-12-03 at 11:41 -0800, Deepa Dinamani wrote: > > Thanks Deepa. We'll plan to take this one in via the ceph tree. > > Actually, deletion of the timespec64_trunc() will depend on this > patch. Can we merge the series through a common tree? Otherwise, > whoever takes the [PATCH 6/7] ("fs: > Delete timespec64_trunc()") would have to depend on your tree. If you > are ok with the change, can you ack it? > > Thanks, > Deepa Sure, no problem if that works better for you. Acked-by: Jeff Layton