From: Darren Hart <dvhart@infradead.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 1/5] intel_scu_ipc: fix error path by turning to devm_* / pcim_*
Date: Sat, 10 Oct 2015 21:21:36 -0700 [thread overview]
Message-ID: <20151011042136.GC2958@malice.jf.intel.com> (raw)
In-Reply-To: <1444399896-78599-1-git-send-email-andriy.shevchenko@linux.intel.com>
On Fri, Oct 09, 2015 at 05:11:32PM +0300, Andy Shevchenko wrote:
> The error handling is broken right now since it leaves resources unfreed.
> Convert the code to use managed resources to fix the error handling.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Thanks Andriy,
Please always explicitly Cc LKML.
Is this hardware you able to test explicitly?
> ---
> drivers/platform/x86/intel_scu_ipc.c | 26 ++++++++------------------
> 1 file changed, 8 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/platform/x86/intel_scu_ipc.c b/drivers/platform/x86/intel_scu_ipc.c
> index 187d108..7148535 100644
> --- a/drivers/platform/x86/intel_scu_ipc.c
> +++ b/drivers/platform/x86/intel_scu_ipc.c
...
> - err = pci_request_regions(dev, "intel_scu_ipc");
> + err = pcim_iomap_regions(dev, 1 << 0, pci_name(dev));
> if (err)
> return err;
>
> - base = pci_resource_start(dev, 0);
> - if (!base)
> - return -ENOMEM;
> -
> init_completion(&ipcdev.cmd_complete);
>
> - if (request_irq(dev->irq, ioc, 0, "intel_scu_ipc", &ipcdev))
> - return -EBUSY;
> + err = devm_request_irq(&dev->dev, dev->irq, ioc, 0, "intel_scu_ipc",
You switched to using pci_name(dev) above, seems to me the same rationale should
apply here. Any reason not to use pci_name(dev) here instead of "intel_scu_ipc"?
Thanks,
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-10-11 4:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 14:11 [PATCH 1/5] intel_scu_ipc: fix error path by turning to devm_* / pcim_* Andy Shevchenko
2015-10-09 14:11 ` [PATCH 2/5] intel_scu_ipc: propagate struct intel_scu_ipc_dev Andy Shevchenko
2015-10-09 14:11 ` [PATCH 3/5] intel_scu_ipc: convert to use struct device * Andy Shevchenko
2015-10-09 14:11 ` [PATCH 4/5] intel_scu_ipc: switch to use module_pci_driver() macro Andy Shevchenko
2015-10-11 4:39 ` Darren Hart
2015-10-09 14:11 ` [PATCH 5/5] intel_scu_ipc: move ipclock to struct intel_scu_ipc_dev Andy Shevchenko
2015-10-09 15:21 ` Andy Shevchenko
2015-10-11 4:43 ` Darren Hart
2015-10-12 8:02 ` Andy Shevchenko
2015-10-11 4:21 ` Darren Hart [this message]
2015-10-12 8:00 ` [PATCH 1/5] intel_scu_ipc: fix error path by turning to devm_* / pcim_* Andy Shevchenko
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=20151011042136.GC2958@malice.jf.intel.com \
--to=dvhart@infradead.org \
--cc=andriy.shevchenko@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 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.