From: Bjorn Helgaas <helgaas@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Abhishek Sahu <abhsahu@nvidia.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux PM <linux-pm@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH] PCI: Fix the ACPI power state during runtime resume
Date: Mon, 7 Feb 2022 14:13:43 -0600 [thread overview]
Message-ID: <20220207201343.GA413636@bhelgaas> (raw)
In-Reply-To: <2249802.ElGaqSPkdT@kreacher>
On Mon, Feb 07, 2022 at 07:58:13PM +0100, Rafael J. Wysocki wrote:
> On Saturday, February 5, 2022 12:32:19 AM CET Bjorn Helgaas wrote:
> > Wonder if we should add something like this to MAINTAINERS so you get
> > cc'd on power-related things:
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index ea3e6c914384..3d9a211cad5d 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -15422,6 +15422,7 @@ F: include/linux/pm.h
> > F: include/linux/pm_*
> > F: include/linux/powercap.h
> > F: kernel/configs/nopm.config
> > +K: pci_[a-z_]*power[a-z_]*\(
>
> It seems so, but generally PM patches should be CCed to linux-pm anyway.
Definitely. It's just that running get_maintainer.pl on this patch
currently shows:
Bjorn Helgaas <bhelgaas@google.com> (supporter:PCI SUBSYSTEM)
linux-pci@vger.kernel.org (open list:PCI SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)
so it's not as helpful as it could be. The MAINTAINERS patch above
would change it to this:
Bjorn Helgaas <bhelgaas@google.com> (supporter:PCI SUBSYSTEM)
"Rafael J. Wysocki" <rafael@kernel.org> (supporter:POWER MANAGEMENT CORE)
linux-pci@vger.kernel.org (open list:PCI SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)
linux-pm@vger.kernel.org (open list:POWER MANAGEMENT CORE)
Bjorn
next prev parent reply other threads:[~2022-02-07 20:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 12:21 [PATCH] PCI: Fix the ACPI power state during runtime resume Abhishek Sahu
2022-02-04 23:32 ` Bjorn Helgaas
2022-02-07 18:58 ` Rafael J. Wysocki
2022-02-07 20:13 ` Bjorn Helgaas [this message]
2022-02-08 10:30 ` Abhishek Sahu
2022-04-05 16:36 ` Abhishek Sahu
2022-04-05 16:50 ` Rafael J. Wysocki
2022-04-06 5:32 ` Abhishek Sahu
2022-04-06 12:06 ` Rafael J. Wysocki
2022-04-06 18:43 ` Abhishek Sahu
2022-04-06 18:49 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220207201343.GA413636@bhelgaas \
--to=helgaas@kernel.org \
--cc=abhsahu@nvidia.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).