public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Pablo Vazquez Rodriguez <peibolvigo@gmail.com>
Cc: greg@kroah.com, swetland@google.com, john.stultz@linaro.org,
	arve@android.com, ccross@android.com, bringert@android.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: android: fix pr_info and pr_err coding style issues in ashmem.c
Date: Fri, 29 Jun 2012 09:37:52 -0700	[thread overview]
Message-ID: <1340987872.6562.47.camel@joe2Laptop> (raw)
In-Reply-To: <1340987232-25169-1-git-send-email-peibolvigo@gmail.com>

On Fri, 2012-06-29 at 18:27 +0200, Pablo Vazquez Rodriguez wrote:
> This is a patch to the ashmem.c file that fixes up several pr_info and pr_err warnings found by the checkpath.pl tool
[]
> diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c
[]
> @@ -707,7 +707,7 @@ static int __init ashmem_init(void)

Try adding
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
before any other #include

>  					  sizeof(struct ashmem_area),
>  					  0, 0, NULL);
>  	if (unlikely(!ashmem_area_cachep)) {
> -		printk(KERN_ERR "ashmem: failed to create slab cache\n");
> +		pr_err("ashmem: failed to create slab cache\n");

these then become
		pr_err("failed to create slab cache\n");

> @@ -715,19 +715,19 @@ static int __init ashmem_init(void)
> +		pr_err("ashmem: failed to create slab cache\n");
		pr_err("failed to create slab cache\n");
[]
> +		pr_err("ashmem: failed to register misc device!\n");
		pr_err("failed ...");

etc.



  reply	other threads:[~2012-06-29 16:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29 16:27 [PATCH] Staging: android: fix pr_info and pr_err coding style issues in ashmem.c Pablo Vazquez Rodriguez
2012-06-29 16:37 ` Joe Perches [this message]
     [not found] ` <CAJ6TP82bM4d+pAc-+w_Y934FgBz5sQoyHm118s39GH5tf3TkJA@mail.gmail.com>
2012-07-06 23:16   ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2012-07-07  1:06 Pablo Vazquez Rodriguez

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=1340987872.6562.47.camel@joe2Laptop \
    --to=joe@perches.com \
    --cc=arve@android.com \
    --cc=bringert@android.com \
    --cc=ccross@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peibolvigo@gmail.com \
    --cc=swetland@google.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