From: Jonathan Cameron <jic23@cam.ac.uk>
To: anish <anish198519851985@gmail.com>
Cc: gregkh@suse.de, manuel.stahl@iis.fraunhofer.de,
lucas.demarchi@profusion.mobi, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
Linux I2C <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH] staging iio: Replace kmalloc with local variable
Date: Tue, 07 Jun 2011 14:00:23 +0100 [thread overview]
Message-ID: <4DEE20E7.4020008@cam.ac.uk> (raw)
In-Reply-To: <1307450354.1516.23.camel@anish-desktop>
On 06/07/11 13:39, anish wrote:
> From: anish kumar <anish198519851985@gmail.com>
>
> replaced kmalloc with local variable as I2C(in this case) doesn't require
> kmalloc memory it can do with stack memory.
I've cc'd linux-i2c just to check I'm right about the whole i2c doesn't need
dma safe buffers bit...
>
> Signed-off-by: anish kumar <anish198519851985@gmail.com>
Acked-by: Jonathan Cameron <jic23@cam.ac.uk>
> ---
> drivers/staging/iio/adc/max1363_core.c | 5 +----
> 1 files changed, 1 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/iio/adc/max1363_core.c b/drivers/staging/iio/adc/max1363_core.c
> index 1037087..9462230 100644
> --- a/drivers/staging/iio/adc/max1363_core.c
> +++ b/drivers/staging/iio/adc/max1363_core.c
> @@ -207,15 +207,12 @@ static int max1363_write_basic_config(struct i2c_client *client,
> unsigned char d2)
> {
> int ret;
> - u8 *tx_buf = kmalloc(2, GFP_KERNEL);
> + u8 tx_buf[2];
>
> - if (!tx_buf)
> - return -ENOMEM;
> tx_buf[0] = d1;
> tx_buf[1] = d2;
>
> ret = i2c_master_send(client, tx_buf, 2);
> - kfree(tx_buf);
>
> return (ret > 0) ? 0 : ret;
> }
next prev parent reply other threads:[~2011-06-07 12:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 12:39 [PATCH] staging iio: Replace kmalloc with local variable anish
2011-06-07 13:00 ` Jonathan Cameron [this message]
2011-06-07 13:41 ` Ben Dooks
2011-06-07 13:54 ` Jonathan Cameron
2011-06-07 14:04 ` Hennerich, Michael
2011-06-07 14:02 ` Jean Delvare
[not found] ` <BANLkTim5-ZKXtDkSQyHAJ9-iKtOPsJ917A@mail.gmail.com>
[not found] ` <BANLkTi=e0A2G-d+t4VF5V0gj+eNoh3KRnQ@mail.gmail.com>
2011-06-09 8:29 ` Jean Delvare
[not found] ` <BANLkTimq_5rmB+UkaxZwrOtV-ZF3+fEOgQ@mail.gmail.com>
2011-06-09 8:48 ` Jonathan Cameron
2011-06-09 10:46 ` Jonathan Cameron
[not found] ` <BANLkTik4Tfd73iKcDsXK-sfy6_ADVX4oYA@mail.gmail.com>
2011-06-09 14:51 ` Jonathan Cameron
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=4DEE20E7.4020008@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=anish198519851985@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=manuel.stahl@iis.fraunhofer.de \
/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