On Tue, Feb 5, 2019 at 4:43 PM Dmitry Torokhov <[email protected]> wrote: > > OK, great, I'll write up a patch for cap11xx and others if I find them. >
Possibly also drivers/input/keyboard/lm8323.c
- [RFC v1 0/3] Address potential user-after-free on module... Sven Van Asbroeck
- [RFC v1 3/3] cap11xx: fix potential user-after-free... Sven Van Asbroeck
- Re: [RFC v1 3/3] cap11xx: fix potential user-af... Dmitry Torokhov
- Re: [RFC v1 3/3] cap11xx: fix potential use... Dmitry Torokhov
- Re: [RFC v1 3/3] cap11xx: fix potential use... Jacek Anaszewski
- Re: [RFC v1 3/3] cap11xx: fix potential... Dmitry Torokhov
- Re: [RFC v1 3/3] cap11xx: fix pote... Sven Van Asbroeck
- [RFC v1 1/3] workqueue: Add resource-managed versio... Sven Van Asbroeck
- [RFC v1 2/3] max17042_battery: fix potential user-a... Sven Van Asbroeck
- Re: [RFC v1 2/3] max17042_battery: fix potentia... Dmitry Torokhov
- Re: [RFC v1 2/3] max17042_battery: fix pote... Sven Van Asbroeck
- Re: [RFC v1 2/3] max17042_battery: fix ... Sebastian Reichel
- Re: [RFC v1 0/3] Address potential user-after-free ... Kees Cook
- Re: [RFC v1 0/3] Address potential user-after-f... Sven Van Asbroeck
- Re: [RFC v1 0/3] Address potential user-aft... Greg KH
- Re: [RFC v1 0/3] Address potential user... Sven Van Asbroeck
