From: Johannes Berg <johannes@sipsolutions.net>
To: Vadim Kochan <vadim4j@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC iw next] phy: Allow set netns by fd
Date: Fri, 23 Jan 2015 17:04:25 +0100 [thread overview]
Message-ID: <1422029065.2728.40.camel@sipsolutions.net> (raw)
In-Reply-To: <20150123154731.GA9454@angus-think.wlc.globallogic.com> (sfid-20150123_165824_857317_15B252D3)
On Fri, 2015-01-23 at 17:47 +0200, Vadim Kochan wrote:
> OK, just to clarify with nl80211.h - you will update it including new
> NL80211_ATTR_NETNS_FD ? If yes - I will wait for this change.
No, don't wait for it - just commit it locally separately for testing,
but send me only the actual code changes. I'll then do the update when I
apply your patch.
johannes
prev parent reply other threads:[~2015-01-23 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 15:13 [RFC iw next] phy: Allow set netns by fd Vadim Kochan
2015-01-23 15:34 ` Johannes Berg
2015-01-23 15:47 ` Vadim Kochan
2015-01-23 16:04 ` Johannes Berg [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=1422029065.2728.40.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=vadim4j@gmail.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).