netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 3/4] man: ip-address: document 15-char limit for LABEL
Date: Sat, 30 Dec 2017 11:32:13 +0100	[thread overview]
Message-ID: <1514629933.6638.53.camel@debian.org> (raw)
In-Reply-To: <20171229200457.2710e99b@xeon-e3>

[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]

On Fri, 2017-12-29 at 20:04 -0800, Stephen Hemminger wrote:
> On Fri, 29 Dec 2017 23:01:24 +0100
> Luca Boccassi <bluca@debian.org> wrote:
> 
> > Trying to set a label longer than 15 characters returns an error:
> >  RTNETLINK answers: Numerical result out of range
> > 
> > Document the limit in the manpage.
> > 
> > Originally reported as a Debian bug:
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661886
> > 
> > Reported-by: Gabor Kiss <kissg@ssg.ki.iif.hu>
> > Signed-off-by: Luca Boccassi <bluca@debian.org>
> > ---
> >  man/man8/ip-address.8.in | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/man/man8/ip-address.8.in b/man/man8/ip-address.8.in
> > index eaa179c6..e7f14533 100644
> > --- a/man/man8/ip-address.8.in
> > +++ b/man/man8/ip-address.8.in
> > @@ -190,6 +190,7 @@ Each address may be tagged with a label string.
> >  In order to preserve compatibility with Linux-2.0 net aliases,
> >  this string must coincide with the name of the device or must be
> > prefixed
> >  with the device name followed by colon.
> > +The maximum allowed length is 15 characters.
> 
> Since these are aliases, lets be precise:
> The maximum allowed total length of label is 15 characters.

Ok, done in v2, thanks

-- 
Kind regards,
Luca Boccassi

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2017-12-30 10:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 22:01 [PATCH iproute2 1/4] man: drop references to Debian-specific paths Luca Boccassi
2017-12-29 22:01 ` [PATCH iproute2 2/4] man: add more keywords to ip.8 short description Luca Boccassi
2017-12-30  4:02   ` Stephen Hemminger
2017-12-30 10:32     ` Luca Boccassi
2017-12-29 22:01 ` [PATCH iproute2 3/4] man: ip-address: document 15-char limit for LABEL Luca Boccassi
2017-12-30  4:04   ` Stephen Hemminger
2017-12-30 10:32     ` Luca Boccassi [this message]
2017-12-29 22:01 ` [PATCH iproute2 4/4] man: routel/routef: don't mention filesystem paths Luca Boccassi
2017-12-30  4:05   ` Stephen Hemminger
2017-12-30 10:31 ` [PATCH iproute2 v2 1/4] man: drop references to Debian-specific paths Luca Boccassi
2017-12-30 10:31   ` [PATCH iproute2 v2 2/4] man: add more keywords to ip.8 short description Luca Boccassi
2017-12-30 10:31   ` [PATCH iproute2 v2 3/4] man: ip-address: document 15-char limit for LABEL Luca Boccassi
2017-12-30 10:31   ` [PATCH iproute2 v2 4/4] man: routel/routef: don't mention filesystem paths Luca Boccassi
2017-12-30 17:44   ` [PATCH iproute2 v2 1/4] man: drop references to Debian-specific paths Stephen Hemminger

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=1514629933.6638.53.camel@debian.org \
    --to=bluca@debian.org \
    --cc=netdev@vger.kernel.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).