The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Petr Mladek <pmladek@suse.com>, <linux-kernel@vger.kernel.org>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>,
	David Howells <dhowells@redhat.com>,
	<linux-afs@lists.infradead.org>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: [PATCH v2 23/33] fs: afs: Use pr_warn instead of pr_warning
Date: Fri, 18 Oct 2019 11:18:40 +0800	[thread overview]
Message-ID: <20191018031850.48498-23-wangkefeng.wang@huawei.com> (raw)
In-Reply-To: <20191018031850.48498-1-wangkefeng.wang@huawei.com>

As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent <prefix>_warn style. Let's do it.

Cc: David Howells <dhowells@redhat.com>
Cc: linux-afs@lists.infradead.org
Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
---
 fs/afs/flock.c     |  4 ++--
 fs/afs/inode.c     | 13 ++++++-------
 fs/afs/yfsclient.c |  4 ++--
 3 files changed, 10 insertions(+), 11 deletions(-)

diff --git a/fs/afs/flock.c b/fs/afs/flock.c
index d5e5a6ddc847..0f2a94ba73cb 100644
--- a/fs/afs/flock.c
+++ b/fs/afs/flock.c
@@ -346,8 +346,8 @@ void afs_lock_work(struct work_struct *work)
 		if (ret < 0) {
 			trace_afs_flock_ev(vnode, NULL, afs_flock_extend_fail,
 					   ret);
-			pr_warning("AFS: Failed to extend lock on {%llx:%llx} error %d\n",
-				   vnode->fid.vid, vnode->fid.vnode, ret);
+			pr_warn("AFS: Failed to extend lock on {%llx:%llx} error %d\n",
+				vnode->fid.vid, vnode->fid.vnode, ret);
 		}
 
 		spin_lock(&vnode->lock);
diff --git a/fs/afs/inode.c b/fs/afs/inode.c
index 46d2d7cb461d..281470fe1183 100644
--- a/fs/afs/inode.c
+++ b/fs/afs/inode.c
@@ -34,8 +34,7 @@ static noinline void dump_vnode(struct afs_vnode *vnode, struct afs_vnode *paren
 {
 	static unsigned long once_only;
 
-	pr_warn("kAFS: AFS vnode with undefined type %u\n",
-		vnode->status.type);
+	pr_warn("kAFS: AFS vnode with undefined type %u\n", vnode->status.type);
 	pr_warn("kAFS: A=%d m=%o s=%llx v=%llx\n",
 		vnode->status.abort_code,
 		vnode->status.mode,
@@ -175,11 +174,11 @@ static void afs_apply_status(struct afs_fs_cursor *fc,
 	BUG_ON(test_bit(AFS_VNODE_UNSET, &vnode->flags));
 
 	if (status->type != vnode->status.type) {
-		pr_warning("Vnode %llx:%llx:%x changed type %u to %u\n",
-			   vnode->fid.vid,
-			   vnode->fid.vnode,
-			   vnode->fid.unique,
-			   status->type, vnode->status.type);
+		pr_warn("Vnode %llx:%llx:%x changed type %u to %u\n",
+			vnode->fid.vid,
+			vnode->fid.vnode,
+			vnode->fid.unique,
+			status->type, vnode->status.type);
 		afs_protocol_error(NULL, -EBADMSG, afs_eproto_bad_status);
 		return;
 	}
diff --git a/fs/afs/yfsclient.c b/fs/afs/yfsclient.c
index 3ee7abf4b2d0..9ac035c17dc4 100644
--- a/fs/afs/yfsclient.c
+++ b/fs/afs/yfsclient.c
@@ -152,8 +152,8 @@ static void yfs_check_req(struct afs_call *call, __be32 *bp)
 		pr_err("kAFS: %s: Request buffer overflow (%zu>%u)\n",
 		       call->type->name, len, call->request_size);
 	else if (len < call->request_size)
-		pr_warning("kAFS: %s: Request buffer underflow (%zu<%u)\n",
-			   call->type->name, len, call->request_size);
+		pr_warn("kAFS: %s: Request buffer underflow (%zu<%u)\n",
+			call->type->name, len, call->request_size);
 }
 
 /*
-- 
2.20.1


  parent reply	other threads:[~2019-10-18  5:05 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191018031710.41052-1-wangkefeng.wang@huawei.com>
2019-10-18  3:18 ` [PATCH v2 01/33] alpha: Use pr_warn instead of pr_warning Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 02/33] arm64: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 03/33] ia64: " Kefeng Wang
2019-10-18 16:35     ` Luck, Tony
2019-10-18  3:18   ` [PATCH v2 04/33] riscv: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 05/33] sh: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 06/33] sparc: " Kefeng Wang
2019-10-18  4:58     ` David Miller
2019-10-18  3:18   ` [PATCH v2 07/33] x86: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 08/33] acpi: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 09/33] drbd: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 10/33] gdrom: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 11/33] clocksource: samsung_pwm_timer: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 12/33] crypto: n2: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 13/33] ide: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 14/33] idsn: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 15/33] macintosh: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 16/33] of: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 17/33] oprofile: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 18/33] platform/x86: eeepc-laptop: " Kefeng Wang
2019-10-18  7:51     ` Andy Shevchenko
2019-10-18  3:18   ` [PATCH v2 19/33] platform/x86: asus-laptop: " Kefeng Wang
2019-10-18  7:51     ` Andy Shevchenko
2019-10-18  3:18   ` [PATCH v2 20/33] platform/x86: intel_oaktrail: " Kefeng Wang
2019-10-18  7:52     ` Andy Shevchenko
2019-10-18  3:18   ` [PATCH v2 21/33] scsi: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 22/33] sh/intc: " Kefeng Wang
2019-10-18  3:18   ` Kefeng Wang [this message]
2019-10-18  3:18   ` [PATCH v2 24/33] vgacon: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 25/33] dma-debug: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 26/33] trace: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 27/33] lib: cpu_rmap: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 28/33] ASoC: samsung: " Kefeng Wang
2019-10-18  8:55     ` Sylwester Nawrocki
2019-10-18  3:18   ` [PATCH v2 29/33] printk: Drop pr_warning Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 30/33] tools lib api: Renaming pr_warning to pr_warn Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 31/33] tools lib bpf: " Kefeng Wang
2019-10-18  4:24     ` Alexei Starovoitov
2019-10-18  7:04       ` Petr Mladek
2019-10-18 18:52         ` Daniel Borkmann
2019-10-21  5:55           ` [bpf-next] " Kefeng Wang
2019-10-21 12:55             ` Daniel Borkmann
2019-10-18  3:18   ` [PATCH v2 32/33] tools perf: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 33/33] checkpatch: Drop pr_warning check Kefeng Wang

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=20191018031850.48498-23-wangkefeng.wang@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=sergey.senozhatsky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox