All of lore.kernel.org
 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>,
	Robert Richter <rric@kernel.org>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: [PATCH v2 17/33] oprofile: Use pr_warn instead of pr_warning
Date: Fri, 18 Oct 2019 11:18:34 +0800	[thread overview]
Message-ID: <20191018031850.48498-17-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: Robert Richter <rric@kernel.org>
Acked-by: Robert Richter <rric@kernel.org>
Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
---
 drivers/oprofile/oprofile_perf.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/oprofile/oprofile_perf.c b/drivers/oprofile/oprofile_perf.c
index 4b150a754890..98a63a5f8763 100644
--- a/drivers/oprofile/oprofile_perf.c
+++ b/drivers/oprofile/oprofile_perf.c
@@ -46,8 +46,8 @@ static void op_overflow_handler(struct perf_event *event,
 	if (id != num_counters)
 		oprofile_add_sample(regs, id);
 	else
-		pr_warning("oprofile: ignoring spurious overflow "
-				"on cpu %u\n", cpu);
+		pr_warn("oprofile: ignoring spurious overflow on cpu %u\n",
+			cpu);
 }
 
 /*
@@ -88,8 +88,8 @@ static int op_create_counter(int cpu, int event)
 
 	if (pevent->state != PERF_EVENT_STATE_ACTIVE) {
 		perf_event_release_kernel(pevent);
-		pr_warning("oprofile: failed to enable event %d "
-				"on CPU %d\n", event, cpu);
+		pr_warn("oprofile: failed to enable event %d on CPU %d\n",
+			event, cpu);
 		return -EBUSY;
 	}
 
-- 
2.20.1


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

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18  3:17 [PATCH v2 00/33] Kill pr_warning in the whole linux code Kefeng Wang
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     ` Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 16/33] of: " Kefeng Wang
2019-10-18  3:18   ` Kefeng Wang [this message]
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   ` [PATCH v2 23/33] fs: afs: " Kefeng Wang
2019-10-18  3:18   ` [PATCH v2 24/33] vgacon: " Kefeng Wang
2019-10-18  3:18     ` 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
2019-10-18 14:26 ` [PATCH v2 00/33] Kill pr_warning in the whole linux code Petr Mladek
2019-10-18 15:22   ` Christoph Hellwig
2019-10-18 15:36     ` Joe Perches

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-17-wangkefeng.wang@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rric@kernel.org \
    --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 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.