linux-kernel - Re: [PATCH] spi: dw: Drop empty line from DebugFS init function

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: <168563614666.139315.15131843196445419713.b4-ty@kernel.org>
Date:   Thu, 01 Jun 2023 17:15:46 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Serge Semin <fancer.lancer@...il.com>,
        Serge Semin <Sergey.Semin@...kalelectronics.ru>
Cc:     Osama Muhammad <osmtendev@...il.com>, linux-spi@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: dw: Drop empty line from DebugFS init function

On Wed, 31 May 2023 01:17:25 +0300, Serge Semin wrote:
> Just drop a redundant empty line from the dw_spi_debugfs_init() function
> left in the framework of the commit 0178f1e5d984 ("spi-dw-core.c: Fix
> error checking for debugfs_create_dir") after removing the last return
> statement.
> 
> 

Applied to

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

Thanks!

[1/1] spi: dw: Drop empty line from DebugFS init function
      commit: 3ecd5a728903b3057012043f98464c20cea1cdbb

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