linux-kernel - Re: [PATCH] Make uapi/linux/irqnr.h non-empty

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]

Date:	Tue, 16 Oct 2012 19:03:15 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	David Howells <dhowells@...hat.com>
Cc:	linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...otime.net>,
	Alessandro Suardi <alessandro.suardi@...il.com>,
	Viresh Kumar <viresh.kumar@...com>,
	Michal Marek <mmarek@...e.cz>
Subject: Re: [PATCH] Make uapi/linux/irqnr.h non-empty

On Mon, Oct 15, 2012 at 9:14 AM, David Howells <dhowells@...hat.com> wrote:
> uapi/linux/irqnr.h was emitted by the UAPI disintegration script as an empty
> file because the parent linux/irqnr.h had no UAPI stuff in it, despite being
> marked with "header-y".
>
> Unfortunately, it patch deletes the empty file when applying a kernel patch.

Sadly, this is by far not the only empty file we now have, so applying
this patch seems pointless..

Doing a "git clean -dqfx" followed by "find . -size 0" shows quite a
few empty files, most of them being Kbuild files, and most of them
having come in through the UAPI patches. Maybe some of those *should*
be removed?

Some of the empty files seem pointless. The

  arch/arm/mach-spear13xx/include/mach/spear1310_misc_regs.h

file, for example, has always been empty, and does not seem to be actually used.

Hmm? I added a few more people to the cc list.

                 Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/