From: vkolluri <vkolluri@cisco.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>
Subject: Re: [next-next-2.6 PATCH] enic: Add support to configure hardware interrupt coalesce timers in a platform independent way
Date: Fri, 17 Jun 2011 10:27:50 -0700 [thread overview]
Message-ID: <CA20DCA6.5F74%vkolluri@cisco.com> (raw)
In-Reply-To: <20110616.235715.2076846351080666905.davem@davemloft.net>
I'll fix and resubmit.
Thanks
Vasanthy
On 6/16/11 8:57 PM, "David Miller" <davem@davemloft.net> wrote:
> From: Vasanthy Kolluri <vkolluri@cisco.com>
> Date: Wed, 15 Jun 2011 14:17:58 -0700
>
>> + /* Get interrupt coalesce timer info
>> + */
>> +
>> + err = enic_dev_intr_coal_timer_info(enic);
>
> Please, comment should be just one line long and empty
> line is superflous.
next prev parent reply other threads:[~2011-06-17 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 21:17 [next-next-2.6 PATCH] enic: Add support to configure hardware interrupt coalesce timers in a platform independent way Vasanthy Kolluri
2011-06-17 3:57 ` David Miller
2011-06-17 17:27 ` vkolluri [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-17 17:56 Vasanthy Kolluri
2011-06-17 19:25 ` David Miller
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=CA20DCA6.5F74%vkolluri@cisco.com \
--to=vkolluri@cisco.com \
--cc=davem@davemloft.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).