Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757312AbYLDLe5 (ORCPT ); Thu, 4 Dec 2008 06:34:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754917AbYLDLes (ORCPT ); Thu, 4 Dec 2008 06:34:48 -0500 Received: from rv-out-0506.google.com ([209.85.198.230]:40460 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754680AbYLDLer (ORCPT ); Thu, 4 Dec 2008 06:34:47 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=BaXEHK/2tc3n9pUscmdLNGKTui5uZ+sdKYEq2dVE9BXdsTnPAOK0N483OMUpZjiI+K viHDOHqbU2p4CGzKrpwCPHaOB/xHEby21l8N0fdnxBqA4ZPCocMtzJYIv4vDSlbV9vh0 WduTNYy7IgFkavC6KEsPUIesD83uO3L9RBNWg= Message-ID: <2375c9f90812040334x1abed8d9q98b74a3883fe0417@mail.gmail.com> Date: Thu, 4 Dec 2008 11:34:46 +0000 From: "=?UTF-8?Q?Am=C3=A9rico_Wang?=" To: "Ingo Molnar" Subject: Re: [PATCH 2/3] fix warning of not used variable Cc: "Jianjun Kong" , rusty@rustcorp.com.au, Linux-Kernel-Mailing-List In-Reply-To: <20081204101223.GB18708@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081204010022.GB17445@ubuntu> <20081204101223.GB18708@elte.hu> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 607 Lines: 19 On Thu, Dec 4, 2008 at 10:12 AM, Ingo Molnar wrote: > > > NAK. Warnings do not need to be "fixed", then need to be looked at and > then there are two approaches: > > 1) GCC is wrong => annotate the code > 2) GCC is right => fix the code > Gcc is correct. The only user of print_unload_info() is m_show() which is protected by CONFIG_PROC_FS. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/