linux-kernel - Re: Changelog quality

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: <20100115133933.GB21188@rakim.wolfsonmicro.main>
Date:	Fri, 15 Jan 2010 13:39:33 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Julia Lawall <julia@...u.dk>
Cc:	Pekka Enberg <penberg@...helsinki.fi>,
	David Miller <davem@...emloft.net>, stefanr@...6.in-berlin.de,
	adi@...apodia.org, nm127@...email.hu, david.vrabel@....com,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	cocci@...u.dk, Andrew Morton <akpm@...ux-foundation.org>,
	Nicolas Palix <npalix@...u.dk>
Subject: Re: Changelog quality

On Fri, Jan 15, 2010 at 01:06:04PM +0100, Julia Lawall wrote:
> On Fri, 15 Jan 2010, Mark Brown wrote:

> > This would also mean that other people could run and re-run the scripts
> > during development much more easily which would help improve the
> > coverage of new code.

> On the other hand, one has to take into account the fact that at least in 
> my case, the patches that are submitted are the ones that I have carefully 
> checked for correctness.  Having a make target in the kernel might give 
> some suggestion of quality that is perhaps not appropriate?

This is a general problem with any tool that generates warnings - we
already have to educate people about how to use the GCC and sparse
warnings appropriately, I can't see that these warnings would be any
different.
--
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/