On Sat, Sep 22, 2012 at 1:01 PM, Theo de Raadt wrote:
>> Only concern I have is whether #include could have
>> side-effects on architectures I don't know of (which, admittedly, is
>> quite a few).
>
> it is a bad idea to pull machine/ header files.
It's also the documented method of getting the
> Only concern I have is whether #include could have
> side-effects on architectures I don't know of (which, admittedly, is
> quite a few).
it is a bad idea to pull machine/ header files.
Ping, ping, on this essentially +1 -1 diff?
Only concern I have is whether #include could have
side-effects on architectures I don't know of (which, admittedly, is
quite a few).
/Alexander
On 09/12/12 00:43, Alexander Hall wrote:
This pulls in machine/cpu.h so we can see CPU_LIDSUSPEND if
On 2012/09/22 13:29, Camiel Dobbelaar wrote:
> On 21-9-2012 23:40, Stuart Henderson wrote:
> > $ ifconfig vr0 hwfeatures|head -2
> > vr0: flags=8b43
> > mtu 1500
> > hwfeatures=8017
> >
> > No problems noticed yet. (this is running i386).
> >
> > $ ifconfig vlan6 hwfeatures|head -2
> > v
On 21-9-2012 23:40, Stuart Henderson wrote:
> $ ifconfig vr0 hwfeatures|head -2
> vr0: flags=8b43 mtu
> 1500
> hwfeatures=8017
>
> No problems noticed yet. (this is running i386).
>
> $ ifconfig vlan6 hwfeatures|head -2
> vlan6: flags=8943 mtu 1500
> hwfeatures=0<>
>
> Is it rig
