From: Olaf Hering <olaf@aepfle.de>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: "jasowang@redhat.com" <jasowang@redhat.com>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH net-next] hyperv: Add handler for RNDIS_STATUS_NETWORK_CHANGE event
Date: Thu, 26 Jun 2014 10:45:39 +0200 [thread overview]
Message-ID: <20140626084539.GA32471@aepfle.de> (raw)
In-Reply-To: <4ee8be5360a44b5abfa6df871ec45527@DFM-DB3MBX15-06.exchange.corp.microsoft.com>
On Mon, Jun 23, Haiyang Zhang wrote:
> Yes, there is a link down/up event from the host, we currently call netif_carrier_off()
> / netif_carrier_on() with these events. Will hotplug scripts be triggered by
> netif_carrier_off/on? Where are the scripts located at (SLES)?
In /etc/sysconfig/network/ifcfg-eth0 STARTMODE= should be set to
"ifplugd", this will most likely fix this sort of setup.
Olaf
next prev parent reply other threads:[~2014-06-26 8:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 1:34 [PATCH net-next] hyperv: Add handler for RNDIS_STATUS_NETWORK_CHANGE event Haiyang Zhang
2014-06-20 4:21 ` David Miller
2014-06-20 4:57 ` Olaf Hering
2014-06-20 5:12 ` Greg KH
2014-06-20 16:09 ` Haiyang Zhang
2014-06-23 8:02 ` Olaf Hering
2014-06-23 12:47 ` Haiyang Zhang
2014-06-23 13:17 ` Olaf Hering
2014-06-23 16:09 ` Haiyang Zhang
2014-06-23 16:27 ` Olaf Hering
2014-06-23 18:21 ` Haiyang Zhang
2014-06-26 8:45 ` Olaf Hering [this message]
2014-06-26 14:55 ` Haiyang Zhang
2014-06-23 16:29 ` Greg KH
2014-06-23 18:23 ` Haiyang Zhang
2014-06-23 20:11 ` David Miller
2014-06-23 20:10 ` David Miller
2014-06-23 20:17 ` Haiyang Zhang
2015-10-27 22:36 ` Richard Weinberger
2015-10-28 17:59 ` Haiyang Zhang
2015-10-29 19:09 ` Haiyang Zhang
2015-10-30 10:56 ` Vitaly Kuznetsov
2015-10-30 22:03 ` Haiyang Zhang
2015-10-30 22:10 ` Richard Weinberger
2014-06-23 20:06 ` David Miller
2014-06-20 8:41 ` Dan Carpenter
2014-06-20 15:48 ` Haiyang Zhang
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=20140626084539.GA32471@aepfle.de \
--to=olaf@aepfle.de \
--cc=davem@davemloft.net \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).