From: Eva Rachel Retuya <eraretuya@gmail.com>
To: "pooja.shamili" <poojashamili@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] staging: mt29f_spinand: Replacing pr_info with dev_info after the call to devm_kzalloc
Date: Sat, 5 Mar 2016 16:00:20 +0800 [thread overview]
Message-ID: <20160305080019.GA28126@Socrates-Mint> (raw)
In-Reply-To: <20160303170735.GA3773@localhost>
On Thu, Mar 03, 2016 at 10:37:35PM +0530, pooja.shamili wrote:
> The function devm_kzalloc has a first argument of type struct device *.
> This is the type of argument required by printing functions such as
> dev_info, dev_err, etc. Thus, functions like pr_info should not normally
> be used after a call to devm_kzalloc. Thus, all pr_info occurances are
> replaced with dev_info function calls.
>
> This was done using Coccinelle, the patch being:
> @@
> expression E1,E2;
> expression list args;
> @@
>
> E1 = devm_kzalloc(E2, ...);
> <...
> - pr_info(
> + dev_info(E2,
> args);
> ...>
>
> Signed-off-by: pooja.shamili <poojashamili@gmail.com>
> ---
> drivers/staging/mt29f_spinand/mt29f_spinand.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/mt29f_spinand/mt29f_spinand.c b/drivers/staging/mt29f_spinand/mt29f_spinand.c
> index 75fe61c..791e36f 100644
> --- a/drivers/staging/mt29f_spinand/mt29f_spinand.c
> +++ b/drivers/staging/mt29f_spinand/mt29f_spinand.c
> @@ -893,7 +893,8 @@ static int spinand_probe(struct spi_device *spi_nand)
> #else
> chip->ecc.mode = NAND_ECC_SOFT;
> if (spinand_disable_ecc(spi_nand) < 0)
> - pr_info("%s: disable ecc failed!\n", __func__);
> + dev_info(&spi_nand->dev, "%s: disable ecc failed!\n",
> + __func__);
> #endif
>
> nand_set_flash_node(chip, spi_nand->dev.of_node);
> --
> 2.1.4
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20160303170735.GA3773%40localhost.
> For more options, visit https://groups.google.com/d/optout.
Hello Pooja,
I'm also working on the semantic patch you presented here but I'm aiming
for the "extended" one. I'm using this driver to test my patch -- other
than what you have changed, I suggest you also convert the other pr_
calls on this driver even if it's by hand and add that to your commit
message. I think there are only 2 left, for consistency purposes.
Eva
next prev parent reply other threads:[~2016-03-05 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 17:07 [PATCH] staging: mt29f_spinand: Replacing pr_info with dev_info after the call to devm_kzalloc pooja.shamili
2016-03-05 8:00 ` Eva Rachel Retuya [this message]
2016-03-05 8:27 ` [Outreachy kernel] " Julia Lawall
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=20160305080019.GA28126@Socrates-Mint \
--to=eraretuya@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=poojashamili@gmail.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 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.