From: Stephen Hemminger <stephen@networkplumber.org>
To: Vlad Zolotarov <vladz@cloudius-systems.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1 5/5] ixgbe: Add LRO support
Date: Wed, 4 Mar 2015 10:51:51 -0800 [thread overview]
Message-ID: <20150304105151.0a6f0553@urahara> (raw)
In-Reply-To: <54F6BB6A.5080205@cloudius-systems.com>
On Wed, 04 Mar 2015 09:59:38 +0200
Vlad Zolotarov <vladz@cloudius-systems.com> wrote:
> > Checkpatch warnings (edited to remove ones that should be ok)
>
> I was unaware that checkpatch rules apply here - at least looking at the
> current code it looks like it... ;)
> But I'm all for it! I'll fix all the issues and respin
Checkpatch doesn't generally have to apply. But is good and useful tool
to find obvious style gaffs.
Just don't let it rule your world
prev parent reply other threads:[~2015-03-04 18:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 19:48 [dpdk-dev] [PATCH v1 0/5]: Add LRO support to ixgbe PMD Vlad Zolotarov
2015-03-03 19:48 ` [dpdk-dev] [PATCH v1 1/5] ixgbe: Cleanups Vlad Zolotarov
2015-03-03 19:48 ` [dpdk-dev] [PATCH v1 2/5] ixgbe: Bug fix: Properly configure Rx CRC stripping for x540 devices Vlad Zolotarov
2015-03-03 19:48 ` [dpdk-dev] [PATCH v1 3/5] ixgbe: Code refactoring Vlad Zolotarov
2015-03-03 19:48 ` [dpdk-dev] [PATCH v1 4/5] common_linuxapp: Added CONFIG_RTE_ETHDEV_LRO_SUPPORT option Vlad Zolotarov
2015-03-03 19:48 ` [dpdk-dev] [PATCH v1 5/5] ixgbe: Add LRO support Vlad Zolotarov
2015-03-04 0:33 ` Stephen Hemminger
2015-03-04 7:24 ` Vlad Zolotarov
2015-03-04 0:33 ` Stephen Hemminger
2015-03-04 7:57 ` Vlad Zolotarov
2015-03-04 18:54 ` Stephen Hemminger
2015-03-05 9:36 ` Vlad Zolotarov
2015-03-04 8:05 ` Avi Kivity
2015-03-04 0:34 ` Stephen Hemminger
2015-03-04 7:57 ` Vlad Zolotarov
2015-03-04 0:36 ` Stephen Hemminger
2015-03-04 7:59 ` Vlad Zolotarov
2015-03-04 18:51 ` Stephen Hemminger [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=20150304105151.0a6f0553@urahara \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=vladz@cloudius-systems.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 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).