DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/5] trivial blank line at end of file cleanup
Date: Mon, 22 Apr 2019 13:37:37 +0200	[thread overview]
Message-ID: <6034278.LiO6WW6BUP@xps> (raw)
In-Reply-To: <20190410180537.14226-1-stephen@networkplumber.org>

10/04/2019 20:05, Stephen Hemminger:
> 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

Squashed in one patch and applied, thanks

  parent reply	other threads:[~2019-04-22 11:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 18:05 Stephen Hemminger
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 ` Thomas Monjalon [this message]
2019-04-22 11:37   ` [dpdk-dev] [PATCH 0/5] trivial blank line at end of file cleanup 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=6034278.LiO6WW6BUP@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --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).