śr., 11 gru 2019 o 11:47 Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> napisał(a): > > On Wed, Dec 11, 2019 at 05:29:21PM +0800, Kent Gibson wrote: > > On Wed, Dec 11, 2019 at 10:18:39AM +0100, Bartosz Golaszewski wrote: > > > wt., 10 gru 2019 o 17:55 Andy Shevchenko > > > <andriy.shevchenko@xxxxxxxxxxxxxxx> napisał(a): > > > > > > Neither of those options are available for the > > > > > gpioevent_data, as that would break the ABI. > > > > > > > > ABI needs v2 actually. > > > > > > > > > > I finally sat down to integrate this with my series and figured that > > > this can't go on top of it. It's a bug-fix actually and maybe even > > > stable material. > > > > > > On the other hand - if we have so few users of GPIO chardev with > > > 32-bit user-space and 64-bit kernel - maybe we should just bite the > > > bullet, not fix this one, deprecate it and introduce a proper v2 of > > > the API? > > > > > > > Fixing it in API v2 makes the most sense to me. > > I agree. Please, use only second patch in my series (if needed I can resend > it separately) and drop this one. > > P.S. Actually it's not a bugfix since it's never worked from the day 1. > Yeah I guess so. Anyway, in this case, I won't be adding the event watch feature to v1 - I'll go ahead and just add it to v2 then. Bart