All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Guillaume Nault <gnault@redhat.com>
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: Fri, 8 Nov 2019 15:31:59 -0800	[thread overview]
Message-ID: <20191108153159.25e09c8a@hermes.lan> (raw)
In-Reply-To: <beefb89b340483d75c39c46a9ec69384e839f663.1573248448.git.gnault@redhat.com>

On Fri, 8 Nov 2019 22:28:04 +0100
Guillaume Nault <gnault@redhat.com> wrote:

> PPP devices can be moved to different network namespaces. The feature
> was added by commit 79c441ae505c ("ppp: implement x-netns support")
> in Linux 4.3.
> 
> Signed-off-by: Guillaume Nault <gnault@redhat.com>
> ---
>  man/man8/ip-link.8.in | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> 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

  reply	other threads:[~2019-11-08 23:32 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 [this message]
2019-11-09 17:01   ` Guillaume Nault
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=20191108153159.25e09c8a@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=dsahern@gmail.com \
    --cc=gnault@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.