From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: Fix inconsistent teardown and release of private netdev state.
Date: Fri, 09 Jun 2017 14:54:34 -0400 (EDT) [thread overview]
Message-ID: <20170609.145434.399590645965329804.davem@davemloft.net> (raw)
In-Reply-To: <20170609102104.34c26568@xeon-e3>
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri, 9 Jun 2017 10:21:04 -0700
> Is there anything in Documentation/networking/netdevices.txt about this to
> avoid any future issues?
You asked me about this last time, and I did not forget about it.
I sincerely lack the time to do a writeup about it, and I felt that
delaying the fix for another week or two until I find that magical
non-existing timeframe to write the docs was not beneficial for
users at all.
next prev parent reply other threads:[~2017-06-09 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 19:54 [PATCH] net: Fix inconsistent teardown and release of private netdev state David Miller
2017-06-09 12:45 ` Johannes Berg
2017-06-09 14:17 ` David Miller
2017-06-09 14:33 ` Johannes Berg
2017-06-09 17:14 ` David Miller
2017-06-09 17:21 ` Stephen Hemminger
2017-06-09 18:54 ` David Miller [this message]
2017-06-12 20:40 ` 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=20170609.145434.399590645965329804.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).