On Wed, Sep 20, 2017 at 4:08 PM, Jerome Brunet <jbrunet@xxxxxxxxxxxx> wrote: > ENOSYS is special and should only be used for incorrect syscall number. > It is not the case here. let's use ENOTSUPP instead. > > Signed-off-by: Jerome Brunet <jbrunet@xxxxxxxxxxxx> Patch applied. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] pinctrl: meson: fix incorrect usage of ENOSYS
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] pinctrl: meson: fix incorrect usage of ENOSYS
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Thu, 21 Sep 2017 14:18:33 +0200
- In-reply-to: <20170920140815.20776-1-jbrunet@baylibre.com>
- References: <20170920140815.20776-1-jbrunet@baylibre.com>
- References:
- [PATCH] pinctrl: meson: fix incorrect usage of ENOSYS
- From: Jerome Brunet
- [PATCH] pinctrl: meson: fix incorrect usage of ENOSYS
- Prev by Date: Re: [PATCH 2/3] arm64: dts: mt2712: add pintcrl device node.
- Next by Date: Re: [PATCH] gpio: Wakeup gpio controller when it is used as IRQ controller
- Previous by thread: [PATCH] pinctrl: meson: fix incorrect usage of ENOSYS
- Next by thread: [PATCH 0/2] pinctrl: Allow indicating loss of state across suspend/resume
- Index(es):
 |