netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Timothy Redaelli <tredaelli@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [iproute PATCH] bridge: Prevent a double space in bridge mdb show
Date: Fri, 23 Feb 2018 08:14:58 -0800	[thread overview]
Message-ID: <20180223081458.612f4009@xeon-e3> (raw)
In-Reply-To: <09c2d14a14282f74739012d70f4a1cf103bee2e3.1519054060.git.tredaelli@redhat.com>

On Mon, 19 Feb 2018 17:13:06 +0100
Timothy Redaelli <tredaelli@redhat.com> wrote:

> Prevent a double space in "bridge mdb show" when the MDB entry is not
> marked as "offload".
> 
> Signed-off-by: Timothy Redaelli <tredaelli@redhat.com>

Applied.

In iproute2-next printout has changed in this area, so this patch won't merge
to next. It looks like the json stuff might have introduced other spacing glitches though.

      reply	other threads:[~2018-02-23 16:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 16:13 [iproute PATCH] bridge: Prevent a double space in bridge mdb show Timothy Redaelli
2018-02-23 16:14 ` 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=20180223081458.612f4009@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    --cc=tredaelli@redhat.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).