netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guillaume Nault <gnault@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: David Ahern <dsahern@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] man: remove ppp from list of devices not allowed to change netns
Date: Sat, 9 Nov 2019 18:01:23 +0100	[thread overview]
Message-ID: <20191109170123.GA2424@linux.home> (raw)
In-Reply-To: <20191108153159.25e09c8a@hermes.lan>

On Fri, Nov 08, 2019 at 03:31:59PM -0800, Stephen Hemminger wrote:
> On Fri, 8 Nov 2019 22:28:04 +0100
> Guillaume Nault <gnault@redhat.com> wrote:
> > diff --git a/man/man8/ip-link.8.in b/man/man8/ip-link.8.in
> > index 9629a649..939e2ad4 100644
> > --- a/man/man8/ip-link.8.in
> > +++ b/man/man8/ip-link.8.in
> > @@ -1921,7 +1921,7 @@ move the device to the network namespace associated with name
> >  .RI process " PID".
> >  
> >  Some devices are not allowed to change network namespace: loopback, bridge,
> > -ppp, wireless. These are network namespace local devices. In such case
> > +wireless. These are network namespace local devices. In such case
> >  .B ip
> >  tool will return "Invalid argument" error. It is possible to find out
> >  if device is local to a single network namespace by checking
> 
> This doesn't have to wait for net-next
Right, I should have posted it for -iproute2, sorry. The patch applies
cleanly there though. Do you want to take it as is, or do you prefer
that I submit it again?


  reply	other threads:[~2019-11-09 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 21:28 [PATCH iproute2-next] man: remove ppp from list of devices not allowed to change netns Guillaume Nault
2019-11-08 23:31 ` Stephen Hemminger
2019-11-09 17:01   ` Guillaume Nault [this message]
2019-11-09 20:02     ` 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=20191109170123.GA2424@linux.home \
    --to=gnault@redhat.com \
    --cc=dsahern@gmail.com \
    --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).