From: Varka Bhadram <varkabhadram@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: netdev@vger.kernel.org, Thomas.Lendacky@amd.com,
geert+renesas@linux-m68k.org, ebiederm@xmission.com,
macro@linux-mips.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, Varka Bhadram <varkab@cdac.in>
Subject: Re: [PATCH net-next v2 3/6] ethernet: amd: dynamic debug fixes
Date: Mon, 14 Jul 2014 13:51:05 +0530 [thread overview]
Message-ID: <53C392F1.7090904@gmail.com> (raw)
In-Reply-To: <1405325166.9132.40.camel@joe-AO725>
On 07/14/2014 01:36 PM, Joe Perches wrote:
> On Mon, 2014-07-14 at 11:55 +0530, varkabhadram@gmail.com wrote:
>> From: Varka Bhadram <varkab@cdac.in>
> []
>> diff --git a/drivers/net/ethernet/amd/amd8111e.c b/drivers/net/ethernet/amd/amd8111e.c
> []
>> @@ -501,8 +501,7 @@ static int amd8111e_restart(struct net_device *dev)
>>
>> /* Enable interrupt coalesce */
>> if(lp->options & OPTION_INTR_COAL_ENABLE){
>> - printk(KERN_INFO "%s: Interrupt Coalescing Enabled.\n",
>> - dev->name);
>> + netdev_info(dev, "Interrupt Coalescing Enabled");
> This needs a terminating newlines.
>
>
OOOps.... I will fix it.
--
Regards,
Varka Bhadram.
next prev parent reply other threads:[~2014-07-14 8:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 6:25 [PATCH net-next v2 0/6] cleanup for AMD811E ethernet driver varkabhadram
2014-07-14 6:25 ` [PATCH net-next v2 1/6] ethernet: amd: move amd111e_remove_one after probe varkabhadram
2014-07-14 6:25 ` [PATCH net-next v2 2/6] ethernet: amd: use devm_ioremap() varkabhadram
2014-07-14 6:25 ` [PATCH net-next v2 3/6] ethernet: amd: dynamic debug fixes varkabhadram
2014-07-14 8:06 ` Joe Perches
2014-07-14 8:21 ` Varka Bhadram [this message]
2014-07-14 6:25 ` [PATCH net-next v2 4/6] ethernet: amd: fix comment styles varkabhadram
2014-07-14 6:25 ` [PATCH net-next v2 5/6] ethernet: amd: fix pci device ids varkabhadram
2014-07-14 17:36 ` Sergei Shtylyov
2014-07-14 6:25 ` [PATCH net-next v2 6/6] ethernet: amd: fix 'foo* bar' varkabhadram
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=53C392F1.7090904@gmail.com \
--to=varkabhadram@gmail.com \
--cc=Thomas.Lendacky@amd.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=geert+renesas@linux-m68k.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=netdev@vger.kernel.org \
--cc=varkab@cdac.in \
/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.