From: Linus Walleij <linus.walleij@linaro.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Marc Zyngier <marc.zyngier@arm.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"Bartosz Golaszewski" <bgolaszewski@baylibre.com>
Subject: Re: [PATCH 1/2] irq/irq_sim: provide irq_sim_fire_edge()
Date: Fri, 30 Nov 2018 23:26:25 +0100 [thread overview]
Message-ID: <CACRpkdY9-umyz=T8v0ZmfOx8tFapvDguS3B=BYAVkY73BrkxqQ@mail.gmail.com> (raw)
In-Reply-To: <CAMRc=Mfu=e3BsjMN=_H9CbUvumdmT1pvNjsyivTo1WN+LC1+2A@mail.gmail.com>
On Thu, Nov 29, 2018 at 7:14 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> Thomas, Linus: after commit fa38869b0161 ("gpiolib: Don't support irq
> sharing for userspace") some libgpiod tests are failing because we can
> no longer depend on reading the value of a dummy GPIO after detecting
> an interrupt to know the edge of the interrupt. While these interrupts
> are triggered from debugfs and debugfs is not required to maintain
> compatibility, I thing having a working test suite for the GPIO
> subsystem and uAPI is worth applying these two patches and also the
> previous one[1].
>
> Can we have them applied for 4.20 or are there any objections?
I'm fine with applying them if I can just get an ACK from one of the IRQ
maintainers (Thomas, Marc).
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-11-30 22:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 13:40 [PATCH 0/2] irq/irq_sim: provide a specialized variant of irq_sim_fire() Bartosz Golaszewski
2018-11-20 13:40 ` [PATCH 1/2] irq/irq_sim: provide irq_sim_fire_edge() Bartosz Golaszewski
2018-11-20 17:17 ` Uwe Kleine-König
2018-11-21 16:34 ` Bartosz Golaszewski
2018-11-21 19:15 ` Uwe Kleine-König
2018-11-23 15:59 ` Bartosz Golaszewski
2018-11-25 21:18 ` Uwe Kleine-König
2018-11-29 18:14 ` Bartosz Golaszewski
2018-11-30 22:26 ` Linus Walleij [this message]
2018-12-02 12:29 ` Marc Zyngier
2018-12-02 17:00 ` Bartosz Golaszewski
2018-12-02 21:56 ` Uwe Kleine-König
2018-12-02 22:20 ` Bartosz Golaszewski
2018-12-03 10:23 ` Bartosz Golaszewski
2018-12-03 10:49 ` Uwe Kleine-König
2018-12-03 10:57 ` Bartosz Golaszewski
2018-12-03 11:06 ` Uwe Kleine-König
2018-12-05 12:19 ` Linus Walleij
2018-12-05 12:38 ` Bartosz Golaszewski
2018-12-05 12:55 ` Linus Walleij
2018-12-17 10:32 ` Bartosz Golaszewski
2018-12-17 12:59 ` Uwe Kleine-König
2018-12-17 13:59 ` Bartosz Golaszewski
2018-12-05 13:20 ` Uwe Kleine-König
2018-12-14 14:07 ` Linus Walleij
2018-12-17 11:19 ` Uwe Kleine-König
2018-11-20 13:40 ` [PATCH 2/2] gpio: mockup: use irq_sim_fire_edge() Bartosz Golaszewski
2018-12-03 11:09 ` Uwe Kleine-König
2018-12-11 14:15 ` Uwe Kleine-König
2018-12-11 15:38 ` Bartosz Golaszewski
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='CACRpkdY9-umyz=T8v0ZmfOx8tFapvDguS3B=BYAVkY73BrkxqQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).