Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1246606imm; Wed, 25 Jul 2018 14:23:58 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcth1+tr/WM23R/aqtDu9bmWclWAdN0tq7zcxWJQ11lvI3RmjweG05X9ryXuwDGKLJCYorF X-Received: by 2002:a63:b256:: with SMTP id t22-v6mr22662353pgo.101.1532553838735; Wed, 25 Jul 2018 14:23:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532553838; cv=none; d=google.com; s=arc-20160816; b=yrWoYrA4klQyISYNLMgBGlR42GZlwlhBT0WO3hSOdh4GBc/4tbXXQo2Al6uKr42ZIJ 4iFU+u1lC9+TDXB7Xv38jYp2cvkvEAZMP+fyI4JQ0Z0A8K3UpfsOPhITnh1pUBQwk3oF XRcdntzRo5KpnJghj3Hm23S0PiSMqJjbfLvn+H3yGkiEK74H8Gdn5D0s+SKhlB35FUTv Pwsg2Dn0di1ctRihyaB81RwcBqTu8KH8+2EpBqfuaLhnOrJaLXewLXC2+N1eeW816aI+ OapSVZM4Wtp3DV3lIaV6hL1pIns436i05CB4kg8fwyFvVVD5b54wYsbo73kpqiS4xYK5 54Rg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :arc-authentication-results; bh=Jm/iXJtYRjZBX1VNnESJf9jdmP57v4V/eFM33S8Ytu4=; b=b8otnzzSnxHd0kP+PyuBPuZccNBw/co2emji2PoxBc1o3GbAi87/szJ7EFmfIaBj0V KIkETr2eymROgyFtXLPuM+BXQ98Ogx3QFTUTkH5qEn/l2zQ7NDc7vMwPYEJ0tjLBGOtZ CckVyB0s9C5oOsVZSMBDQWFhqTcnyd86whD+s1JxOCqUdckmZSIZAcIx0E+exJ56yRzx hRyZSlYJSuiEI1kWIsg4zOXFxy42znycOZqaZEAd1DdheegAEjBFaYyp9vjhgf4kyF5b uvmTpydoewQp6gJPApDWXP3+EmSrNwNjDfkQBWFBZ4Pnkfyl0AvCh+l59Bww430rH3wT 7uhg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j135-v6si16485651pfd.207.2018.07.25.14.23.43; Wed, 25 Jul 2018 14:23:58 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731389AbeGYWgT (ORCPT + 99 others); Wed, 25 Jul 2018 18:36:19 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:56696 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730337AbeGYWgT (ORCPT ); Wed, 25 Jul 2018 18:36:19 -0400 Received: from localhost.localdomain (c-24-4-125-7.hsd1.ca.comcast.net [24.4.125.7]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id 154A1D8D; Wed, 25 Jul 2018 21:22:47 +0000 (UTC) Date: Wed, 25 Jul 2018 14:22:46 -0700 From: Andrew Morton To: Coly Li Cc: Andy Shevchenko , Eric Biggers , linux-kernel@vger.kernel.org, linux-bcache@vger.kernel.org, linux-block@vger.kernel.org, Greg Kroah-Hartman , Michael Lyle , Kent Overstreet , Linus Torvalds , Thomas Gleixner , Kate Stewart , Randy Dunlap Subject: Re: [PATCH v4 1/3] lib: add crc64 calculation routines Message-Id: <20180725142246.23e354fcc21ef041bb3f87e6@linux-foundation.org> In-Reply-To: <01f8e352-a49f-2f41-6264-bb6395bb0bf2@suse.de> References: <20180718165545.1622-1-colyli@suse.de> <20180718165545.1622-2-colyli@suse.de> <20180724042637.GA1944@sol.localdomain> <399c1cc851f983370a0308c76c68a97ff41a5d4f.camel@linux.intel.com> <01f8e352-a49f-2f41-6264-bb6395bb0bf2@suse.de> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 25 Jul 2018 10:37:23 +0800 Coly Li wrote: > > IIUC this series in Andrew's quilt. So, it's still possible to replace > > it with better one, I suppose. Ask Andrew (at least I remember recent > > case where he just replaced series by fixed one). > > Hi Andrew, > > It seems there should be some fix/update for this series. I see current > series is in linux-next for now. If I want to add the fix, should I post > a new version of the series, or the incremental patches to fix current > series ? mm... it sounds like the changes will be large, so probably a new series would be better at this early stage. If the changes are small then little fixup patches would be nicer to the people who have already reviewed v1.