public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k•org>
To: Pavel Machek <pavel@ucw•cz>
Cc: "David S. Miller" <davem@davemloft•net>,
	Netdev list <netdev@vger•kernel.org>
Subject: Re: [PATCH] Documentation: fix ascii art in networking docs
Date: Sat, 16 Sep 2017 20:18:15 +0200	[thread overview]
Message-ID: <87efr65wyg.fsf@linux-m68k.org> (raw)
In-Reply-To: <20170916162217.GA11237@amd> (Pavel Machek's message of "Sat, 16 Sep 2017 18:22:17 +0200")

On Sep 16 2017, Pavel Machek <pavel@ucw•cz> wrote:

> diff --git a/Documentation/networking/switchdev.txt b/Documentation/networking/switchdev.txt
> index 5e40e1f..6309e90 100644
> --- a/Documentation/networking/switchdev.txt
> +++ b/Documentation/networking/switchdev.txt
> @@ -29,7 +29,7 @@ with SR-IOV or soft switches, such as OVS, are possible.
>                        sw1p1  +  sw1p3  +  sw1p5  +          eth1
>                          +    |    +    |    +    |            +
>                          |    |    |    |    |    |            |
> -                     +--+----+----+----+-+--+----+---+  +-----+-----+
> +                     +--+----+----+----+----+----+---+  +-----+-----+
>                       |         Switch driver         |  |    mgmt   |
>                       |        (this document)        |  |   driver  |
>                       |                               |  |           |
>

This is all mis-aligned.  How about replacing all the thin space
characters by normal spaces?

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k•org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  parent reply	other threads:[~2017-09-16 18:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-16 16:22 [PATCH] Documentation: fix ascii art in networking docs Pavel Machek
2017-09-16 16:51 ` Andrew Lunn
2017-09-16 18:18 ` Andreas Schwab [this message]
2017-09-16 19:25   ` Pavel Machek
2017-09-16 19:47   ` Randy Dunlap

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=87efr65wyg.fsf@linux-m68k.org \
    --to=schwab@linux-m68k$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pavel@ucw$(echo .)cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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