From: Stephen Hemminger <stephen@networkplumber.org>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: David Ahern <dsa@cumulusnetworks.com>,
Roopa Prabhu <roopa@cumulusnetworks.com>,
Robert Shearman <rshearma@brocade.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: rcu locking issue in mpls output code?
Date: Mon, 20 Jun 2016 12:37:41 -0700 [thread overview]
Message-ID: <20160620123741.71401da7@xeon-e3> (raw)
In-Reply-To: <20160620174408.GT20238@wantstofly.org>
> ifconfig tons 172.16.20.20 netmask 255.255.255.0
Really, still using ifconfig?
prev parent reply other threads:[~2016-06-20 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 0:45 rcu locking issue in mpls output code? Lennert Buytenhek
2016-06-20 2:19 ` David Ahern
2016-06-20 6:30 ` Lennert Buytenhek
2016-06-20 15:19 ` David Ahern
2016-06-20 16:13 ` Roopa Prabhu
2016-06-20 16:33 ` Lennert Buytenhek
2016-06-20 16:38 ` David Ahern
2016-06-20 17:44 ` Lennert Buytenhek
2016-06-20 19:37 ` Stephen Hemminger [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=20160620123741.71401da7@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=buytenh@wantstofly.org \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=rshearma@brocade.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).