From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
S-k Shyam-sundar <Shyam-sundar.S-k@amd.com>,
Natikar Basavaraj <Basavaraj.Natikar@amd.com>,
Deucher Alexander <Alexander.Deucher@amd.com>,
linux-pm@vger.kernel.org, Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCH v4 1/2] PCI: Refactor pci_bridge_d3_possible()
Date: Fri, 26 May 2023 15:12:41 +0300 [thread overview]
Message-ID: <20230526121241.GU45886@black.fi.intel.com> (raw)
In-Reply-To: <20230524190726.17012-1-mario.limonciello@amd.com>
On Wed, May 24, 2023 at 02:07:25PM -0500, Mario Limonciello wrote:
> All of the cases handled by pci_bridge_d3_possible() are specific
> to these branches:
> ```
> case PCI_EXP_TYPE_ROOT_PORT:
> case PCI_EXP_TYPE_UPSTREAM:
> case PCI_EXP_TYPE_DOWNSTREAM:
> ```
> Drop a level of indentation by returning false in the default case
> instead. No intended functional changes.
>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
prev parent reply other threads:[~2023-05-26 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 19:07 [PATCH v4 1/2] PCI: Refactor pci_bridge_d3_possible() Mario Limonciello
2023-05-24 19:07 ` [PATCH v4 2/2] PCI: Don't assume root ports from > 2015 are power manageable Mario Limonciello
2023-05-25 14:15 ` Rafael J. Wysocki
2023-05-25 14:21 ` Limonciello, Mario
2023-05-25 16:03 ` Sathyanarayanan Kuppuswamy
2023-05-25 16:10 ` Limonciello, Mario
2023-05-26 12:17 ` Mika Westerberg
2023-05-25 13:48 ` [PATCH v4 1/2] PCI: Refactor pci_bridge_d3_possible() Rafael J. Wysocki
2023-05-26 12:12 ` Mika Westerberg [this message]
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=20230526121241.GU45886@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Alexander.Deucher@amd.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mario.limonciello@amd.com \
--cc=rafael@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.