From: "Zhang, Helin" <helin.zhang@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Stephen Hemminger <shemming@brocade.com>
Subject: Re: [dpdk-dev] [PATCH 9/9] drivers: fix whitespace
Date: Fri, 5 Jun 2015 02:59:36 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A870EB1@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1433429007-4640-10-git-send-email-stephen@networkplumber.org>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen Hemminger
> Sent: Thursday, June 4, 2015 10:43 PM
> To: dev@dpdk.org
> Cc: Stephen Hemminger
> Subject: [dpdk-dev] [PATCH 9/9] drivers: fix whitespace
>
> From: Stephen Hemminger <shemming@brocade.com>
>
> Note: ignored whitespace issues in base (external code).
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Helin Zhang <helin.zhang@intel.com>
> ---
> drivers/net/e1000/em_rxtx.c | 1 -
> drivers/net/e1000/igb_rxtx.c | 1 -
> drivers/net/pcap/rte_eth_pcap.c | 2 +-
> 3 files changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/net/e1000/em_rxtx.c b/drivers/net/e1000/em_rxtx.c index
> 3a79e8b..fdc825f 100644
> --- a/drivers/net/e1000/em_rxtx.c
> +++ b/drivers/net/e1000/em_rxtx.c
> @@ -1862,4 +1862,3 @@ eth_em_tx_init(struct rte_eth_dev *dev)
> /* This write will effectively turn on the transmit unit. */
> E1000_WRITE_REG(hw, E1000_TCTL, tctl); }
> -
> diff --git a/drivers/net/e1000/igb_rxtx.c b/drivers/net/e1000/igb_rxtx.c index
> f586311..43d6703 100644
> --- a/drivers/net/e1000/igb_rxtx.c
> +++ b/drivers/net/e1000/igb_rxtx.c
> @@ -2394,4 +2394,3 @@ eth_igbvf_tx_init(struct rte_eth_dev *dev)
> }
>
> }
> -
> diff --git a/drivers/net/pcap/rte_eth_pcap.c b/drivers/net/pcap/rte_eth_pcap.c
> index ff9b534..a6ed5bd 100644
> --- a/drivers/net/pcap/rte_eth_pcap.c
> +++ b/drivers/net/pcap/rte_eth_pcap.c
> @@ -760,7 +760,7 @@ rte_pmd_init_internals(const char *name, const unsigned
> nb_rx_queues,
>
> return 0;
>
> -error:
> +error:
> rte_free(data);
> rte_free(pci_dev);
> rte_free(*internals);
> --
> 2.1.4
next prev parent reply other threads:[~2015-06-05 3:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 14:43 [dpdk-dev] [PATCH 0/9] whitespace cleanups Stephen Hemminger
2015-06-04 14:43 ` [dpdk-dev] [PATCH 1/9] kni: fix whitespace Stephen Hemminger
2015-06-04 14:51 ` Thomas Monjalon
2015-06-05 3:00 ` Zhang, Helin
2015-06-05 2:58 ` Zhang, Helin
2015-06-04 14:43 ` [dpdk-dev] [PATCH 2/9] eal: " Stephen Hemminger
2015-06-04 14:43 ` [dpdk-dev] [PATCH 3/9] cmdline: " Stephen Hemminger
2015-06-04 14:43 ` [dpdk-dev] [PATCH 4/9] vhost: fix trailing whitespace Stephen Hemminger
2015-06-04 14:43 ` [dpdk-dev] [PATCH 5/9] lib: fix misc whitespace Stephen Hemminger
2015-06-04 14:43 ` [dpdk-dev] [PATCH 6/9] app: fix whitespace Stephen Hemminger
2015-06-04 14:43 ` [dpdk-dev] [PATCH 7/9] examples: " Stephen Hemminger
2015-06-04 14:43 ` [dpdk-dev] [PATCH 8/9] mk, scripts: remove useless blank lines Stephen Hemminger
2015-06-04 14:43 ` [dpdk-dev] [PATCH 9/9] drivers: fix whitespace Stephen Hemminger
2015-06-05 2:59 ` Zhang, Helin [this message]
2015-06-11 15:37 ` [dpdk-dev] [PATCH 0/9] whitespace cleanups Thomas Monjalon
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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A870EB1@SHSMSX104.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=shemming@brocade.com \
--cc=stephen@networkplumber.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).