linux-kernel - Re: [PATCH 0/1] Constify struct address_space

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: <4B26C68D.1080300@gmail.com>
Date:	Tue, 15 Dec 2009 00:13:17 +0100
From:	Emese Revfy <re.emese@...il.com>
To:	Arjan van de Ven <arjan@...radead.org>
CC:	Pavel Machek <pavel@....cz>, Paul Mundt <lethal@...ux-sh.org>,
	Matthew Wilcox <matthew@....cx>, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, viro@...iv.linux.org.uk,
	akpm@...ux-foundation.org, Greg KH <gregkh@...e.de>
Subject: Re: [PATCH 0/1] Constify struct address_space_operations for 2.6.32-git-053fe57ac
 v2

Arjan van de Ven wrote:
> Now, a 300 patch series to lkml is not the way to do this.
> First step is to make checkpatch.pl warn about new cases.

I will add this structures the checkpatch in the next patch series.

> Second step should be to convert all definitions, but using the "one
> patch per maintainer" rule, not "one patch per file" rule. Yes it's
> somewhat janitorial, but no it's not a big deal as long as it's not 300
> patches to lkml. And it is much better than whitespace changes; it's
> a real quality improvement to the kernel (in terms of code generation
> and API)

The first series was based on one patch per structure type, the current
split-up is based on one patch per structure type *and* subsystem as
suggested by Greg KH. I used get_maintainer --subsystem to find them which
resulted in 150 patches. If you know a better way or want per-type patches,
please let me know (and discuss it with Greg ;).
--
Emese


--
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/