On Sat, May 20, 2023 at 07:47:46PM +0200, Florian Obser wrote:
> On 2023-05-20 19:37 +02, Paul de Weerd wrote:
> > On Sat, May 20, 2023 at 05:33:11PM +0200, Florian Obser wrote:
> > | In case this turns out to be useful for unlocking work in the kernel.
> > |
> > | It's a minimum diff, if we want
On 2023-05-20 19:37 +02, Paul de Weerd wrote:
> On Sat, May 20, 2023 at 05:33:11PM +0200, Florian Obser wrote:
> | In case this turns out to be useful for unlocking work in the kernel.
> |
> | It's a minimum diff, if we want to go this way we probably want to move
> | init_soiikey() to the engine
On Sat, May 20, 2023 at 05:33:11PM +0200, Florian Obser wrote:
| In case this turns out to be useful for unlocking work in the kernel.
|
| It's a minimum diff, if we want to go this way we probably want to move
| init_soiikey() to the engine process and stop bouncing through the main
| process whe
In case this turns out to be useful for unlocking work in the kernel.
It's a minimum diff, if we want to go this way we probably want to move
init_soiikey() to the engine process and stop bouncing through the main
process when an interface changes.
This changes behaviour: in -current we can chang
