From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750855AbXBMToD (ORCPT ); Tue, 13 Feb 2007 14:44:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750854AbXBMToD (ORCPT ); Tue, 13 Feb 2007 14:44:03 -0500 Received: from ug-out-1314.google.com ([66.249.92.175]:42968 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750839AbXBMTnp (ORCPT ); Tue, 13 Feb 2007 14:43:45 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=ahyb1Q2w2IrVABypLaZbcV6scXxyrAKYOKbrnwL2JVUshxN1MMtGVk86cZ9cngde3RzbvqCpUOMPWYkRgdr8vQiuQRPYytqNPRbQE4YQgcN1Nk452reM75BaQchP88TBvHFmQNM9diFmWJuKzePa1Kk41+q6uqsJUhJjkHAk9Js= Message-ID: <84144f020702131143r767aa40blb97a39b40bee73b8@mail.gmail.com> Date: Tue, 13 Feb 2007 21:43:41 +0200 From: "Pekka Enberg" To: "Sergei Organov" Subject: Re: somebody dropped a (warning) bomb Cc: "Linus Torvalds" , "=?ISO-8859-1?Q?J.A._Magall=C3=C3=C2=B3n?=" , "Jan Engelhardt" , "Jeff Garzik" , "Linux Kernel Mailing List" , "Andrew Morton" In-Reply-To: <87bqjxooog.fsf@javad.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45CB3B28.60102@garzik.org> <87abznsdyo.fsf@javad.com> <874pprr5nn.fsf@javad.com> <87ps8end9b.fsf@javad.com> <84144f020702131026q2af1afd6vbcd2708d7b7b9907@mail.gmail.com> <87bqjxooog.fsf@javad.com> X-Google-Sender-Auth: c9cef168dc564338 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 2/13/07, Sergei Organov wrote: > With almost any warning out there one makes more or less efforts to > suppress the warning where it gives false positives, isn't it? Yes, as long it's the _compiler_ that's doing the effort. You shouldn't need to annotate the source just to make the compiler shut up. Once the compiler starts issuing enough false positives, it's time to turn off that warning completely. Therefore, the only sane strategy for a warning is to aim for zero false positives. Pekka