From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 4671D221EA0BA for ; Fri, 8 Dec 2017 09:43:14 -0800 (PST) Date: Fri, 8 Dec 2017 10:47:47 -0700 From: Ross Zwisler Subject: Re: [fstests PATCH v6 2/2] generic: add test for DAX MAP_SYNC support Message-ID: <20171208174747.GA4308@linux.intel.com> References: <20171207103657.GF2749@eguan.usersys.redhat.com> <20171207231950.9023-1-ross.zwisler@linux.intel.com> <20171208063610.GH2749@eguan.usersys.redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20171208063610.GH2749@eguan.usersys.redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Eryu Guan Cc: Jan Kara , linux-nvdimm , Amir Goldstein , Dave Chinner , fstests , linux-xfs List-ID: On Fri, Dec 08, 2017 at 02:36:10PM +0800, Eryu Guan wrote: > (Test was re-numbered as generic/470, BTW.) Thanks! For future reference, does the pattern of us submitting tests with high numbers (generic/999) to avoid merge conflicts and asking you to renumber them when you merge work for you? Or would you prefer that we number our tests to the next available, which may change from submission to submission? _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm