[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMRc=Md+F=S1ipwNPjZQ+Kp=t7Py_Y=-SmFtbpOQa-xGYWsBPw@mail.gmail.com>
Date: Mon, 21 Aug 2023 15:34:25 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Kent Gibson <warthog618@...il.com>, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [PATCH v2 4/6] gpio: cdev: wake up chardev poll() on device unbind
On Fri, Aug 18, 2023 at 12:31 PM Andy Shevchenko
<andriy.shevchenko@...ux.intel.com> wrote:
>
> On Thu, Aug 17, 2023 at 08:49:56PM +0200, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
> >
> > Add a notifier block to the gpio_chardev_data structure and register it
> > with the gpio_device's device notifier. Upon reception of an event, wake
> > up the wait queue so that the user-space be forced out of poll() and need
> > to go into a new system call which will then fail due to the chip being
> > gone.
>
> ...
>
> > + struct gpio_chardev_data *cdev = container_of(nb,
> > + struct gpio_chardev_data,
> > + device_unregistered_nb);
>
> struct gpio_chardev_data *cdev =
> container_of(nb, struct gpio_chardev_data, device_unregistered_nb);
>
Ah, this goes over 80 chars. I will leave it as it is, I will fix the
other one when applying.
Bart
> ?
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
Powered by blists - more mailing lists