From: Stephen Hemminger <stephen@networkplumber.org>
To: Luca Boccassi <bluca@debian.org>
Cc: netdev@vger.kernel.org, dsahern@gmail.com
Subject: Re: [PATCH iproute2] Fix warning in tc-skbprio.8 manpage
Date: Fri, 9 Nov 2018 08:06:37 -0800 [thread overview]
Message-ID: <20181109080637.1fee1f01@xeon-e3> (raw)
In-Reply-To: <20181102105741.25381-1-bluca@debian.org>
On Fri, 2 Nov 2018 10:57:41 +0000
Luca Boccassi <bluca@debian.org> wrote:
> ". If" gets interpreted as a macro, so move the period to the previous
> line:
>
> 33: warning: macro `If' not defined
>
> Fixes: 141b55f8544e ("Add SKB Priority qdisc support in tc(8)")
>
> Signed-off-by: Luca Boccassi <bluca@debian.org>
Applied
prev parent reply other threads:[~2018-11-10 1:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 10:57 [PATCH iproute2] Fix warning in tc-skbprio.8 manpage Luca Boccassi
2018-11-02 15:19 ` Edward Cree
2018-11-02 15:28 ` Luca Boccassi
2018-11-02 15:27 ` [PATCH iproute2 v2] " Luca Boccassi
2018-11-09 16:06 ` 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=20181109080637.1fee1f01@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bluca@debian.org \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.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).