From: Petr Mladek <pmladek@suse.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: joe@perches.com, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, tj@kernel.org, arnd@arndb.de,
sergey.senozhatsky@gmail.com, rostedt@goodmis.org
Subject: Re: [PATCH 2/4] staging: isdn: gigaset: Use pr_warn instead of pr_warning
Date: Fri, 29 Nov 2019 12:49:36 +0100 [thread overview]
Message-ID: <20191129114936.x53gaief2vz3o7vn@pathway.suse.cz> (raw)
In-Reply-To: <20191128004752.35268-3-wangkefeng.wang@huawei.com>
On Thu 2019-11-28 08:47:50, Kefeng Wang wrote:
> Use pr_warn() instead of the remaining pr_warning() calls.
>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> ---
> drivers/staging/isdn/gigaset/interface.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/isdn/gigaset/interface.c b/drivers/staging/isdn/gigaset/interface.c
> index 17fa615a8c68..9ddadd07e707 100644
> --- a/drivers/staging/isdn/gigaset/interface.c
> +++ b/drivers/staging/isdn/gigaset/interface.c
> @@ -518,7 +518,7 @@ void gigaset_if_init(struct cardstate *cs)
> if (!IS_ERR(cs->tty_dev))
> dev_set_drvdata(cs->tty_dev, cs);
> else {
> - pr_warning("could not register device to the tty subsystem\n");
> + pr_warn("could not register device to the tty subsystem\n");
This patch has reached mainline via the staging tree in the meantime.
Best Regards,
Petr
next prev parent reply other threads:[~2019-11-29 11:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 0:47 [PATCH 0/4] part2: kill pr_warning from kernel Kefeng Wang
2019-11-28 0:47 ` [PATCH 1/4] workqueue: Use pr_warn instead of pr_warning Kefeng Wang
2019-12-02 18:00 ` Tejun Heo
2019-11-28 0:47 ` [PATCH 2/4] staging: isdn: gigaset: " Kefeng Wang
2019-11-29 11:49 ` Petr Mladek [this message]
2019-11-28 0:47 ` [PATCH 3/4] printk: Drop pr_warning definition Kefeng Wang
2019-11-28 7:14 ` kbuild test robot
2019-11-29 11:53 ` Petr Mladek
2019-11-30 9:03 ` [kbuild-all] " Philip Li
2019-12-03 9:15 ` Petr Mladek
2019-11-28 0:47 ` [PATCH 4/4] checkpatch: Drop pr_warning check Kefeng Wang
2019-11-28 1:05 ` Joe Perches
2019-11-29 11:58 ` [PATCH 0/4] part2: kill pr_warning from kernel Petr Mladek
2019-11-29 12:56 ` 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=20191129114936.x53gaief2vz3o7vn@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=tj@kernel.org \
--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
Powered by JetHome