Re: [PATCH] Hyperv: Trigger DHCP renew after host hibernation

2014-08-13 Thread Tom Gundersen
On Tue, Aug 12, 2014 at 10:29 AM, Dexuan Cui wrote: >> From: Tom Gundersen >> > Unluckily this logic doesn't work because the user-space daemons >> > like ifplugd, usually don't renew the DHCP immediately as long as they >> > receive a link-down message

Re: [PATCH] Hyperv: Trigger DHCP renew after host hibernation

2014-08-11 Thread Tom Gundersen
On Mon, Aug 11, 2014 at 5:23 AM, Dexuan Cui wrote: >> -Original Message- >> From: Greg KH [mailto:gre...@linuxfoundation.org] >> > > > >> > > > IMO the most feasible and need-the-least-change solution may be: >> > > > the hyperv network VSC driver passes the event >> > > > RNDIS_STATUS_NET

Re: [PATCH] Hyperv: Trigger DHCP renew after host hibernation

2014-07-21 Thread Tom Gundersen
On Mon, Jul 21, 2014 at 12:21 PM, Yue Zhang (OSTC DEV) wrote: >> From: Tom Gundersen [mailto:t...@jklm.no] >> Sent: Monday, July 21, 2014 5:42 PM >> >> On Fri, Jul 18, 2014 at 12:55 PM, Yue Zhang wrote: >> > From: Yue Zhang >> > >> > This patch

Re: [PATCH] Hyperv: Trigger DHCP renew after host hibernation

2014-07-21 Thread Tom Gundersen
On Fri, Jul 18, 2014 at 12:55 PM, Yue Zhang wrote: > From: Yue Zhang > > This patch addresses the comment from Olaf Hering and Greg KH > for a previous commit 3a494e710367 ("hyperv: Add handler for > RNDIS_STATUS_NETWORK_CHANGE event") > > In previous solution, the driver calls "network restart"

[PATCH v7 16/33] net: gdm_lte - set name assign type

2014-07-10 Thread Tom Gundersen
Devices are named according to the scheme lteXpdnY, where Y is the nic type, and X is the normal enumeration, so the scheme is NET_NAME_ENUM. Signed-off-by: Tom Gundersen Cc: Greg Kroah-Hartman Cc: Won Kang Cc: Rashika Kheria Cc: de...@driverdev.osuosl.org --- drivers/staging/gdm724x

[BUG?] staging: zram: Add auto loading of module if user opens /dev/zram.

2013-09-10 Thread Tom Gundersen
Hi Konrad, The above commit (c70bda9 in mainline) doesn't appear to work for me. I.e., depmod does not create an entry in modules.devname and hence no device node is created on boot. If I understand correctly, you'd also need to create the correct "char-major--" alias. But I don't really see how