From: Johannes Berg <johannes@sipsolutions.net>
To: Mark Asselstine <mark.asselstine@windriver.com>,
Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFT] brcmfmac: add support to move wiphy instance into network namespace
Date: Fri, 17 Mar 2017 13:58:58 +0100 [thread overview]
Message-ID: <1489755538.2544.11.camel@sipsolutions.net> (raw)
In-Reply-To: <10023407.Rx0XN2k1RN@yow-masselst-lx1>
> > I guess this is intended behavior?
>
> I had thought this was intended behavior as well but I see that a
> patch is already prepped and tested to make this not happen. At any
> rate it wasn't appearing to affect my usecase.
I can't actually see how it'd affect any usecase, since you really need
to check inside the new netns what's going on etc. anyway, and you
don't really want to pass such identifiers across the boundaries. But
preserving it makes more sense, if only for debugging and making sure
we won't run out of numbers :)
johannes
next prev parent reply other threads:[~2017-03-17 12:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 21:51 [RFT] brcmfmac: add support to move wiphy instance into network namespace Arend van Spriel
2017-03-14 22:19 ` Johannes Berg
2017-03-15 8:54 ` Arend Van Spriel
2017-03-16 21:51 ` Mark Asselstine
2017-03-17 8:21 ` Arend Van Spriel
2017-03-17 9:06 ` Arend Van Spriel
2017-03-17 9:24 ` Johannes Berg
2017-03-17 9:33 ` Arend Van Spriel
2017-03-17 9:36 ` Arend Van Spriel
2017-03-17 9:30 ` Arend Van Spriel
2017-03-17 12:43 ` Mark Asselstine
2017-03-17 12:58 ` Johannes Berg [this message]
2017-03-17 13:05 ` Mark Asselstine
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=1489755538.2544.11.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mark.asselstine@windriver.com \
/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).