From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Kent Gibson <warthog618@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH] gpiolib: notify user-space about line status changes after flags are set
Date: Sat, 16 May 2020 19:28:42 +0530 [thread overview]
Message-ID: <20200516135842.GA17153@Mani-XPS-13-9360> (raw)
In-Reply-To: <CACRpkdZ2WGs=aWjwS=vk6-PDMvXMLppfBBF-8rs42F=ko3biNg@mail.gmail.com>
On Sat, May 16, 2020 at 11:30:36AM +0200, Linus Walleij wrote:
> On Sat, May 9, 2020 at 4:15 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
>
> > Since the flags can be configured in different ways depending on how the
> > line is being requested - we need to call the notifier chain in different
> > places separately.
>
> Ooops.
>
> > This comes late in the release cycle but I only recently got down to
> > writing libgpiod support for this new ioctl(). When writing test cases
> > I noticed this doesn't really work as expected.
>
> This is why I am so grateful about the tests you are doing with
> libgpiod! We actually find these problems quickly and not after
> years. Thanks!
>
This forces me to add tests for chardev in MRAA ;) (Don't ask me about other
interfaces)
Thanks,
Mani
> > This patch fixes the
> > issue I identified this week. There may be more coming the following
> > week though...
>
> I will pull in your pull request once the next -rc is out as I had already
> sent my first pull request, but do not hesitate to bug me about this.
>
> Yours,
> Linus Walleij
prev parent reply other threads:[~2020-05-16 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 14:15 [PATCH] gpiolib: notify user-space about line status changes after flags are set Bartosz Golaszewski
2020-05-16 9:30 ` Linus Walleij
2020-05-16 13:58 ` Manivannan Sadhasivam [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200516135842.GA17153@Mani-XPS-13-9360 \
--to=manivannan.sadhasivam@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog618@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox