From: David Miller <davem@davemloft.net>
To: chenweilong@huawei.com
Cc: alex.bluesman.smirnov@gmail.com, dbaryshkov@gmail.com,
linux-zigbee-devel@lists.sourceforge.net, netdev@vger.kernel.org,
dingtianhong@huawei.com
Subject: Re: [PATCH] mac802154: Use pr_err(...) rather than printk(KERN_ERR ...)
Date: Wed, 30 Oct 2013 17:06:10 -0400 (EDT) [thread overview]
Message-ID: <20131030.170610.231481031187411692.davem@davemloft.net> (raw)
In-Reply-To: <1383118087-10128-1-git-send-email-chenweilong@huawei.com>
From: Chen Weilong <chenweilong@huawei.com>
Date: Wed, 30 Oct 2013 15:28:07 +0800
> This change is inspired by checkpatch.
>
> Signed-off-by: Weilong Chen <chenweilong@huawei.com>
Applied to net-next, thanks.
prev parent reply other threads:[~2013-10-30 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 7:28 [PATCH] mac802154: Use pr_err(...) rather than printk(KERN_ERR ...) Chen Weilong
2013-10-30 21:06 ` David Miller [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=20131030.170610.231481031187411692.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=chenweilong@huawei.com \
--cc=dbaryshkov@gmail.com \
--cc=dingtianhong@huawei.com \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).