From: Jes Sorensen <jes.sorensen@gmail.com>
To: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>,
outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v2] Staging: rtl8192u: Replace printk() with pr_debug()
Date: Mon, 23 Feb 2015 14:57:35 -0500 [thread overview]
Message-ID: <54EB862F.90103@gmail.com> (raw)
In-Reply-To: <1424721379-8173-1-git-send-email-ksenija.stanojevic@gmail.com>
On 02/23/15 14:56, Ksenija Stanojevic wrote:
> For dynamic debugging pr_debug() macro is preferred over printk(), which
> is the raw way to print something. Issue found by checkpatch.pl.
>
> Signed-off-by: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
> ---
> v2: include only changes made to this file.
>
> drivers/staging/rtl8192u/ieee80211/ieee80211_crypt_wep.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Looks good!
Jes
> diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt_wep.c b/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt_wep.c
> index 8c1bf1f..7fab680 100644
> --- a/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt_wep.c
> +++ b/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt_wep.c
> @@ -49,14 +49,14 @@ static void *prism2_wep_init(int keyidx)
>
> priv->tx_tfm = crypto_alloc_blkcipher("ecb(arc4)", 0, CRYPTO_ALG_ASYNC);
> if (IS_ERR(priv->tx_tfm)) {
> - printk(KERN_DEBUG "ieee80211_crypt_wep: could not allocate "
> + pr_debug("ieee80211_crypt_wep: could not allocate "
> "crypto API arc4\n");
> priv->tx_tfm = NULL;
> goto fail;
> }
> priv->rx_tfm = crypto_alloc_blkcipher("ecb(arc4)", 0, CRYPTO_ALG_ASYNC);
> if (IS_ERR(priv->rx_tfm)) {
> - printk(KERN_DEBUG "ieee80211_crypt_wep: could not allocate "
> + pr_debug("ieee80211_crypt_wep: could not allocate "
> "crypto API arc4\n");
> priv->rx_tfm = NULL;
> goto fail;
>
next prev parent reply other threads:[~2015-02-23 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 19:56 [PATCH v2] Staging: rtl8192u: Replace printk() with pr_debug() Ksenija Stanojevic
2015-02-23 19:57 ` Jes Sorensen [this message]
2015-02-26 21:45 ` [Outreachy kernel] " Greg KH
2015-02-26 21:55 ` Ksenija Stanojević
2015-02-26 22:26 ` Greg KH
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=54EB862F.90103@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=ksenija.stanojevic@gmail.com \
--cc=outreachy-kernel@googlegroups.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.