From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Sam Muhammed <jane.pnx9@gmail.com>
Cc: outreachy-kernel@googlegroups.com,
William Hubbs <w.d.hubbs@gmail.com>,
Chris Brannon <chris@the-brannons.com>,
Kirk Reiser <kirk@reisers.ca>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] Staging: speakup: Use pr_warn() defined in <linux/printk.h>.
Date: Sun, 22 Mar 2020 15:35:16 +0100 [thread overview]
Message-ID: <20200322143516.wsekmcsreziw5tvo@function> (raw)
In-Reply-To: <20200322143322.29098-1-jane.pnx9@gmail.com>
Sam Muhammed, le dim. 22 mars 2020 10:33:22 -0400, a ecrit:
> Dropping a user-defined pr_warn() and using the kernel
> message printing functions implemented in <linux/printk.h>.
>
> Since both have the same functionality, using the standard
> kernel functions is better.
>
> Signed-off-by: Sam Muhammed <jane.pnx9@gmail.com>
Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
Thanks!
> ---
> drivers/staging/speakup/spk_priv.h | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/speakup/spk_priv.h b/drivers/staging/speakup/spk_priv.h
> index ac6a74883af4..c75b40838794 100644
> --- a/drivers/staging/speakup/spk_priv.h
> +++ b/drivers/staging/speakup/spk_priv.h
> @@ -11,13 +11,11 @@
> #ifndef _SPEAKUP_PRIVATE_H
> #define _SPEAKUP_PRIVATE_H
>
> +#include <linux/printk.h>
> +
> #include "spk_types.h"
> #include "spk_priv_keyinfo.h"
>
> -#ifndef pr_warn
> -#define pr_warn(fmt, arg...) printk(KERN_WARNING fmt, ##arg)
> -#endif
> -
> #define V_LAST_VAR { MAXVARS }
> #define SPACE 0x20
> #define SYNTH_CHECK 20030716 /* today's date ought to do for check value */
> ---
> 2.20.1
>
next prev parent reply other threads:[~2020-03-22 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 14:33 [PATCH] Staging: speakup: Use pr_warn() defined in <linux/printk.h> Sam Muhammed
2020-03-22 14:35 ` Samuel Thibault [this message]
2020-03-22 14:47 ` [Outreachy kernel] " Sam Muhammed
2020-03-22 14:54 ` Julia Lawall
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=20200322143516.wsekmcsreziw5tvo@function \
--to=samuel.thibault@ens-lyon.org \
--cc=chris@the-brannons.com \
--cc=gregkh@linuxfoundation.org \
--cc=jane.pnx9@gmail.com \
--cc=kirk@reisers.ca \
--cc=outreachy-kernel@googlegroups.com \
--cc=w.d.hubbs@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.