> It's a single work, it cannot run twice. Ok, thanks > E.g. set_bit() (one bit per OP) to something like 'unsigned long flags' > in 'struct corsair_void_drvdata'. But it depends if you want to preserve > order of actions... (Which was not guaranteed with separate queues > anyway, so I assume not?) Wouldn't using one variable for the flags risk overwriting each other, unless it was atomic? I might be misunderstanding, I haven't played with the kernel's work much. Yeah I wasn't worried about the order, since add and remove can't fire that close to each other anyway.
