On Fri, Apr 21, 2017 at 7:28 PM, Mark Brown <broonie@xxxxxxxxxx> wrote: > The patch > > ASoC: Add Odroid sound DT bindings documentation > > has been applied to the asoc tree at > > git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git > > 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 > > From 92c9f05ebc7290e638c7b1b85288918c4fc65d4e Mon Sep 17 00:00:00 2001 > From: Sylwester Nawrocki <s.nawrocki@xxxxxxxxxxx> > Date: Fri, 21 Apr 2017 19:19:49 +0200 > Subject: [PATCH] ASoC: Add Odroid sound DT bindings documentation > > This patch adds DT binding documentation for Odroid XU3/4 > sound subsystem. > > Signed-off-by: Sylwester Nawrocki <s.nawrocki@xxxxxxxxxxx> > Signed-off-by: Mark Brown <broonie@xxxxxxxxxx> > --- > .../devicetree/bindings/sound/samsung,odroid.txt | 57 ++++++++++++++++++++++ > 1 file changed, 57 insertions(+) > create mode 100644 Documentation/devicetree/bindings/sound/samsung,odroid.txt Hi Mark, Although Sylwester is known of writing good quality code and can be trusted but he posted it just 9 minutes ago. Isn't it a little bit too fast to apply? I just finished reading cover letter but didn't manage to start looking at the rest. :) Best regards, Krzysztof -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |