Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3425679imu; Mon, 24 Dec 2018 01:31:05 -0800 (PST) X-Google-Smtp-Source: ALg8bN7Omh0b0248F3r7MUPMKGsBMTwSYhHAVBn4GoFMbC1H/jQ2vcofqQfZDTL14qIMhXZEhChK X-Received: by 2002:a63:4456:: with SMTP id t22mr11981389pgk.0.1545643865152; Mon, 24 Dec 2018 01:31:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545643865; cv=none; d=google.com; s=arc-20160816; b=jRMYQbx32KJIR0j+/OJnzVibtgSJy9JicDmPdNsKQ0/vKTvqLWhd90k3Mi95L5xh0w kKYk4xxJ51j3tP74xftzqJWksbny1XhI5efboW8QdfiTekE28JA7cZ/oE7qUcH9OXzUc lQ5DcIU9zTU58iHw5ZmiygB0kUpXcDt0dtc8lfQVxcdlMiHyYWercvxpBVFZktFXNzP5 ZjM2K0KpQ+iEv9mMP31IH0GAz0987geo5PxK+zrcKSp/1a5g1d0OSHAG0zlhB7a8TPSe /o43E5O4SgUyNEwqI1TPsao6TMnSCqeyIQVSxj0pyL7OsYDF9FCwMVAJrWydKwTWSlnt wGMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=HPezM66pVmxTxhKD/0frKbX9UwCxSC89V6zm7ebpruo=; b=r33B8tABisl9n3VI4FCiyu5XBzHcmXo00nS8R1DPPjo1Gh09nu7RgtjpNBNkRQbDBY 3DTDN86XT/qzEMkmNWx52UHoifHx7vJvfHwVE2U+kp1/nW2VfOMURTyF6tH7ID9L3cFC 2cmOhba97UshYKZLsp+i/Bt8TnQajSvLDhH22Xs05xUJH2qONrL+t2Pm00HPjutLunYZ M8VzEAhKluhNplUJ3kx9uq6lLxncM6ifDL2NscmC3RCIeXVnVTjmoKYSyfF6okOdmBWw KyhAg2lAkZnFgZNJEDOQeW+5f1NHPSBUsMDsTpH/9ZnkQW81ZqYl/RvjxVkUVgQoDjz8 zz4A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ffwll.ch header.s=google header.b=kRDf7uuy; 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 d8si8202400pgl.386.2018.12.24.01.30.49; Mon, 24 Dec 2018 01:31:05 -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; dkim=pass header.i=@ffwll.ch header.s=google header.b=kRDf7uuy; 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 S1725836AbeLXJ1z (ORCPT + 99 others); Mon, 24 Dec 2018 04:27:55 -0500 Received: from mail-it1-f196.google.com ([209.85.166.196]:54876 "EHLO mail-it1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725298AbeLXJ1y (ORCPT ); Mon, 24 Dec 2018 04:27:54 -0500 Received: by mail-it1-f196.google.com with SMTP id i145so15209011ita.4 for ; Mon, 24 Dec 2018 01:27:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HPezM66pVmxTxhKD/0frKbX9UwCxSC89V6zm7ebpruo=; b=kRDf7uuyvhxEj23tQDxxx5PSLRBVG75DFCkp4boAk779KVCLjsmp8T5E4bqR925SG+ Brc85PzYQTn8TISAkfc4AMLLHQRUWBcJsl1CibxgyojE2PnuvyvpnbHOf0JsyPtNEJTA ZOfkqEKx5yO3OMpE/IoqcD0gaD5qZyTb2NZS4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HPezM66pVmxTxhKD/0frKbX9UwCxSC89V6zm7ebpruo=; b=c34To8rDvPyecObdpzAH02DQV5wK5Cd5oSXLiKlx2pROG+C5WyKrG5P1gRKPhg5EaK DuEV7ueI7BqOHDzujeN46+F2l0GjAzUvOhdrYOFbxXRtlTAFpukJEBYaWG6JMZwXquph LOT6si7zyrtRCYulkVC3wkvdmIjpk1khAA/wi51KlGZ7lRKz82x1L6T32vbE+r6B2gd7 HuKtjVjz0id00aJoYW41V3g1o2/7m2Ve2vIEo4IObgH7mo2wbQ7iqBfBAShfJvvn/QgO Z0f52fAqN4LMoWye/p/EQbQXT5uYs3eWZrSlOjBXBV1GPYiRdbHTdk/8R9BkSiQHb8sK gkbA== X-Gm-Message-State: AA+aEWYYTntVVAPx8SME0nDl2mlzZ7doljSt56Tz3hcWdtIuK+2/a0Sf nBcrrVwcQQpUNWCTzmDBlO++hgI61i3/jOeW0bzHRw== X-Received: by 2002:a02:85ae:: with SMTP id d43mr8113309jai.70.1545643673277; Mon, 24 Dec 2018 01:27:53 -0800 (PST) MIME-Version: 1.0 References: <20181222090720.19234-1-okaya@kernel.org> <20181222090720.19234-4-okaya@kernel.org> <20181222164013.2l7etklpxjrrobnm@wunner.de> <20181223171501.4hwqu6wn4jzwrcmn@wunner.de> In-Reply-To: <20181223171501.4hwqu6wn4jzwrcmn@wunner.de> From: Daniel Vetter Date: Mon, 24 Dec 2018 10:27:28 +0100 Message-ID: Subject: Re: [PATCH v2 03/11] vga-switcheroo: make PCI dependency explicit To: Lukas Wunner Cc: Sinan Kaya , ACPI Devel Mailing List , Maxime Ripard , "open list:PCI SUBSYSTEM" , open list , "open list:DRM DRIVERS" , David Airlie , Sean Paul Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Dec 23, 2018 at 6:15 PM Lukas Wunner wrote: > > On Sun, Dec 23, 2018 at 02:00:15AM +0300, Sinan Kaya wrote: > > On Sat, Dec 22, 2018 at 7:40 PM Lukas Wunner wrote: > > > On Sat, Dec 22, 2018 at 09:07:12AM +0000, Sinan Kaya wrote: > > > > This driver depends on the PCI infrastructure but the dependency has not > > > > been explicitly called out. > > > > > > > > Signed-off-by: Sinan Kaya > > > > Reviewed-by: Lukas Wunner > > > > > > This series doesn't have a cover letter so it's unclear to me through > > > which tree it's supposed to go in? Each patch through the individual > > > subsystem tree or all through the same tree? If the former I guess I > > > could push this to drm-misc... > > > > Feel free to apply individual patches independently. Let me know which > > one you applied so that I can drop them on the next rev. > > I've realized only now that this patch fixes fallout of commit > 5d32a66541c4 ("PCI/ACPI: Allow ACPI to be built without CONFIG_PCI set") > which is part of Rafael's acpi pull for v4.21. > > Usually such fixes go through the same tree as the offending commit, > so I'd expect Raphael to pick up the whole series and forward it to > Linus in the second half of the merge window. I'm not sure if that's > how it'll play out though given the holidays. Yeah, best to get this merged through the tree that broke things. Acked-by: Daniel Vetter for that. > Additionally, drm-misc is currently in a somewhat confusing state: > Normally fixes targeting v4.21 should have been applied to > drm-misc-next-fixes for the last 2 weeks, yet no new commits have > been applied to that branch since December 5, but plenty of stuff > that should have been applied (various fixes and a MAINTAINERS change) > went to drm-misc-next instead. So it looks like a lot of folks picked > the wrong branch and drm-misc-next is now a mix of v4.22 features and > v4.21 fixes. I think I should rather not add to this mess before a > drm-misc maintainer has had a chance to sort it out. If a patch has been misplaced the only way to fix it is to cherry-pick it over. Hence no need to wait for maintainers to sort out anything if you have patches for drm-misc-next-fixes, you can't make it worse :-) > I'll be sure to keep an eye on this though. The fallout addressed by > the patch is mostly confined to randconfigs I think, so waiting a few > more days probably won't hurt much. Agreed. -Daniel > > Thanks, > > Lukas > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch