Displaying 5 results from an estimated 5 matches for "dev_get_flag".
Did you mean:
dev_get_flags
2019 Mar 06
0
[RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
...devices. Many devices turn off PHY and link layer
> > if not IFF_UP
> True, that's what I said about introducing internal state for those driver
> and other kernel component. Very invasive change indeed.
>
> -Siwei
Well I did say it's vague.
How about hiding IFF_UP from dev_get_flags (and probably
__dev_change_flags)?
2019 Mar 06
0
[RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
...; if not IFF_UP
> > > True, that's what I said about introducing internal state for those driver
> > > and other kernel component. Very invasive change indeed.
> > >
> > > -Siwei
> > Well I did say it's vague.
> > How about hiding IFF_UP from dev_get_flags (and probably
> > __dev_change_flags)?
> >
> Any different? This has small footprint for the kernel change for sure,
> while the discrepancy is still there. Anyone who writes code for IFF_UP will
> not notice IFF_FAILOVER_SLAVE.
>
> Not to mention more userspace "...
2019 Mar 06
0
[RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
...at I said about introducing internal state for those driver
> > > > > and other kernel component. Very invasive change indeed.
> > > > >
> > > > > -Siwei
> > > > Well I did say it's vague.
> > > > How about hiding IFF_UP from dev_get_flags (and probably
> > > > __dev_change_flags)?
> > > >
> > > Any different? This has small footprint for the kernel change for sure,
> > > while the discrepancy is still there. Anyone who writes code for IFF_UP will
> > > not notice IFF_FAILOVER_SLAV...
2019 Mar 06
0
[RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
...se driver
> > > > > > > and other kernel component. Very invasive change indeed.
> > > > > > >
> > > > > > > -Siwei
> > > > > > Well I did say it's vague.
> > > > > > How about hiding IFF_UP from dev_get_flags (and probably
> > > > > > __dev_change_flags)?
> > > > > >
> > > > > Any different? This has small footprint for the kernel change for sure,
> > > > > while the discrepancy is still there. Anyone who writes code for IFF_UP will
>...
2006 Feb 22
0
Re: [PATCH] Fix IPSec for Xen checksum offload packets (Jon Mason)
...)
>+ goto out_kfree_skb;
>
> /* If packet is not checksummed and device does not support
> * checksumming for this protocol, complete checksumming here.
>@@ -3350,6 +3361,7 @@
> EXPORT_SYMBOL(net_enable_timestamp);
> EXPORT_SYMBOL(net_disable_timestamp);
> EXPORT_SYMBOL(dev_get_flags);
>+EXPORT_SYMBOL(xen_checksum_setup);
>
> #if defined(CONFIG_BRIDGE) || defined(CONFIG_BRIDGE_MODULE)
> EXPORT_SYMBOL(br_handle_frame_hook);
>diff -r 57e6d7218427 -r 079135b0d58f patches/linux-2.6.16-rc2/net-csum.patch
>--- a/patches/linux-2.6.16-rc2/net-csum.patch Fri Feb 3 1...