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=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 8F364C0650F for ; Thu, 8 Aug 2019 10:14:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6551720B7C for ; Thu, 8 Aug 2019 10:14:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389897AbfHHKOC (ORCPT ); Thu, 8 Aug 2019 06:14:02 -0400 Received: from foss.arm.com ([217.140.110.172]:59328 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389793AbfHHKOB (ORCPT ); Thu, 8 Aug 2019 06:14:01 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 152E328; Thu, 8 Aug 2019 03:14:01 -0700 (PDT) Received: from e121166-lin.cambridge.arm.com (e121166-lin.cambridge.arm.com [10.1.196.255]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 7D7403F694; Thu, 8 Aug 2019 03:13:59 -0700 (PDT) Date: Thu, 8 Aug 2019 11:13:54 +0100 From: Lorenzo Pieralisi To: Sasha Levin Cc: Bjorn Helgaas , Haiyang Zhang , Randy Dunlap , linux-pci , LKML , Matthew Wilcox , Jake Oshins , KY Srinivasan , Stephen Hemminger , Stephen Hemminger , Dexuan Cui Subject: Re: [PATCH] PCI: pci-hyperv: fix build errors on non-SYSFS config Message-ID: <20190808101354.GA30230@e121166-lin.cambridge.arm.com> References: <20190713150353.GF10104@sasha-vm> <20190723212107.GB9742@google.com> <20190807150654.GB16214@e121166-lin.cambridge.arm.com> <20190808012745.GV17747@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190808012745.GV17747@sasha-vm> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 07, 2019 at 09:27:45PM -0400, Sasha Levin wrote: > On Wed, Aug 07, 2019 at 04:06:54PM +0100, Lorenzo Pieralisi wrote: > > On Tue, Jul 23, 2019 at 04:21:07PM -0500, Bjorn Helgaas wrote: > > > On Sat, Jul 13, 2019 at 11:03:53AM -0400, Sasha Levin wrote: > > > > Queued up for hyperv-fixes, thank you! > > > > > > What merge strategy do you envision for this? Previous > > > drivers/pci/controller/pci-hyperv.c changes have generally been merged > > > by Lorenzo and incorporated into my PCI tree. > > > > > > This particular patch doesn't actually touch pci-hyperv.c; it touches > > > drivers/pci/Kconfig, so should somehow be coordinated with me. > > > > > > Does this need to be tagged for stable? a15f2c08c708 appeared in > > > v4.19, so my first guess is that it's not stable material. > > > > AFAIC Bjorn's question still stands. Who will pick this patch up ? > > Would it be easier if I just ignored Hyper-V PCI patches? I think it probably would, yes. Actually this patch does not even fall within "Hyper-V CORE AND DRIVERS" maintainers entry. As for drivers/pci/controller/pci-hyperv.c, for urgent fixes I understand it is easier for you to pull them I would still ask you please to sync with me before pulling them. Thanks, Lorenzo