From: Guillaume Nault <g.nault@alphalink.fr>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, paulus@samba.org
Subject: Re: [PATCH net-next 0/2] ppp: implement x-netns support
Date: Fri, 14 Aug 2015 10:51:31 +0200 [thread overview]
Message-ID: <20150814085131.GD2825@alphalink.fr> (raw)
In-Reply-To: <20150813.212004.553374390201687089.davem@davemloft.net>
On Thu, Aug 13, 2015 at 09:20:04PM -0700, David Miller wrote:
> From: Guillaume Nault <g.nault@alphalink.fr>
> Date: Thu, 13 Aug 2015 15:28:02 +0200
>
> > This series allows PPP devices to reside in a different netns from the
> > PPP unit/channels. Packets only cross netns boundaries when they're
> > transmitted between the net_device and the PPP unit (units and channels
> > always remain in their creation namespace).
> > So only PPP units need to handle cross namespace operations. Channels
> > and lower layer protocols aren't affected.
> >
> > Patch #1 is a bug fix for an existing namespace deletion bug and has
> > been separetly sent to net.
> > Patch #2 is the actual x-netns implementation.
>
> Patch #1 needs to be respun with the change I requested.
>
Ok, done.
> And this is not the way to submit things that have dependencies
> upon bug fixes.
>
Will do. I was actually unsure about how to handle this case.
Thanks.
prev parent reply other threads:[~2015-08-14 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 13:28 [PATCH net-next 0/2] ppp: implement x-netns support Guillaume Nault
2015-08-13 13:28 ` [PATCH net-next 1/2] ppp: fix device unregistration upon netns deletion Guillaume Nault
2015-08-13 13:28 ` [PATCH net-next 2/2] ppp: implement x-netns support Guillaume Nault
2015-08-14 4:20 ` [PATCH net-next 0/2] " David Miller
2015-08-14 8:51 ` Guillaume Nault [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=20150814085131.GD2825@alphalink.fr \
--to=g.nault@alphalink.fr \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.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).