From: Greg KH <gregkh@linuxfoundation.org>
To: "Hatice ERTÜRK" <haticeerturk27@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] Staging: rtl8192u: ieee80211: pr_warn instead printk
Date: Fri, 6 Mar 2015 15:51:05 -0800 [thread overview]
Message-ID: <20150306235105.GA26968@kroah.com> (raw)
In-Reply-To: <1425578480-7151-1-git-send-email-haticeerturk27@gmail.com>
On Thu, Mar 05, 2015 at 08:01:20PM +0200, Hatice ERT�RK wrote:
> This patch fixes the following warning using checkpatch.pl
> WARNING: Prefer [subsystem eg: netdev]_warn([subsystem]dev, ... then
> dev_warn(dev, ... then pr_warn(... to printk(KERN_WARNING ...
>
> Signed-off-by: Hatice ERTURK <haticeerturk27@gmail.com>
> ---
> drivers/staging/rtl8192u/ieee80211/ieee80211_tx.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_tx.c b/drivers/staging/rtl8192u/ieee80211/ieee80211_tx.c
> index ff6b212..ecd8542 100644
> --- a/drivers/staging/rtl8192u/ieee80211/ieee80211_tx.c
> +++ b/drivers/staging/rtl8192u/ieee80211/ieee80211_tx.c
> @@ -197,7 +197,7 @@ int ieee80211_encrypt_fragment(
> struct ieee80211_hdr_3addrqos *header;
>
> header = (struct ieee80211_hdr_3addrqos *)frag->data;
> - pr_debug(KERN_DEBUG "%s: TKIP countermeasures: dropped "
> + dev_debug(KERN_DEBUG "%s: TKIP countermeasures: dropped "
This obviously will not even build.
Please test all of your patches, to not do so can cause a lot of time
being wasted by others.
thanks,
greg k-h
next prev parent reply other threads:[~2015-03-07 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 18:01 [PATCH] Staging: rtl8192u: ieee80211: pr_warn instead printk Hatice ERTÜRK
2015-03-06 23:51 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-05 17:34 Hatice ERTÜRK
2015-03-05 17:45 ` [Outreachy kernel] " 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=20150306235105.GA26968@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=haticeerturk27@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.