mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Fabian Frederick <fabf@skynet.be>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	tytso <tytso@mit.edu>, akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] fs/devpts/inode.c: convert printk to pr_foo()
Date: Tue, 13 May 2014 09:35:10 -0700	[thread overview]
Message-ID: <1399998910.24350.8.camel@joe-AO725> (raw)
In-Reply-To: <20140513181320.1fbf491f12fab39034ecd702@skynet.be>

On Tue, 2014-05-13 at 18:13 +0200, Fabian Frederick wrote:
> Also convert spaces to tabs (checkpatch warnings)
[]
> diff --git a/fs/devpts/inode.c b/fs/devpts/inode.c
[]

It may be better to add a #define pr_fmt

> @@ -225,7 +225,7 @@ static int parse_mount_options(char *data, int op, struct pts_mount_opts *opts)
>  			break;
>  #endif
>  		default:
> -			printk(KERN_ERR "devpts: called with bogus options\n");
> +			pr_err("devpts: called with bogus options\n");

and remove all the embedded "devpts: "

> @@ -261,7 +261,7 @@ static int mknod_ptmx(struct super_block *sb)
>  
>  	dentry = d_alloc_name(root, "ptmx");
>  	if (!dentry) {
> -		printk(KERN_NOTICE "Unable to alloc dentry for ptmx node\n");
> +		pr_notice("Unable to alloc dentry for ptmx node\n");
>  		goto out;
>  	}
>  
> @@ -270,7 +270,7 @@ static int mknod_ptmx(struct super_block *sb)
>  	 */
>  	inode = new_inode(sb);
>  	if (!inode) {
> -		printk(KERN_ERR "Unable to alloc inode for ptmx node\n");
> +		pr_err("Unable to alloc inode for ptmx node\n");
>  		dput(dentry);
>  		goto out;
>  	}

Adding pr_fmt would prefix these.

It seems odd that one of these is an err and the other a notice.



      reply	other threads:[~2014-05-13 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 16:13 Fabian Frederick
2014-05-13 16:35 ` Joe Perches [this message]

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=1399998910.24350.8.camel@joe-AO725 \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=fabf@skynet.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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®