linux-kernel - Re: [PATCH] ASoC: qcom: lpass-platform: Update warning print to control excess logging

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <164581054746.2548431.12085357818762890090.b4-ty@kernel.org>
Date:   Fri, 25 Feb 2022 17:35:47 +0000
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, quic_plai@...cinc.com, robh+dt@...nel.org,
        perex@...ex.cz, linux-arm-msm@...r.kernel.org,
        srinivas.kandagatla@...aro.org, devicetree@...r.kernel.org,
        tiwai@...e.com, linux-kernel@...r.kernel.org,
        bjorn.andersson@...aro.org, agross@...nel.org, swboyd@...omium.org,
        judyhsiao@...omium.org, rohitkr@...eaurora.org,
        Srinivasa Rao Mandadapu <quic_srivasam@...cinc.com>,
        alsa-devel@...a-project.org, bgoswami@...eaurora.org
Cc:     Venkata Prasad Potturu <quic_potturu@...cinc.com>
Subject: Re: [PATCH] ASoC: qcom: lpass-platform: Update warning print to control excess logging

On Fri, 25 Feb 2022 18:12:23 +0530, Srinivasa Rao Mandadapu wrote:
> Update dev_warn to dev_warn_ratelimit to control excess xrun logging
> in lpass platform driver.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: qcom: lpass-platform: Update warning print to control excess logging
      commit: 5a5d2316a5292222383d4e3589b8f5144f7c9b49

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