From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753268AbdKHDBl (ORCPT ); Tue, 7 Nov 2017 22:01:41 -0500 Received: from mail.kernel.org ([198.145.29.99]:39244 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752189AbdKHDBk (ORCPT ); Tue, 7 Nov 2017 22:01:40 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EBDD5218DB Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=helgaas@kernel.org Date: Tue, 7 Nov 2017 21:01:33 -0600 From: Bjorn Helgaas To: Dexuan Cui Cc: Bjorn Helgaas , "linux-pci@vger.kernel.org" , Jake Oshins , KY Srinivasan , Stephen Hemminger , "devel@linuxdriverproject.org" , "linux-kernel@vger.kernel.org" , Haiyang Zhang , Jork Loeser , "Chris Valean (Cloudbase Solutions SRL)" , "Adrian Suhov (Cloudbase Solutions SRL)" , Simon Xiao , "'Eyal Mizrachi'" , Jack Morgenstein , Armen Guezalian , Firas Mahameed , Tziporet Koren , Daniel Jurgens Subject: Re: [PATCH] PCI: hv: use effective affinity mask Message-ID: <20171108030133.GB28427@bhelgaas-glaptop.roam.corp.google.com> References: <20171108010736.GA28427@bhelgaas-glaptop.roam.corp.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 08, 2017 at 01:27:02AM +0000, Dexuan Cui wrote: > > From: Bjorn Helgaas [mailto:helgaas@kernel.org] > > Sent: Tuesday, November 7, 2017 5:08 PM > > On Wed, Nov 01, 2017 at 08:30:53PM +0000, Dexuan Cui wrote: > > > > > > Please consider this for v4.14, if it's not too late. > > > > What would be the rationale for putting it in v4.14? After the merge > > window, I usually only merge fixes for problems introduced during the > > merge window, or for serious regressions. I can't tell if this fits > > into that or not. > > The patch was sent last Wednesday and I hoped it could catch the > merge window to be in v4.14 so we won't have to request a backport > for the v4.14 stable kernel in future. And I was not exactly sure when > the merge window was. Sorry :-) > > The patch is not fixing a serious regression. It just fixes a long standing > issue from the beginning of the Hyper-V vPCI driver: 1 of 7 Mellanox > VFs of a 32-vCPU VM running on Hyper-V may not receive interrupts. No problem. I added a stable tag so the backport should happen automatically and put it on my pci/host-hv branch for v4.15, with Jake's Reviewed-by. Thanks! Bjorn