linux-kernel - Re: (subset) [PATCH 0/9] Remove some unused header files

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <163700406707.683472.13536842768773786666.b4-ty@kernel.org>
Date:   Mon, 15 Nov 2021 19:21:07 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH 0/9] Remove some unused header files

On Tue, 2 Nov 2021 16:01:54 -0600, Jonathan Corbet wrote:
> While working on something totally different, it occurred to me to wonder
> which header files in the kernel are not used anywhere.  Writing a little
> program to figure that out in Rust was the perfect distriction from the
> work I really needed to be doing...  It turns out there aren't many under
> include/linux; this gets rid of the ones I found.
> 
> Jonathan Corbet (9):
>   Remove unused headers <linux/jz4740-adc.h> and
>     <linux/power/jz4740-battery.h>
>   nfs: remove unused header <linux/pnfs_osd_xdr.h>
>   Remove unused header <linux/cnt32_to_63.h>
>   Remove unused header <linux/sdb.h>
>   Input: remove unused header <linux/input/cy8ctmg110_pdata.h>
>   mtd: remove unused header file <linux/mtd/latch-addr-flash.h>
>   ARM: ixp4xx: remove unused header file pata_ixp4xx_cf.h
>   spi: remove unused header file <linux/platform_data/spi-clps711x.h>
>   net: remove unused header file <linux/ks8851_mll.h>
> 
> [...]

Applied to

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

Thanks!

[8/9] spi: remove unused header file <linux/platform_data/spi-clps711x.h>
      commit: 45971bdd8ca8b5a99a49f4db86737401c45e246f

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