From: Martin Kelly <martin@martingkelly.com>
To: "Li, Aubrey" <aubrey.li@linux.intel.com>,
x86@kernel.org, mingo@redhat.com
Cc: vishwesh.m.rudramuni@intel.com, joe@perches.com,
hpa@linux.intel.com, linux-kernel@vger.kernel.org,
Martin Kelly <martkell@amazon.com>
Subject: Re: [PATCH v2] x86/pmc_atom: Fix warning when CONFIG_DEBUG_FS=n
Date: Tue, 16 Sep 2014 20:20:12 -0700 [thread overview]
Message-ID: <5418FDEC.40201@martingkelly.com> (raw)
In-Reply-To: <5418ED4A.2030607@linux.intel.com>
On 09/16/2014 07:09 PM, Li, Aubrey wrote:
>
> Thanks to take care of this warning. How about this version?
>
> diff --git a/arch/x86/kernel/pmc_atom.c b/arch/x86/kernel/pmc_atom.c
> index 0c424a6..cd91b57 100644
> --- a/arch/x86/kernel/pmc_atom.c
> +++ b/arch/x86/kernel/pmc_atom.c
> @@ -240,7 +240,7 @@ err:
> static int pmc_setup_dev(struct pci_dev *pdev)
> {
> struct pmc_dev *pmc = &pmc_device;
> - int ret;
> + int ret = 0;
>
> /* Obtain ACPI base address */
> pci_read_config_dword(pdev, ACPI_BASE_ADDR_OFFSET, &acpi_base_addr);
> @@ -269,7 +269,7 @@ static int pmc_setup_dev(struct pci_dev *pdev)
> return ret;
> }
> #endif /* CONFIG_DEBUG_FS */
> - return 0;
> + return ret;
> }
>
> /*
>
> Thanks,
> -Aubrey
>
Thanks for the suggestion, Aubrey. Although that version would also work, it still has inline #ifdef, which is harder to read and goes against general Linux conventions:
https://www.kernel.org/doc/Documentation/SubmittingPatches
(section 2, "#ifdefs are ugly")
next prev parent reply other threads:[~2014-09-17 3:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 0:49 [PATCH v2] x86/pmc_atom: Fix warning when CONFIG_DEBUG_FS=n Martin Kelly
2014-09-17 2:09 ` Li, Aubrey
2014-09-17 3:20 ` Martin Kelly [this message]
2014-09-17 3:44 ` Li, Aubrey
2014-09-17 4:04 ` Martin Kelly
2014-09-17 12:24 ` Ingo Molnar
2014-09-17 14:19 ` Martin Kelly
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=5418FDEC.40201@martingkelly.com \
--to=martin@martingkelly.com \
--cc=aubrey.li@linux.intel.com \
--cc=hpa@linux.intel.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martkell@amazon.com \
--cc=mingo@redhat.com \
--cc=vishwesh.m.rudramuni@intel.com \
--cc=x86@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.