From: Octavian Purdila <octavian.purdila@intel.com>
To: sameo@linux.intel.com, lee.jones@linaro.org
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
johan@kernel.org, Octavian Purdila <octavian.purdila@intel.com>
Subject: [PATCH v4 2/3] mfd: viperboard: switch to devm_ allocation
Date: Thu, 25 Sep 2014 18:41:36 +0300 [thread overview]
Message-ID: <1411659697-27258-3-git-send-email-octavian.purdila@intel.com> (raw)
In-Reply-To: <1411659697-27258-1-git-send-email-octavian.purdila@intel.com>
Switch to using devm_ allocation to simplify the error path. Also
remove a redundant OOM error message.
Signed-off-by: Octavian Purdila <octavian.purdila@intel.com>
---
drivers/mfd/viperboard.c | 23 +++++++----------------
1 file changed, 7 insertions(+), 16 deletions(-)
diff --git a/drivers/mfd/viperboard.c b/drivers/mfd/viperboard.c
index 5f62f4e..0d46d05 100644
--- a/drivers/mfd/viperboard.c
+++ b/drivers/mfd/viperboard.c
@@ -58,17 +58,14 @@ static int vprbrd_probe(struct usb_interface *interface,
int pipe, ret;
/* allocate memory for our device state and initialize it */
- vb = kzalloc(sizeof(*vb), GFP_KERNEL);
- if (vb == NULL) {
- dev_err(&interface->dev, "Out of memory\n");
+ vb = devm_kzalloc(&interface->dev, sizeof(*vb), GFP_KERNEL);
+ if (vb == NULL)
return -ENOMEM;
- }
- vb->buf = kzalloc(sizeof(struct vprbrd_i2c_write_msg), GFP_KERNEL);
- if (vb->buf == NULL) {
- ret = -ENOMEM;
- goto error;
- }
+ vb->buf = devm_kzalloc(&interface->dev,
+ sizeof(struct vprbrd_i2c_write_msg), GFP_KERNEL);
+ if (vb->buf == NULL)
+ return -ENOMEM;
mutex_init(&vb->lock);
@@ -109,11 +106,7 @@ static int vprbrd_probe(struct usb_interface *interface,
return 0;
error:
- if (vb) {
- usb_put_dev(vb->usb_dev);
- kfree(vb->buf);
- kfree(vb);
- }
+ usb_put_dev(vb->usb_dev);
return ret;
}
@@ -125,8 +118,6 @@ static void vprbrd_disconnect(struct usb_interface *interface)
mfd_remove_devices(&interface->dev);
usb_set_intfdata(interface, NULL);
usb_put_dev(vb->usb_dev);
- kfree(vb->buf);
- kfree(vb);
dev_dbg(&interface->dev, "disconnected\n");
}
--
1.9.1
next prev parent reply other threads:[~2014-09-25 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 15:41 [PATCH v4 0/3] mfd: viperboard: fix cache line sharing and cleanups Octavian Purdila
2014-09-25 15:41 ` [PATCH v4 1/3] mfd: viperboard: allocate I/O buffer separately Octavian Purdila
2014-09-25 15:52 ` Johan Hovold
2014-09-25 15:41 ` Octavian Purdila [this message]
2014-09-25 15:53 ` [PATCH v4 2/3] mfd: viperboard: switch to devm_ allocation Johan Hovold
2014-09-25 15:41 ` [PATCH v4 3/3] mfd: viperboard: remove unused platform_device Octavian Purdila
2014-09-25 15:54 ` Johan Hovold
2014-10-09 20:39 ` [PATCH v4 0/3] mfd: viperboard: fix cache line sharing and cleanups Octavian Purdila
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=1411659697-27258-3-git-send-email-octavian.purdila@intel.com \
--to=octavian.purdila@intel.com \
--cc=johan@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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
all inboxes | Powered by JetHome®