Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp4257067ybg; Mon, 21 Oct 2019 06:18:38 -0700 (PDT) X-Google-Smtp-Source: APXvYqyr+LvCE9uUJQ1NXEM3e31YloS9dVL62oOXtDJINAYxNx2rJFG1p1ChvEnDsMIjOtMt+9PG X-Received: by 2002:aa7:ca59:: with SMTP id j25mr24957516edt.78.1571663918521; Mon, 21 Oct 2019 06:18:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571663918; cv=none; d=google.com; s=arc-20160816; b=aCtJhQYOhHkdO5ulyuKKXhLhbcIKqrmVrF2oP02cO6XU+9irII3cjYa/J/HfeSJkDS QaAZKOyQfTVUsREQ8xwbhTnyQrsyupryYvT9rdvIdUf3h6t+4vuzkS84fYutXteWHoRL Htbzems6T3/9szifKWlMaAZ+ok7oemBdp3VTWJ6yKvydbEUMa3LavORTznOxdXctVdWx l31hHZ5OXURUURbzswD5fMW0TDpBZ7BFy3iaM/9wt6ExtghsIOEAYPjFrpfzmZ1vuEn+ CLtPgNzhVhRG9iSBbYJA8qkjqyN7uzRI43VwfvQZZgCWbQ9I5bMeR1MuaVn+pzFdEPKH 5yXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:subject:cc:to:from:message-id:date; bh=menOCtIyDVWuwU5LsTMdgYlEA11DdxL3neUDLUL54uQ=; b=ywWWnGyoALtJcHRM44hufE2YA0gt6iVLtYsRxJvPv0y3X6g2ELeZyo6PrhNONlr7Af hA8Iv/VfEDnByrqTlp0HSuGrXrD4piXxkclbTGkz9XtxrfmaRLE2BXGG7qzzoxiCWhxW EksN/BJ/nY5BHsfi+DzhlNgG9zZRRkd5VKtEMw0ioLt1EFtpNt7vzmtij76PlrYBSDlz EV4h4tXGKQof93A/39oEMbuycj1WKBbCCLDwckTkIekDI6I0gagNR4fQv1vofKX1CxUz kOjDsj1KPcO4eEUxCoc0QL+q+Oc9fA51w4+EcZtrUPUpZ88aKdA1VfFVtYR1Q6aBaJMr eY6w== 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 k16si8143573ejc.134.2019.10.21.06.18.14; Mon, 21 Oct 2019 06:18:38 -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 S1728792AbfJUNPQ (ORCPT + 99 others); Mon, 21 Oct 2019 09:15:16 -0400 Received: from mx2.suse.de ([195.135.220.15]:43368 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726767AbfJUNPQ (ORCPT ); Mon, 21 Oct 2019 09:15:16 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 07225B712; Mon, 21 Oct 2019 13:15:14 +0000 (UTC) Date: Mon, 21 Oct 2019 15:15:14 +0200 Message-ID: From: Takashi Iwai To: Kai-Heng Feng Cc: bhelgaas@google.com, linux-pci@vger.kernel.org, alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v6 1/2] PCI: Add a helper to check Power Resource Requirements _PR3 existence In-Reply-To: References: <20191018073848.14590-1-kai.heng.feng@canonical.com> <4C18DF4A-FAE8-4762-AF65-F892A4845297@canonical.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 18 Oct 2019 10:45:43 +0200, Takashi Iwai wrote: > > On Fri, 18 Oct 2019 10:30:11 +0200, > Kai-Heng Feng wrote: > > > > > > > > > On Oct 18, 2019, at 16:18, Takashi Iwai wrote: > > > > > > On Fri, 18 Oct 2019 09:38:47 +0200, > > > Kai-Heng Feng wrote: > > >> > > >> A driver may want to know the existence of _PR3, to choose different > > >> runtime suspend behavior. A user will be add in next patch. > > >> > > >> This is mostly the same as nouveau_pr3_present(). > > >> > > >> Reported-by: kbuild test robot > > > > > > It's confusing -- this particular change isn't reported by the test > > > bot, but only about the lack of the CONFIG_ACPI ifdef. > > > > Hmm, because the test bot asked to add the tag. > > Yes, but it's only if you add a new fix patch on top of it. > You can write some their credit, too, but basically it'd be enough to > point to the Link tag to the thread. > > > If it's not appropriate will you drop it? I can also send a v7. > > I can modify in my side. Now I merged both patches to for-next branch. thanks, Takashi