From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 0/5] trivial blank line at end of file cleanup
Date: Wed, 10 Apr 2019 11:05:32 -0700 [thread overview]
Message-ID: <20190410180537.14226-1-stephen@networkplumber.org> (raw)
Ran script that looks for extra whitespace (what git and checkpatch
complain about). Found several trival cases of extra line at
end of file.
Stephen Hemminger (5):
vhost: eliminate blank line at EOF
net/atlantic: remove extra blank line at EOF
bus/fslmc: remove blank line at EOF
raw/ifpga_rawdev: remove blank line at EOF
net/qede: remove blank line at EOF
drivers/bus/fslmc/rte_bus_fslmc_version.map | 1 -
drivers/net/atlantic/atl_ethdev.c | 1 -
drivers/net/atlantic/atl_rxtx.c | 1 -
drivers/net/atlantic/hw_atl/hw_atl_b0.c | 1 -
drivers/net/qede/qede_filter.c | 1 -
drivers/raw/ifpga_rawdev/base/ifpga_feature_dev.c | 1 -
drivers/raw/ifpga_rawdev/ifpga_rawdev.c | 1 -
lib/librte_vhost/iotlb.c | 1 -
8 files changed, 8 deletions(-)
--
2.17.1
next reply other threads:[~2019-04-10 18:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 18:05 Stephen Hemminger [this message]
2019-04-10 18:05 ` Stephen Hemminger
2019-04-10 18:05 ` [dpdk-dev] [PATCH 1/5] vhost: eliminate blank line at EOF Stephen Hemminger
2019-04-10 18:05 ` Stephen Hemminger
2019-04-10 18:05 ` [dpdk-dev] [PATCH 2/5] net/atlantic: remove extra " Stephen Hemminger
2019-04-10 18:05 ` Stephen Hemminger
2019-04-10 18:05 ` [dpdk-dev] [PATCH 3/5] bus/fslmc: remove " Stephen Hemminger
2019-04-10 18:05 ` Stephen Hemminger
2019-04-10 18:05 ` [dpdk-dev] [PATCH 4/5] raw/ifpga_rawdev: " Stephen Hemminger
2019-04-10 18:05 ` Stephen Hemminger
2019-04-10 18:05 ` [dpdk-dev] [PATCH 5/5] net/qede: " Stephen Hemminger
2019-04-10 18:05 ` Stephen Hemminger
2019-04-22 11:37 ` [dpdk-dev] [PATCH 0/5] trivial blank line at end of file cleanup Thomas Monjalon
2019-04-22 11:37 ` 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=20190410180537.14226-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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).