From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Date: Wed, 08 Jul 2020 18:00:25 +0100 From: Mark Brown In-Reply-To: <20200706175353.16404-1-michael@walle.cc> References: <20200706175353.16404-1-michael@walle.cc> Message-Id: <159422762554.28767.4356365814640031762.b4-ty@kernel.org> Subject: Re: [PATCH v5 00/13] Add support for Kontron sl28cpld To: linux-watchdog@vger.kernel.org, linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-pwm@vger.kernel.org, Michael Walle Cc: Jason Cooper , Lee Jones , Bartosz Golaszewski , Wim Van Sebroeck , Thierry Reding , Jean Delvare , Greg Kroah-Hartman , Rob Herring , Linus Walleij , u.kleine-koenig@pengutronix.de, Guenter Roeck , Thomas Gleixner , Andy Shevchenko , Marc Zyngier , Shawn Guo , Li Yang List-ID: On Mon, 6 Jul 2020 19:53:40 +0200, Michael Walle wrote: > The Kontron sl28cpld is a board management chip providing gpio, pwm, fan > monitoring and an interrupt controller. For now this controller is used on > the Kontron SMARC-sAL28 board. But because of its flexible nature, it > might also be used on other boards in the future. The individual blocks > (like gpio, pwm, etc) are kept intentionally small. The MFD core driver > then instantiates different (or multiple of the same) blocks. It also > provides the register layout so it might be updated in the future without a > device tree change; and support other boards with a different layout or > functionalities. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next Thanks! [1/1] regmap-irq: use fwnode instead of device node in add_irq_chip() commit: 5cc2013bfeee756a1ee6da9bfbe42e52b4695035 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark