The linux-next integration testing tree https://git.rulkc.org/pub/scm/linux/kernel/git/next/linux-next.git/atom?h=akpm 2022-06-28T06:17:03+00:00 2022-06-28T06:17:03+00:00 Stephen Rothwell sfr@canb.auug.org.au 2022-06-28T06:17:03+00:00 urn:sha1:6e61f3d86cf7c00909e7972f618ac5202060c7fe 2022-06-28T05:41:14+00:00 Stephen Rothwell sfr@canb.auug.org.au 2022-06-28T05:41:14+00:00 urn:sha1:6d2c4faac6e3168b1ad7f77a8ac59dd8311cdb24 # Conflicts: # Makefile # include/uapi/linux/android/binder.h 2022-06-28T05:01:06+00:00 Stephen Rothwell sfr@canb.auug.org.au 2022-06-28T05:01:06+00:00 urn:sha1:def536ebb0e85dcd381259c073d3b249cce8cc6a 2022-06-28T05:01:05+00:00 Stephen Rothwell sfr@canb.auug.org.au 2022-06-28T05:01:05+00:00 urn:sha1:eb47467200cdf8bece17594a619e612122285767 2022-06-27T22:56:31+00:00 Stephen Rothwell sfr@canb.auug.org.au 2022-06-27T22:56:31+00:00 urn:sha1:a15a8e7f4e9d849531b250ea1978b42b231d46e9 2022-06-25T00:01:31+00:00 Linus Torvalds torvalds@linux-foundation.org 2022-06-25T00:01:31+00:00 urn:sha1:8c23f235a6a8ae43abea215812eb9d8cf4dd165e Pull gpio fixes from Bartosz Golaszewski: - make the irqchip immutable in gpio-realtek-otto - fix error code propagation in gpio-winbond - fix device removing in gpio-grgpio - fix a typo in gpio-mxs which indicates the driver is for a different model - documentation fixes - MAINTAINERS file updates * tag 'gpio-fixes-for-v5.19-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux: gpio: mxs: Fix header comment gpio: Fix kernel-doc comments to nested union gpio: grgpio: Fix device removing gpio: winbond: Fix error code in winbond_gpio_get() gpio: realtek-otto: Make the irqchip immutable docs: driver-api: gpio: Fix filename mismatch MAINTAINERS: add include/dt-bindings/gpio to GPIO SUBSYSTEM 2022-06-23T21:20:33+00:00 Uwe Kleine-König u.kleine-koenig@pengutronix.de 2022-06-15T12:47:18+00:00 urn:sha1:097c53a7281852422278568dde6132af1c23c97f The remove callback is only called after probe completed successfully. In this case platform_set_drvdata() was called with a non-NULL argument and so chip is never NULL. Also note that returning an error code from a remove callback doesn't result in the device staying bound. It's still removed and devm callbacks are called. This is a preparation for making platform remove callbacks return void. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl> 2022-06-23T21:19:14+00:00 Uwe Kleine-König u.kleine-koenig@pengutronix.de 2022-06-21T06:35:24+00:00 urn:sha1:0c609049273bee373d65df875b95cf73dfb51813 priv cannot be NULL because brcmstb_gpio_probe() calls platform_set_drvdata() with a non-NULL argument, so the check for !priv can be dropped. Also remove the variable ret that is only used to hide a bit that in the end zero is returned. This is a preparation for making platform remove callbacks return void. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl> 2022-06-23T21:18:13+00:00 Stefan Wahren stefan.wahren@i2se.com 2022-06-17T10:38:09+00:00 urn:sha1:b0d473185ba887c798ed0cd6f5abf4075363baa4 This driver is about MXS GPIO support. MXC is a different platform. Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com> Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl> 2022-06-23T21:13:32+00:00 Uwe Kleine-König u.kleine-koenig@pengutronix.de 2022-06-14T19:48:02+00:00 urn:sha1:1933569ab5331036e21e5b9f9ac691c1bc49f914 There is no user of these callbacks. The motivation for this change is to stop returning an error code from the remove callback. This is a preparation for making platform remove callbacks return void. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>