Hello Andy Thanks again for your feedback. On Tue, Nov 28, 2023 at 5:29 PM Andy Shevchenko <andy@xxxxxxxxxx> wrote: > > On Tue, Nov 28, 2023 at 03:13:21PM +0100, Boerge Struempfel wrote: > > If gpio_set_transitory() fails, we should free the gpio again. Most > > gpio --> GPIO descriptor > (I already mentioned capitalization in v1 review) > I'm sorry, I misunderstood your comment "GPIO" in the v1 review. I fixed it for the next version. > > notably, the flag FLAG_REQUESTED has previously been set in > > gpiod_request_commit(), and should be reset on failure. > > > > To my knowledge, this does not affect any current users, since the > > gpio_set_transitory() mainly returns 0 and -ENOTSUPP, which is converted > > to 0. However the gpio_set_transitory() function calles the .set_config() > > function of the corresponding gpio chip and there are some gpio drivers in > > gpio --> GPIO > thanks > > which some (unlikely) branches return other values like -EPROBE_DEFER, > > and EINVAL. In these cases, the above mentioned FLAG_REQUESTED would not > > -EINVAL > thanks, I missed that, when I added the minus to all the other Error codes. > > be reset, which results in the pin being blocked until the next reboot. > > Fixes tag? > (`git log --no-merges --grep "Fixes:" will show you examples) > I thought it was optional. But I have added it for the next version. > -- > With Best Regards, > Andy Shevchenko > >