Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265287AbUIOQ6o (ORCPT ); Wed, 15 Sep 2004 12:58:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266244AbUIOQ57 (ORCPT ); Wed, 15 Sep 2004 12:57:59 -0400 Received: from convulsion.choralone.org ([212.13.208.157]:33802 "EHLO convulsion.choralone.org") by vger.kernel.org with ESMTP id S266821AbUIOQ4N (ORCPT ); Wed, 15 Sep 2004 12:56:13 -0400 Date: Wed, 15 Sep 2004 17:56:08 +0100 From: Dave Jones To: Linus Torvalds Cc: Kernel Mailing List Subject: Re: Being more anal about iospace accesses.. Message-ID: <20040915165608.GC24892@redhat.com> Mail-Followup-To: Dave Jones , Linus Torvalds , Kernel Mailing List References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1057 Lines: 22 On Wed, Sep 15, 2004 at 09:30:42AM -0700, Linus Torvalds wrote: > So right now the current snapshots (and 2.6.9-rc2) have this enabled, and > some drivers will be _very_ noisy when compiled. Most of the regular ones > are fine, so maybe people haven't even noticed it that much, but some of > them were using things like "u32" to store MMIO pointers, and are > generally extremely broken on anything but an x86. We'll hopefully get > around to fixing them up eventually, but in the meantime this should at > least explain the background for some of the new noise people may see. For the curious, 6MB of sparse output is generated from a make allmodconfig right now. (http://www.codemonkey.org.uk/junk/2.6.9-rc2-warnings.txt) You can filter out just the __iomem warnings by grepping for asn:2 Dave - 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/