linux-kernel - Re: [PATCH] x86-kernel: fix sparse warnings

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: <20080721112355.GA23095@elte.hu>
Date:	Mon, 21 Jul 2008 13:23:55 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jaswinder Singh <jaswinder@...radead.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	kernelnewbies <kernelnewbies@...linux.org>,
	kernel-janitors <kernel-janitors@...r.kernel.org>,
	David Woodhouse <dwmw2@...radead.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] x86-kernel: fix sparse warnings


* Jaswinder Singh <jaswinder@...radead.org> wrote:

> I am trying to solve following sparse warnings. Please give me feedback
> for the Patch. You can also find updated sparse patches from
> http://git.infradead.org/users/jaswinder/sparse-2.6.git

>  28 files changed, 140 insertions(+), 18 deletions(-)

nice.

Could you please split this up into individual commits, and against 
tip/master:

  http://people.redhat.com/mingo/tip.git/README

Granularity should be roughly per file. (i.e. around 30 commits would be 
fine) That way if any commit is found to be bad we can unapply/revert it 
just fine without the rest of your changes. Merging into different topic 
branches is also easier that way.

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