From: Greg KH <gregkh@linuxfoundation.org>
To: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v3] Staging: rtl8192u: Replace printk() with pr_debug()
Date: Thu, 26 Feb 2015 15:27:17 -0800 [thread overview]
Message-ID: <20150226232717.GA31152@kroah.com> (raw)
In-Reply-To: <1424990950-10390-1-git-send-email-ksenija.stanojevic@gmail.com>
On Thu, Feb 26, 2015 at 11:49:10PM +0100, Ksenija Stanojevic wrote:
> For dynamic debugging netdev_dbg(), dev_dbg() or pr_debug() macro is
> preferred over printk(), which is the raw way to print something.
> Network system has it's own printk format, netdev_dbg, but in this case
> function's argument list has no pointer to a struct netdevice so
> pr_debug is used instead.
> Issue found by checkpatch.pl.
> ---
> v3: Change commit message.
> v2: Include only changes made to this file.
> drivers/staging/rtl8192u/ieee80211/ieee80211_crypt_wep.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
No signed-off-by: Line :(
prev parent reply other threads:[~2015-02-26 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 22:49 [PATCH v3] Staging: rtl8192u: Replace printk() with pr_debug() Ksenija Stanojevic
2015-02-26 23:27 ` Greg KH [this message]
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=20150226232717.GA31152@kroah.com \
--to=gregkh@linuxfoundation.org \
--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.