mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: wangkefeng.wang@huawei.com
Cc: pmladek@suse.com, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, sergey.senozhatsky@gmail.com
Subject: Re: [PATCH v2 06/33] sparc: Use pr_warn instead of pr_warning
Date: Thu, 17 Oct 2019 21:58:04 -0700 (PDT)	[thread overview]
Message-ID: <20191017.215804.307604979788731139.davem@davemloft.net> (raw)
In-Reply-To: <20191018031850.48498-6-wangkefeng.wang@huawei.com>

From: Kefeng Wang <wangkefeng.wang@huawei.com>
Date: Fri, 18 Oct 2019 11:18:23 +0800

> 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 S. Miller" <davem@davemloft.net>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>

Acked-by: David S. Miller <davem@davemloft.net>

  reply	other threads:[~2019-10-18  4:58 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: " 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 [this message]
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   ` [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   ` [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=20191017.215804.307604979788731139.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=wangkefeng.wang@huawei.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

all inboxes | Powered by JetHome®