[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <165461109692.1597191.11390741473240531333.b4-ty@kernel.org>
Date: Tue, 07 Jun 2022 15:11:36 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-doc@...r.kernel.org, corbet@....net, mchehab@...nel.org
Cc: linux@...ck-us.net, linux-cachefs@...hat.com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
dave.hansen@...ux.intel.com, linux-samsung-soc@...r.kernel.org,
geert@...ux-m68k.org, ulf.hansson@...aro.org, hpa@...or.com,
alsa-devel@...a-project.org, linux-m68k@...ts.linux-m68k.org,
krzysztof.kozlowski+dt@...aro.org,
bcm-kernel-feedback-list@...adcom.com, kvm@...r.kernel.org,
mingo@...hat.com, mchehab+huawei@...nel.org, jdelvare@...e.com,
robh+dt@...nel.org, linux-gpio@...r.kernel.org, rafael@...nel.org,
linux-mmc@...r.kernel.org, federico.vaga@...a.pv.it, bp@...en8.de,
linux-phy@...ts.infradead.org, mmayer@...adcom.com,
keyrings@...r.kernel.org, x86@...nel.org,
linux-usb@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
alim.akhtar@...sung.com, Viresh Kumar <viresh.kumar@...aro.org>,
linux-pm@...r.kernel.org, linux-hwmon@...r.kernel.org,
jarkko@...nel.org, tglx@...utronix.de, linus.walleij@...aro.org
Subject: Re: (subset) [PATCH 00/23] Update Documentation/ cross-references
On Mon, 6 Jun 2022 16:25:22 +0100, Mauro Carvalho Chehab wrote:
> There were a number of DT binding conversions and other docs change that
> were not updated. Address them, in order to keep the cross-references on
> a sane state.
>
> Patch series is against v5.19-rc1 (and applies cleanly on the top of
> today's -next).
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[22/23] ASoC: wm8731: update wlf,wm8731.yaml reference
commit: 69c8027c5ff43d68449fda4510a8cce70e8578b0
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
Powered by blists - more mailing lists