From: Mario Limonciello <mario.limonciello@amd.com>
To: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com
Cc: Sanket.Goswami@amd.com, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 3/4] platform/x86/amd/pmc: Remove unnecessary line breaks
Date: Mon, 17 Feb 2025 09:38:45 -0600 [thread overview]
Message-ID: <14d745cd-6c36-4db1-8605-5bb169f8dd80@amd.com> (raw)
In-Reply-To: <20250217081720.107719-3-Shyam-sundar.S-k@amd.com>
On 2/17/2025 02:17, Shyam Sundar S K wrote:
> Enhance code readability by fixing line break and blank line
> inconsistencies.
>
> Co-developed-by: Sanket Goswami <Sanket.Goswami@amd.com>
> Signed-off-by: Sanket Goswami <Sanket.Goswami@amd.com>
> Signed-off-by: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
> ---
> drivers/platform/x86/amd/pmc/pmc.c | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/drivers/platform/x86/amd/pmc/pmc.c b/drivers/platform/x86/amd/pmc/pmc.c
> index 742920530987..d80a5b899a1d 100644
> --- a/drivers/platform/x86/amd/pmc/pmc.c
> +++ b/drivers/platform/x86/amd/pmc/pmc.c
> @@ -168,7 +168,6 @@ static int get_metrics_table(struct amd_pmc_dev *pdev, struct smu_metrics *table
> {
> if (!pdev->smu_virt_addr) {
> int ret = amd_pmc_setup_smu_logging(pdev);
> -
> if (ret)
Does checkpatch like this?
I thought it has checks explicitly for
"Missing a blank line after declarations"
> return ret;
> }
> @@ -222,7 +221,6 @@ static ssize_t smu_fw_version_show(struct device *d, struct device_attribute *at
>
> if (!dev->major) {
> int rc = amd_pmc_get_smu_version(dev);
> -
> if (rc)
> return rc;
> }
> @@ -236,7 +234,6 @@ static ssize_t smu_program_show(struct device *d, struct device_attribute *attr,
>
> if (!dev->major) {
> int rc = amd_pmc_get_smu_version(dev);
> -
> if (rc)
> return rc;
> }
> @@ -704,7 +701,6 @@ static int amd_pmc_suspend_handler(struct device *dev)
> */
> if (pdev->disable_8042_wakeup && !disable_workarounds) {
> int rc = amd_pmc_wa_irq1(pdev);
> -
> if (rc) {
> dev_err(pdev->dev, "failed to adjust keyboard wakeup: %d\n", rc);
> return rc;
> @@ -743,7 +739,6 @@ static int amd_pmc_probe(struct platform_device *pdev)
> u32 val;
>
> dev->dev = &pdev->dev;
> -
> rdev = pci_get_domain_bus_and_slot(0, 0, PCI_DEVFN(0, 0));
> if (!rdev || !pci_match_id(pmc_pci_ids, rdev)) {
> err = -ENODEV;
> @@ -751,7 +746,6 @@ static int amd_pmc_probe(struct platform_device *pdev)
> }
>
> dev->cpu_id = rdev->device;
> -
> if (dev->cpu_id == AMD_CPU_ID_SP || dev->cpu_id == AMD_CPU_ID_SHP) {
> dev_warn_once(dev->dev, "S0i3 is not supported on this hardware\n");
> err = -ENODEV;
> @@ -767,7 +761,6 @@ static int amd_pmc_probe(struct platform_device *pdev)
> }
>
> base_addr_lo = val & AMD_PMC_BASE_ADDR_HI_MASK;
> -
> err = amd_smn_read(0, AMD_PMC_BASE_ADDR_HI, &val);
> if (err) {
> dev_err(dev->dev, "error reading 0x%x\n", AMD_PMC_BASE_ADDR_HI);
next prev parent reply other threads:[~2025-02-17 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 8:17 [PATCH 1/4] platform/x86/amd/pmc: Notify user when platform does not support s0ix transition Shyam Sundar S K
2025-02-17 8:17 ` [PATCH 2/4] platform/x86/amd/pmc: Move macros and structures to the PMC header file Shyam Sundar S K
2025-02-17 8:17 ` [PATCH 3/4] platform/x86/amd/pmc: Remove unnecessary line breaks Shyam Sundar S K
2025-02-17 15:38 ` Mario Limonciello [this message]
2025-02-18 7:08 ` Shyam Sundar S K
2025-02-18 14:52 ` Mario Limonciello
2025-03-05 12:21 ` Ilpo Järvinen
2025-02-17 8:17 ` [PATCH 4/4] platform/x86/amd/pmc: Use managed APIs for mutex Shyam Sundar S K
2025-03-05 12:16 ` Ilpo Järvinen
2025-02-17 15:40 ` [PATCH 1/4] platform/x86/amd/pmc: Notify user when platform does not support s0ix transition Mario Limonciello
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=14d745cd-6c36-4db1-8605-5bb169f8dd80@amd.com \
--to=mario.limonciello@amd.com \
--cc=Sanket.Goswami@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=platform-driver-x86@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox