From: David Miller <davem@davemloft.net>
To: jon.mason@exar.com
Cc: joe@perches.com, Ramkrishna.Vepa@exar.com,
Sreenivasa.Honnur@exar.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] drivers/net/vxge/vxge-main.c: Use pr_<level> and netdev_<level>
Date: Fri, 30 Jul 2010 23:28:22 -0700 (PDT) [thread overview]
Message-ID: <20100730.232822.59674331.davem@davemloft.net> (raw)
In-Reply-To: <20100728032117.GL28630@exar.com>
From: Jon Mason <jon.mason@exar.com>
Date: Tue, 27 Jul 2010 22:21:18 -0500
> On Tue, Jul 27, 2010 at 02:47:03PM -0700, Joe Perches wrote:
>> Use pr_fmt, pr_<level> and netdev_<level> where appropriate.
>>
>> Signed-off-by: Joe Perches <joe@perches.com>
>
> Acked-by: Jon Mason <jon.mason@exar.com>
Applied.
prev parent reply other threads:[~2010-07-31 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 21:47 [PATCH net-next] drivers/net/vxge/vxge-main.c: Use pr_<level> and netdev_<level> Joe Perches
2010-07-28 3:21 ` Jon Mason
2010-07-31 6:28 ` 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=20100730.232822.59674331.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Ramkrishna.Vepa@exar.com \
--cc=Sreenivasa.Honnur@exar.com \
--cc=joe@perches.com \
--cc=jon.mason@exar.com \
--cc=linux-kernel@vger.kernel.org \
--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).