Message ID | 20241106005800.7520-1-kiseok.jo@irondevice.com |
---|---|
Headers | show |
Series | Add a driver for the Iron Device SMA1307 Amp | expand |
On Wed, Nov 06, 2024 at 09:57:59AM +0900, Kiseok Jo wrote: > This adds the schema binding for the Iron Device SMA1307 Amp > That's a v5. RESEND means you send exactly the same or the same plus tags. If you change patch, then it is v5, so the tools know how to handle it and we do no waste time at reviewing things twice. > Signed-off-by: Kiseok Jo <kiseok.jo@irondevice.com> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Best regards, Krzysztof
On Wed, Nov 06, 2024 at 11:28:45PM +0000, Ki-Seok Jo wrote: > Oh, I'm sorry, that was my mistake. > I realized the error and send it again using a script, but I accidentally left out the changelogs. > I'll resend it with the changelogs added this time. > Since there are no changes, I'll simply resend it without additional modifications. It's OK, no need for any further resends just now - just try to consider it in future.
On Wed, 06 Nov 2024 09:57:58 +0900, Kiseok Jo wrote: > This adds basic audio support for the Iron Device SMA1307 amplifier > > Kiseok Jo (2): > ASoC: dt-bindings: irondevice,sma1307: Add initial DT > ASoC: sma1307: Add driver for Iron Device SMA1307 > > .../bindings/sound/irondevice,sma1307.yaml | 53 + > sound/soc/codecs/Kconfig | 10 + > sound/soc/codecs/Makefile | 2 + > sound/soc/codecs/sma1307.c | 2052 +++++++++++++++++ > sound/soc/codecs/sma1307.h | 444 ++++ > 5 files changed, 2561 insertions(+) > create mode 100644 Documentation/devicetree/bindings/sound/irondevice,sma1307.yaml > create mode 100644 sound/soc/codecs/sma1307.c > create mode 100644 sound/soc/codecs/sma1307.h > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/2] ASoC: dt-bindings: irondevice,sma1307: Add initial DT commit: 82a1ccdf616d396c99f535febb6c997781c5c26c [2/2] ASoC: sma1307: Add driver for Iron Device SMA1307 commit: 576c57e6b4c1d734bcb7cc33dde9a99a9383b520 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