linux-kernel - Re: [PATCH] sound: remove duplicate "the the" phrase in Kconfig text

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 for Android: free password hash cracker in your pocket

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

Date:   Tue, 18 Aug 2020 17:55:50 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Michal Simek <michal.simek@...inx.com>,
        Colin King <colin.king@...onical.com>,
        linux-arm-kernel@...ts.infradead.org,
        Jaroslav Kysela <perex@...ex.cz>, alsa-devel@...a-project.org,
        Liam Girdwood <lgirdwood@...il.com>,
        Takashi Iwai <tiwai@...e.com>
Cc:     linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] sound: remove duplicate "the the" phrase in Kconfig text

On Mon, 17 Aug 2020 23:47:06 +0100, Colin King wrote:
> There are a couple of occurrences of "the the" in the Kconfig
> text. Fix these.

Applied to

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

Thanks!

[1/1] sound: remove duplicate "the the" phrase in Kconfig text
      commit: 466a806a7d2beffa6a79d61dbabac8a48685c3e2

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