Re: [PATCH 000/182] Rid struct gpio_chip from container_of() usage
From: Linus Walleij <hidden>
Date: 2015-12-18 14:42:27
Also in:
linux-gpio, linux-mips, linux-wireless
Possibly related (same subject, not in this thread)
- 2015-12-18 · Re: [PATCH 000/182] Rid struct gpio_chip from container_of() usage · Linus Walleij <hidden>
- 2015-12-15 · Re: [PATCH 000/182] Rid struct gpio_chip from container_of() usage · Dmitry Torokhov <dmitry.torokhov@gmail.com>
- 2015-12-14 · Re: [PATCH 000/182] Rid struct gpio_chip from container_of() usage · Linus Walleij <hidden>
- 2015-12-09 · Re: [PATCH 000/182] Rid struct gpio_chip from container_of() usage · Dmitry Torokhov <hidden>
- 2015-12-09 · [PATCH 000/182] Rid struct gpio_chip from container_of() usage · Linus Walleij <hidden>
On Mon, Dec 14, 2015 at 1:46 PM, Johan Hovold [off-list ref] wrote:
Ok, but let's take a step back. So you have all this in place and a
consumer calls gpiod_get_value() that returns an errno because the device
is gone. Note that this wasn't even possible before e20538b82f1f ("gpio:
Propagate errors from chip->get()") that went into *v4.3*, and I assume
most drivers would need to be updated to even handle that that gpio
call, and all future calls, are now suddenly failing.I actually have a revert of that in my fixes queue. So another step back and two forward for v4.5 (hopefully): audit all drivers to respect this. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html