Received: by 10.223.164.202 with SMTP id h10csp3509258wrb; Tue, 28 Nov 2017 12:28:53 -0800 (PST) X-Google-Smtp-Source: AGs4zMZyU2NbIt1wcwCyICDRA5F5xX7uVL25lmnELdrTkEIz1RkE8PL5qBZIQgxlQRPMAJ41WIem X-Received: by 10.101.91.5 with SMTP id y5mr341202pgq.445.1511900933838; Tue, 28 Nov 2017 12:28:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1511900933; cv=none; d=google.com; s=arc-20160816; b=Jzqmtv2Ccf47uFPG7XJ88DkMECnXMJ81Qtq7Ij6H9ssFnZRGYxHe7aMCeBDtvGsA70 t9/uqfNM+aS1fKn1B79IBdPf4Ixc/9rCDC4OIGZNdiZtLYn3GUlBT5IUAf2gdBJN22R4 aA+mzkFq6b3ZT6jSadbxn2zqe+o1U+hg8dmAvYNMaJeo9Y7wMCMGAOH/bxO3DJi0zEBp fsHyzGayX3ElLmeRrEAKhyu2wHc4TgdEEH10DShlkMfQutsef1Rtv0kMUdF6UuNCR+vC gJQjHayUDUgrBy9ZgjlUrVSz82Dp5KgEUqcFZItgIsEv09y86CRrs3X+vzYjCb3Eukvy lQxA== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=Ncxn8UcXXwsMctPMoRuCg8ffKAPyG6o+bzckx+6JljQ=; b=Tryp9lgFaIGK4T0KIQe1gUDd3+bUkSGCDo1dcURFHkWbN4RIMZH5/n507ucKXMaS15 W81tMs2wWcjjHRFfqlRrRsI6sKuJvwis5V3AH5mlCHGQO1PA83nUDRmr98QUGp40v1HH Jl3StJj5j5uawzr+42d/J06Zdg6nmWWkqI8J8bpOwzh7UyXdj029EgdRvxwzO2Q7tFGq mABFLHlEO3lWUyTkiJGMeZz50/wWbFhIlobzvh9J8GxEf3QAtnvop4/wYIdqlugBQlSD wDvbnOM8S9IGnbpGZK1EIlsjZDg4IpG/ZFb6byZaLMv6QjB/7GoJ5NjaUIQEx0voHYR8 PEIg== 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 r59si5818plb.314.2017.11.28.12.28.43; Tue, 28 Nov 2017 12:28:53 -0800 (PST) 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 S1754305AbdK1U12 (ORCPT + 70 others); Tue, 28 Nov 2017 15:27:28 -0500 Received: from mga06.intel.com ([134.134.136.31]:15963 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753164AbdK1U10 (ORCPT ); Tue, 28 Nov 2017 15:27:26 -0500 Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Nov 2017 12:27:26 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,468,1505804400"; d="scan'208";a="154132951" Received: from ddalessa-mobl2.amr.corp.intel.com (HELO [10.254.135.60]) ([10.254.135.60]) by orsmga004.jf.intel.com with ESMTP; 28 Nov 2017 12:27:24 -0800 Subject: Re: [PATCH 0/3] RDMA/hns: Bug fixes in hns RoCE driver To: Jason Gunthorpe , Bart Van Assche Cc: "linux-kernel@vger.kernel.org" , "linux-rdma@vger.kernel.org" , "xavier_huwei@163.com" , "linuxarm@huawei.com" , "xavier.huwei@huawei.com" , "xavier.huwei@tom.com" , "leon@kernel.org" , "dledford@redhat.com" References: <1511750484-102395-1-git-send-email-xavier.huwei@huawei.com> <20171127183637.GA13966@ziepe.ca> <20171128061517.GO29104@mtr-leonro.local> <6e9c4251-8e56-54e2-b186-d3d5b1b85204@intel.com> <20171128183910.GA21325@ziepe.ca> <1511895042.28512.6.camel@wdc.com> <20171128193311.GB21325@ziepe.ca> From: Dennis Dalessandro Message-ID: Date: Tue, 28 Nov 2017 15:27:23 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171128193311.GB21325@ziepe.ca> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/28/2017 2:33 PM, Jason Gunthorpe wrote: > On Tue, Nov 28, 2017 at 06:50:44PM +0000, Bart Van Assche wrote: >> On Tue, 2017-11-28 at 11:39 -0700, Jason Gunthorpe wrote: >>> On Tue, Nov 28, 2017 at 08:20:09AM -0500, Dennis Dalessandro wrote: >>>> I could resubmit just the series, or you could just pick the 4 driver >>>> patches from patchworks whatever is easiest. >>> >>> I marked them in patchworks, but can you review the commit messages >>> and make sure you think Linus will see them as rc material too? >> >> My understanding is that the rc stage is intended primarily for fixes for >> bugs introduced during the merge window. For all patches that do not fix >> bugs introduced during the merge window it should be evaluated carefully >> whether or not these are important enough to be included in a rc pull request. > > Oh? I thought it was more up to the maintainer discretion within some > limits. Eg I thought we were running rdma more with the 'if it is OK > for -stable, then it is OK -rc' kind of mentality? That's always been my understanding. > eg -rc is for stablization and bugfixing only, and not restricted only > to bugs introduced in the latest merge window?? Makes no sense to me to have a hard restriction here. Security fixes, panics, and other serious bugs should certainly qualify. Of course that is subject to how complex the fix is. -Denny From 1585339681967267582@xxx Tue Nov 28 19:35:37 +0000 2017 X-GM-THRID: 1585183540036899465 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread