On Mon, Jul 1, 2019 at 4:28 PM Geert Uytterhoeven <geert+renesas@xxxxxxxxx> wrote: > Obviously functions that are safe to be called from atomic contexts, can > be called from non-atomic contexts, too. > > Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> Patch applied. Yours, Linus Walleij
Re: [PATCH] gpiolib: Clarify use of non-sleeping functions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] gpiolib: Clarify use of non-sleeping functions
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Thu, 4 Jul 2019 09:36:37 +0200
- In-reply-to: <20190701142809.25308-1-geert+renesas@glider.be>
- References: <20190701142809.25308-1-geert+renesas@glider.be>
- References:
- [PATCH] gpiolib: Clarify use of non-sleeping functions
- From: Geert Uytterhoeven
- [PATCH] gpiolib: Clarify use of non-sleeping functions
- Prev by Date: Re: [PATCH] gpiolib: Fix references to gpiod_[gs]et_*value_cansleep() variants
- Next by Date: Re: [PATCH 1/4] gpio: stp-xway: simplify error handling in xway_stp_probe()
- Previous by thread: [PATCH] gpiolib: Clarify use of non-sleeping functions
- Next by thread: [PATCH] Revert "spi: gpio: Don't request CS GPIO in DT use-case"
- Index(es):
 |