ok for me
On 5 January 2017 at 13:19, Francois Ozog wrote:
> Monday is my busiest day (last call ends 10pm) but we can do a morning
> call: 11amCET?
>
> On 5 January 2017 at 12:28, Christophe Milard <
> christophe.mil...@linaro.org> wrote:
>
>> Hi Francois,
>>
>> Can we have a HO on monday ( I u
Monday is my busiest day (last call ends 10pm) but we can do a morning
call: 11amCET?
On 5 January 2017 at 12:28, Christophe Milard
wrote:
> Hi Francois,
>
> Can we have a HO on monday ( I understood today was busy for you, FF and I
> tomorrow is a swedish national holiday). If not, we can of co
Hi Francois,
Can we have a HO on monday ( I understood today was busy for you, FF and I
tomorrow is a swedish national holiday). If not, we can of course take in
on tuesday.
The topics I'd like to discuss are:
1) change of interface: pass a struct _param_t at register time and
get a handle as a
Hi Christophe,
event are not just "new device" (in that case I would agree with you).
Events can be:
- "attention" (before "poweroff") for a specific device to orderly shutdown
before poweroff (or remove if virtio-net device in a VM).
- SFP insertion/removal of a specific port
- Error condition (a
Hi Francois,
Following your suggestion, the driver API contains:
/** Register event notifier function for hotplug events:
*/
int (*register_notifier)(void (*event_handler) (void));
But I an now wondering: Why this double callback?
Wouldn't it be simpler to have the function