netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: netdev@vger.kernel.org, sthemmin@microsoft.com
Subject: Re: [PATCH net-next] inet: whitespace cleanup
Date: Wed, 28 Feb 2018 11:44:19 -0500 (EST)	[thread overview]
Message-ID: <20180228.114419.546448880955799427.davem@davemloft.net> (raw)
In-Reply-To: <20180227234821.5670-1-sthemmin@microsoft.com>

From: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 27 Feb 2018 15:48:21 -0800

> Ran simple script to find/remove trailing whitespace and blank lines
> at EOF because that kind of stuff git whines about and editors leave
> behind.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>

Yeah I find these annoying.  People often make changes and propagate
the trailing whitespace issue from one place to another, so it's not
really their fault that the whitespace problem exists in their
patch.

Anyways, applied, thanks Stephen.

      reply	other threads:[~2018-02-28 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 23:48 [PATCH net-next] inet: whitespace cleanup Stephen Hemminger
2018-02-28 16:44 ` David Miller [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=20180228.114419.546448880955799427.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=sthemmin@microsoft.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).